> For the complete documentation index, see [llms.txt](https://docs.pushpushgo.company/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pushpushgo.company/campaigns/push-campaign/create-campaign/content/personalization.md).
# Personalization
In the process of personalization, you send campaigns with messages tailored to each subscriber.
In the personalization, use nunjucks syntax. It allows you to access previously prepared labels.
An example of nunjucks:
**Title**: `Hello {{name}}!`
If there's no such label, nothing will render in this place.
A subscriber with the `name: "Mateusz"` label will see "`Hello Mateusz`" in their push.
{% hint style="warning" %}
You don't have to do anything to choose the type of personalized campaign. All you need is to use the nunjucks syntax in the Title, Content, or Link fields.
{% endhint %}
There are fields for personalizing the message in the campaign. They are available in the "Personalization" section.
Use those variables in your content and you'll see how the message may look to a given subscriber.
If you want to see how the personalized message looks for another subscriber, refresh the site using the "Refresh" button 
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.pushpushgo.company/campaigns/push-campaign/create-campaign/content/personalization.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.