Revcontent

Revcontent is a native advertising and content-recommendation network. Datafly Signal delivers conversions to Revcontent server-to-server (S2S) using Revcontent’s conversion postback endpoint. When a visitor clicks a Revcontent ad, Revcontent appends a unique click identifier (rc_uuid) to your landing-page URL. Signal captures that identifier first-party, persists it, and replays it on the matching conversion event so Revcontent can attribute the conversion without a client-side pixel.

This integration is conversion-only: there is no page-view or browsing ingest path. Only conversion events (purchase, lead, sign-up) are delivered.

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.
• No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

• A Revcontent advertiser account with active campaigns.
• Your Revcontent API Key (Account Settings).
• Datafly.js installed on your site, configured to capture the rc_uuid URL parameter (see Identity Signals below).
• Your Revcontent destination URLs must forward all query parameters through any redirects, otherwise rc_uuid is dropped before it reaches the landing page.

Configuration

Configure in Signal

1. In the management UI, go to Integrations and add Revcontent.
2. Paste your API Key.
3. Attach the Revcontent integration to the pipeline that carries your conversion events.
4. Select the Default preset, which maps Order Completed, Lead Generated, and Signed Up to the Revcontent postback.
5. Save and enable.

API Endpoint

GET https://trends.revcontent.com/api/v1/conversion.php
    ?api_key={api_key}&rc_uuid={rc_uuid}&amount={amount}

Signal sends one GET request per conversion. The endpoint returns a 2xx response for any well-formed request, so a successful HTTP response does not guarantee a matched conversion. Always validate end-to-end in your Revcontent dashboard conversion report.

Identity Signals

Revcontent attribution depends entirely on the click identifier rc_uuid:

• On the first page of the visit, Revcontent appends ?rc_uuid=... to your landing-page URL.
• Datafly.js reads the rc_uuid URL parameter and stores it first-party so it survives across pages until the conversion happens.
• On the conversion event, Signal reads the stored identifier as vendor_ids.rc_uuid and sends it to Revcontent.

If rc_uuid was never captured (the visitor did not arrive via a Revcontent ad, or a redirect stripped the parameter), the conversion cannot be matched and Revcontent discards it.

No hashed email, phone, or consent field is accepted by this endpoint — matching is on rc_uuid only. Apply any consent gating upstream in your pipeline.

Event Mapping

amount must be a non-zero integer. Map a whole-dollar value; fractional amounts may be rejected or mis-counted.

Example

Track a purchase with Datafly.js:

datafly.track("Order Completed", {
  order_id: "ORDER-12345",
  revenue: 79,
  currency: "USD"
});

Resulting Revcontent postback (the rc_uuid is supplied automatically from the value Datafly.js captured on the landing page):

GET https://trends.revcontent.com/api/v1/conversion.php
    ?api_key=YOUR_API_KEY
    &rc_uuid=8f1c2d3e-...-captured-on-landing
    &amount=79
    &user_ip=203.0.113.7
    &user_agent=Mozilla%2F5.0...

Testing

1. Click one of your live Revcontent ads and confirm the landing-page URL contains ?rc_uuid=....
2. Complete a test conversion (purchase, lead, or sign-up) in the same browser session.
3. In Signal, open the Event Debugger and confirm the conversion event delivered to Revcontent with a populated rc_uuid and a non-zero amount.
4. Check your Revcontent dashboard conversion report for the test conversion (allow for reporting delay).

Troubleshooting

• No conversions appear in Revcontent. Confirm rc_uuid was captured. If the landing-page URL never shows rc_uuid, check that your redirects forward all query parameters to the final landing URL.
• rc_uuid is empty in the Event Debugger. Datafly.js did not capture the click identifier — verify the visitor arrived via a Revcontent ad and that the rc_uuid URL parameter reached the page before navigation.
• Conversion delivered (2xx) but not counted. The endpoint returns 2xx even for unmatched data. Confirm the amount is a non-zero integer and that the rc_uuid belongs to a real Revcontent click within the attribution window.
• amount rejected. Ensure the source value is a whole-dollar integer, not a decimal or zero.