Flashtalking
Datafly Signal can fire the Flashtalking (Innovid) Spotlight container tag server-side.
Cannot deliver attributable conversions. Flashtalking attributes a Spotlight hit by its own browser cookie, which a server request does not carry, and documents no server-to-server conversion API. The hit reaches Flashtalking but cannot be tied to an ad exposure. Use Flashtalking’s browser Spotlight tag for attribution.
Prerequisites
Find your Spotlight IDs
In the Spotlight tag snippet the Advertiser ID follows /container/, then the Spotlight ID and the Spotlight Group ID.
Configure in Signal
Configuration fields
| Field | Required | Description |
|---|---|---|
advertiser_id | Yes | The numeric Advertiser ID — the number immediately after /container/ in your Flashtalking Spotlight tag snippet. |
spotlight_id | Yes | The numeric Spotlight ID — the number immediately after your Advertiser ID in the tag snippet. Identifies the specific Spotlight (conversion activity). Create a separate Signal integration per Spotlight. |
spotlight_group_id | Yes | The numeric Spotlight Group ID — the number immediately after the Spotlight ID in the tag snippet. Identifies the Spotlight group the activity belongs to. |
Management UI setup
- Go to Integrations > Add Integration > Flashtalking.
- Choose a preset: Default (
default). - Fill in the fields above and click Save.
Request format
GET https://servedby.flashtalking.com/container/1234567;987654;5;num?cachebuster=<message ID>
&ftXRef=ORD-1001&ftXValue=259.99&ftXCurrency=GBP&ftXNumItems=2,1Event mapping
| Signal event | Vendor event | Presets |
|---|---|---|
page | page | Default |
purchase | purchase | Default |
sign_up | sign_up | Default |
generate_lead | generate_lead | Default |
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
No personal data is sent. The visitor IP and user agent are sent as headers.
Vendor documentation
Flashtalking (read 2026-09-22).