LiveIntent

Datafly Signal sends conversion signals to LiveIntent server-to-server through the Conversions API, keyed on the visitor’s hashed email for people-based attribution.

Why route LiveIntent through Datafly Signal

Conversions survive ad blockers and tracking prevention. A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari’s ITP shortens the cookies it can set. Signal sends the event from your own server, so what LiveIntent receives is not filtered by the browser.
Personal data is hashed before it leaves your infrastructure. Signal normalises and SHA-256 hashes the identifiers inside your own deployment, so the vendor receives match keys, never the raw values.
One consent decision governs every destination. LiveIntent is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

Get your credentials

Your LiveIntent account manager provides the authorisation token, the customer ID and the pixel ID. Tokens are rotated occasionally.

Send the email

LiveIntent attributes on the email hash. Call datafly.identify() with the email; an event from a visitor without one is not sent.

Configure in Signal

Configuration Fields

Field	Required	Description
`customer_id`	Yes	Your LiveIntent customer ID. Forms part of the Conversions API request path (https://conversions.liveintent.com/conversions/\{customer_id\}). Provided by your LiveIntent account manager.
`api_token`	Yes	The static Bearer token issued by LiveIntent for the Conversions API. Sent as the Authorization header. Request it from your LiveIntent account manager.
`pixel_id`	Yes	The numeric LiveIntent conversion pixel ID to attribute events against. Sent as pixelId on every conversion. Provided by your LiveIntent account manager.

Management UI Setup

Go to Integrations > Add Integration > LiveIntent.
Choose a preset: Default (default), Retail (ecommerce), Lead Generation (lead_gen), Media / Publishing (media), Insurance (insurance).
Fill in the fields above and click Save.

Request format

A JSON array of up to 100 conversion signals; one invalid signal fails the request. pixelId is a number and eventTime is in epoch seconds (at most 7 days old).

POST https://conversions.liveintent.com/conversions/{customer_id}

[
 {
  "eventId": "evt-e2-1",
  "eventTime": 1758500000,
  "pixelId": 67890,
  "purchaseData": {
   "currency": "GBP",
   "orderId": "ORD-1001",
   "sourceUrl": "https://shop.example.co.uk/checkout/done",
   "value": 259.99
  },
  "source": "web",
  "userData": {
   "ip": "203.0.113.9",
   "md5": "0cba00ca3da1b283a57287bcceb17e35",
   "sha2": "86e0b9e56c17cc4d12387e1949b85053fbe73bc3ce5a1188713a9d300cc6133d",
   "ua": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)"
  }
 }
]

Event Mapping

Signal event	Vendor event	Presets
`purchase`	`web`	Default, Retail, Insurance
`generate_lead`	`web`	Default, Lead Generation, Insurance
`sign_up`	`web`	Default, Retail, Lead Generation, Media / Publishing
`newsletter_subscribed`	`web`	Media / Publishing
`subscription_started`	`web`	Media / Publishing
`quote_completed`	`web`	Insurance

Signal forwards event properties the preset does not map unless the integration’s strict output contract is on. Turn on strict_output_contract for this integration so only the documented fields are sent.

Identity

userData.md5 (LiveIntent’s preferred hash) and userData.sha2 are the MD5 and SHA-256 of the trimmed, lower-cased email. IP address and user agent are sent unhashed.

LiveIntent is an advertising destination and requires marketing consent by default.

Known limitations

LiveIntent recommends removing dots and anything after a plus from Gmail addresses before hashing; Signal does not apply that yet, so some Gmail addresses match less often (#1377).

Troubleshooting

Problem	Solution
400 for the whole batch	One signal was invalid; check the currency is a three-letter code and events are less than 7 days old.

Blueprint

The LiveIntent blueprint version is 0.7.0. It was last reviewed against the vendor’s documentation on 2026-09-22.