Map a connector's fields to lead details and consent
Tell ACR which property in Klaviyo, a CRM or another connector holds a phone number, a cart link, an opt-in or a fact for the agent.
Last reviewed November 7, 2026
Where to set it
On the lead source step of a campaign that uses a connector, each trigger card except Order placed has a Field mapping box. Each row reads: vendor property, fills, ACR field. Use dots for nested values, such as extra.checkout_url. Press Add a mapping for another row and Save mapping to store it on the trigger. It applies from the next event.
What a mapping can fill
| ACR field | What it takes |
|---|---|
email, phone, first_name, last_name | Text or a number |
country_code, region_code | The country code, and the state or province code |
language, timezone | Such as en-US and America/Chicago |
cart_link | A full address starting with http:// or https://; anything else is ignored |
consent.sms, consent.calls, consent.email, consent.whatsapp | An opt-in or an opt-out (below) |
context. followed by a name | Any value, kept for start conditions and the agent. A list or object is stored as text, up to 500 characters. |
A mapped value replaces what ACR read on its own. A mapped property that is empty or missing changes nothing.
For consent, true, yes, y, 1, subscribed, opted_in, opt-in, granted and consented count as an opt-in, and false, no, n, 0, unsubscribed, opted_out, opt-out, revoked and denied as an opt-out. Anything else leaves consent unknown. Consent explains which sources a campaign accepts.
Which properties each connector exposes
- Klaviyo: the event's own properties and the fields of the profile it belongs to.
- Omnisend and CheckoutChamp: every key you add to the posted body, or every Export Name you add to the profile.
- NextCommerce: the cart's metadata and attribution fields.
- Pipedrive: the person's fields and custom fields, by Pipedrive's field key.
- Attio: each attribute's first value, by its slug.
- monday.com: each column's text, by column ID.
- Zendesk: the user's fields and user fields, by key.
- GoHighLevel: the contact's standard fields.
- HubSpot, Salesforce and Dynamics 365: only the fixed set of fields ACR fetches, listed in each one's article. A mapping to any other field finds nothing.
- Zapier and Make: mappings are not applied. Send the fields under the Custom API keys instead.
Pipedrive, Attio, GoHighLevel, monday.com and Zendesk also keep a contact's custom fields on the lead without any mapping, under context. and the connector's name, such as context.pipedrive. followed by the field key. Start conditions can test them, and the agent can read them.
When two campaigns map the same field
A checkout source's events can reach every campaign that uses the source, so ACR applies the mappings from all of them. When two map the same ACR field differently, the campaign higher in the list wins. A CRM contact starts one named campaign, and only that campaign's mapping applies.