Acuity Ads
Send conversion events to Acuity Ads (illumin) for programmatic campaign attribution and performance optimisation across display, video, and CTV.
Why route 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, and Safari’s ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Acuity Ads optimises against are not filtered by the browser.
- Email and phone number are hashed before leaving your infrastructure. Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Acuity Ads receives match keys rather than raw personal data.
- Client IP and user agent are carried in the payload. Both are taken from the original visitor request rather than your server, which is what Acuity Ads needs to attribute the event to the right session.
- One consent decision governs every destination. 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
Complete these steps in the Acuity Ads (illumin) platform before configuring the integration in Signal.
Create or access your Acuity Ads (illumin) account
Log in to illumin (formerly Acuity Ads). If you don’t have an account, contact Acuity Ads sales to set up a programmatic advertising account. You’ll need advertiser-level access to retrieve credentials.
Get your Advertiser ID from the campaign dashboard
Navigate to your campaign dashboard and locate the Advertiser ID in Advertiser Settings. This is the unique identifier for your advertiser account and is required for event attribution.
Generate an API key
Go to Settings > API in the illumin platform to generate an API key. If the API settings section is not visible, contact your Acuity Ads account manager to request API access be enabled for your account.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
advertiser_id | string | Yes | Your Acuity Ads advertiser ID. Found in the illumin platform under Advertiser Settings. |
api_key | secret | Yes | API key for authenticating server-side event delivery. Generate in the illumin platform under Settings > API. |
Signal Setup
Quick Setup
- Navigate to Integrations in the sidebar.
- Open the Integration Library tab.
- Find Acuity Ads or filter by Advertising.
- Click Install, select a variant if available, and fill in the required fields.
- Click Install Integration to create the integration with a ready-to-use default configuration.
API Setup
curl -X POST http://localhost:8084/v1/admin/integration-catalog/acuity_ads/install \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "Acuity Ads",
"variant": "default",
"config": {
"advertiser_id": "adv-12345",
"api_key": "ak_acuity_abc123..."
},
"delivery_mode": "server_side"
}'API endpoint
GET https://secure.acuityplatform.com/track/cnvAllow egress to secure.acuityplatform.com from the network your delivery workers run on.
Event Mapping
The default Retail preset maps a minimal set of conversion events:
| Signal event | Acuity Ads event |
|---|---|
page | page_view |
Product Viewed | view_content |
Product Added | add_to_cart |
Order Completed | purchase |
To customise or extend, edit the integration’s Field Mappings in the Management UI.
Delivery
Events are delivered server-side from your Datafly Signal infrastructure directly to the Acuity Ads API. No client-side scripts are loaded for this integration.
Testing
- Install the integration with your Advertiser ID and API key.
- Trigger a test event (e.g. a page view) on your site with the Datafly.js collector active.
- Check the Live Events view in Signal to confirm the event was captured.
- Verify the event appears in the illumin campaign dashboard under conversion reporting.
- Check the Delivery Log in Signal for confirmation of successful delivery (HTTP 200 response).
Conversions may take up to 15 minutes to appear in the illumin reporting dashboard due to processing delays on the Acuity Ads side.
Troubleshooting
| Issue | Resolution |
|---|---|
401 Unauthorized | Verify your API key is correct and has not been revoked. Regenerate in illumin Settings > API if needed. |
404 Not Found | Check that the Advertiser ID matches your account exactly. |
| Events not appearing in illumin | Confirm the integration is enabled in Signal and check the Delivery Log for errors. Conversions may take up to 15 minutes to appear. |
429 Too Many Requests | Acuity Ads rate limits are being hit. Signal will automatically retry with backoff. |
Visit Acuity Ads documentation for full API documentation and credential setup instructions.