> For the complete documentation index, see [llms.txt](https://docs.bird.com/taxi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/taxi/connectors/klaviyo-connector/setting-up-personalisation-for-klaviyo.md).
# Setting up personalisation for Klaviyo
Before setting up personalisation in Taxi from Klaviyo, you'll need to [set up personalisation](https://docs.messagebird.com/taxi/Dynamic%20content,%20segmentation%20and%20personalisation/Personalisation/setting-up-personalisation-fields) in your account.
Klaviyo uses [Django](https://docs.djangoproject.com/en/1.8/ref/templates/builtins/) for segmentation and personalisation. Personalisation fields in Klaviyo use the following style of notation:
\#{{ first\_name }}
or
\#{{ person.title }}
for a custom variable.
These are set up in the personalisation settings in Taxi.
These will become available in rich text fields in the editor.
\
You can add as much or as little code here as you like, so it’s possible to use Klaviyo code to do things like use a fallback for first name and make the first name capitalised:
| Hi #{{ first\_name\|title\|default:'there' }} |
| --------------------------------------------- |
---
# 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:
```
GET https://docs.bird.com/taxi/connectors/klaviyo-connector/setting-up-personalisation-for-klaviyo.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.