> 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/hubspot-connector/setting-up-personalisation-for-hubspot.md).

# Setting up personalisation for Hubspot

Before setting up personalisation in Taxi from Hubspot, 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.

Personalisation fields in Hubspot use HubSpot Markup Language ([HubL](https://developers.hubspot.com/docs/cms/hubl#types-of-delimiters)), and uses the following style of notation:

\#{{contact.firstname}}

These can be set up in the [personalisation](/taxi/dynamic-content-segmentation-and-personalisation/personalisation/what-is-personalisation.md) settings in Taxi.

![](https://2516523503-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMq0EQG9Ff46ZMsrIBcVn%2Fuploads%2Fgit-blob-9c91b49764e3d4e4a268c4851aeb7dc8778592a6%2Fhubspot%2Bpersonalisation1.png?alt=media)

These will become available in rich text fields in the editor.

![](https://2516523503-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMq0EQG9Ff46ZMsrIBcVn%2Fuploads%2Fgit-blob-0426ed91e5375297518f74c151cf827d49c58032%2Fhubspot%2Bpersonalisation2.png?alt=media)

If you would like to set defaults for personalisation using Hubspot, for example, to show different content if a recipient’s first name isn’t known, you can set this up in Hubspot. Find out more [here](https://knowledge.hubspot.com/email/how-do-i-create-default-values-for-my-personalization-tokens).

You can also add as much or as little code to the personalisation page in Taxi to show different content depending on who is receiving the email, for example, based on gender:

}


---

# 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.bird.com/taxi/connectors/hubspot-connector/setting-up-personalisation-for-hubspot.md?ask=<question>&goal=<endgoal>
```

`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.