Integrations / Advertising
VideoAmp
Server-side conversion delivery to VideoAmp for cross-platform CTV measurement. Sends purchase and lead events to VideoAmp's Conversions API so video impressions can be matched against downstream outcomes.
Datafly Signal delivers first-party events to VideoAmp server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload VideoAmp expects.
Why route VideoAmp 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 VideoAmp optimises against are not filtered by the browser.
Email and phone number hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so VideoAmp receives match keys rather than raw personal data.
Client IP and user agent are preserved
Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so VideoAmp attributes the event to the right session.
One consent decision governs every destination
VideoAmp is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
generate_leadpurchaseVertical presets
Retail. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the VideoAmp documentation.
Frequently asked questions
Does Datafly Signal integrate with VideoAmp?
Yes. Datafly Signal delivers first-party events to VideoAmp server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload VideoAmp expects. The integration is included in every deployment at no additional cost.
How is server-side VideoAmp tracking different from the VideoAmp tag?
The VideoAmp tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to VideoAmp from your server, so delivery does not depend on browser conditions.
What personal data is sent to VideoAmp?
Email and phone number are normalised and SHA-256 hashed inside your own deployment before delivery, so VideoAmp receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to VideoAmp?
The blueprint ships with mappings for generate_lead, purchase. Any event in your schema can be mapped to VideoAmp through pipeline configuration without a code change.
Do I need to keep the VideoAmp tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so VideoAmp deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move VideoAmp server-side?
See how Datafly Signal delivers first-party events to VideoAmp from infrastructure you control, with hashed identity and consent enforcement built in.