illumin (Acuity Ads)
Datafly Signal fires illumin (formerly Acuity Ads) page and conversion pixels server-to-server, matched on the illumin user and cookie IDs from the illumin ID sync.
Why route illumin (Acuity Ads) 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. Signal sends the event from your own server, so the conversions illumin (Acuity Ads) optimises against are not filtered by the browser.
- One consent decision governs every destination. illumin (Acuity Ads) 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 pixel URL and Pixel Keys
illumin does not publish its pixel API. Ask your illumin representative for the conversion pixel URL and a Pixel Key (pk) for each event you track: page, conversion (order completed) and, optionally, lead.
Deploy the illumin ID sync
illumin matches on auid (user ID) and cauid (cookie ID), set by the illumin ID sync. Collect both in Signal with ID providers named illumin_auid and illumin_cauid (Settings > ID providers). An event without both is not sent.
Configure in Signal
Configuration fields
| Field | Required | Description |
|---|---|---|
endpoint_url | Yes | The illumin conversion pixel URL, without query parameters, as supplied by your illumin representative. illumin does not publish it. |
page_pixel_key | No | The illumin Pixel Key (pk) for page events. Leave blank to send no page events. |
conversion_pixel_key | Yes | The illumin Pixel Key (pk) for order-completed and policy-purchase conversions. |
lead_pixel_key | No | The illumin Pixel Key (pk) for leads and completed quotes. Leave blank to send no lead events. |
Management UI setup
- Go to Integrations > Add Integration > illumin (Acuity Ads).
- Choose a preset: Default (
default), E-commerce (ecommerce), Insurance (insurance). - Fill in the fields above and click Save.
Request format
GET <pixel URL>?pk=PK_CONV&auid=527998349489&cauid=cauid-77
&pu=https%3A%2F%2Fshop.example.co.uk%2Fcheckout%2Fdone&ordid=ORD-1001&crev=259.99&prodid=SKU_1~SKU_2The visitor IP and user agent are sent as the X-Forwarded-For and User-Agent headers. One request per event; requests over about 20,000 characters fail.
Event mapping
| Signal event | Vendor event | Presets |
|---|---|---|
page | page | Default, E-commerce, Insurance |
purchase | purchase | Default, E-commerce, Insurance |
generate_lead | lead | Default, Insurance |
quote_completed | lead | Insurance |
Events not listed are not sent (the presets drop unmapped events). Each preset turns on the strict output contract, so only the mapped fields are sent.
Identity
Matching is by auid and cauid only. No email, phone or other personal data is sent: the pixel has no parameter for it.
Limitations
- illumin publishes no API reference. The request follows illumin’s partner integration on MetaRouter (read 2026-09-22); confirm it with your illumin representative before going live.
- Currency is not sent: the pixel has no currency parameter.
Vendor documentation
illumin (Acuity Ads) (read 2026-09-22).