Revcontent

Datafly Signal sends conversions to Revcontent server-to-server through the S2S conversion postback, attributed by the Revcontent click ID.

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 what Revcontent receives is not filtered by the browser.
Click identifiers are captured and replayed. Signal keeps the click ID first-party when the visitor lands and attaches it to the later conversion.
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.
No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

Find your API key

Your API access key is in Revcontent Account Settings.

Keep rc_uuid on landing pages

Revcontent appends rc_uuid to your destination URLs after a click. Make sure it survives redirects to the landing page.

Remove the conversion pixel

Do not also fire Revcontent’s conversion pixel for the same conversion: it would be counted twice.

Configure in Signal

Configuration Fields

Field	Required	Description
`api_key`	Yes	Your Revcontent API access key, found in your Revcontent Account Settings. Sent as the api_key query parameter on every conversion postback.

Management UI Setup

Go to Integrations > Add Integration > Revcontent.
Choose a preset: Conversion Tracking (default), Retail (ecommerce), Lead Generation (lead_gen), Insurance (insurance).
Fill in the fields above and click Save.

Request format

A GET with every value in the query string. amount must be a non-zero whole number; Signal rounds the conversion value.

GET https://trends.revcontent.com/api/v1/conversion.php?amount=260&api_key={api_key}&rc_uuid=rc-7f3e&user_agent=Mozilla%2F5.0+%28Macintosh%3B+Intel+Mac+OS+X+10_15_7%29&user_ip=203.0.113.9

Event Mapping

Signal event	Vendor event	Presets
`purchase`	`purchase`	Conversion Tracking, Retail, Insurance
`generate_lead`	`lead`	Conversion Tracking, Lead Generation, Insurance
`sign_up`	`complete_registration`	Conversion Tracking, Lead Generation
`quote_completed`	`lead`	Insurance

Identity

Attribution is by the Revcontent click ID (rc_uuid) only. The visitor’s IP and user agent are sent as the optional user_ip and user_agent. No personal data is sent.

Revcontent is an advertising destination and requires marketing consent by default.

Known limitations

The collector does not capture rc_uuid from the landing URL yet (#1461); until it does, Signal sends it only when an ID provider collects it into collected_ids.rc_uuid.

Troubleshooting

Problem	Solution
Events dropped in Signal	The visitor has no `rc_uuid`, or the conversion has no value (Revcontent requires a non-zero amount).

Blueprint

The Revcontent blueprint version is 0.5.0. It was last reviewed against the vendor’s documentation on 2026-09-22.