Integrations / Advertising
Revcontent
Server-to-server conversion tracking for Revcontent native advertising campaigns. Replays the Revcontent click identifier (rc_uuid) captured first-party on the landing page and posts conversion value to the conversion.php postback endpoint.
Datafly Signal delivers first-party events to Revcontent server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Revcontent expects.
Why route Revcontent 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 Revcontent optimises against are not filtered by the browser.
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 Revcontent needs to attribute the event to the right session.
Click identifiers are captured and replayed
Signal stores clickid first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
One consent decision governs every destination
Revcontent 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_leadpagepurchasesign_upVertical presets
Conversion Tracking. 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 Revcontent documentation.
Frequently asked questions
Does Datafly Signal integrate with Revcontent?
Yes. Datafly Signal delivers first-party events to Revcontent server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Revcontent expects. The integration is included in every deployment at no additional cost.
How is server-side Revcontent tracking different from the Revcontent tag?
The Revcontent 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 Revcontent from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Revcontent?
The blueprint ships with mappings for generate_lead, page, purchase, sign_up. Any event in your schema can be mapped to Revcontent through pipeline configuration without a code change.
Do I need to keep the Revcontent 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 Revcontent deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move Revcontent server-side?
See how Datafly Signal delivers first-party events to Revcontent from infrastructure you control, with hashed identity and consent enforcement built in.