Revcontent boosts,measured widget by widget

The Revcontent template captures widget, content, boost, headline and site data, and Revcontent adds its rc_uuid click ID on every click. ClickFlare posts conversions with payout to trends.revcontent.com using your API key, and the cost integration pulls spend by campaign, content and widget.

Start for free

Read the setup guide

Revcontent

Native content discovery network

At a glance

How it connects

S2S postback (API key) + cost API (Client ID and Secret)

What syncs

Conversions and payout out; campaign, content, widget cost in

Sync schedule

Real time, per conversion

Key parameters

rc_uuid, widget_id, content_id, boost_id, site_name

Works with

Native recommendation widgets, bought on CPC

Good to know

amount is required in the postback and must not be zero

Native ad network

S2S postback

Widget-level cost

Find the Revcontent widgets that pay for themselves

Widget and content ROI

widget_id shows which publisher widgets convert, and content_id with the headline shows which creatives work.

One clean conversion count

Revcontent's postback has no event type, so you send only the event it should optimize on and keep its conversion rate honest.

Spend straight from the API

Revcontent has no cost variable for the URL. The cost integration pulls spend at campaign, content and widget level instead.

How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

Your ad

Visitor clicks

Ad on Revcontent

ClickFlare

Click recorded

A unique cf_click_id is created

Your offer

Conversion

Lead, sale or custom event

ClickFlare

Sent back to Revcontent

Through the Conversion API or postback

Cost API

Spend pulled in

Revcontent cost matched to each campaign

Your ad

Revcontent click

Macros fill the tracking URL

ClickFlare

Click recorded

Zone, site and device data stored

Offer or lander

Visitor converts

On your page or the offer

ClickFlare

Conversion logged

With payout and event type

Postback

Reported to Revcontent

So its optimization sees the result

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

A unique cf_click_id is created

Your article

Keyword block

Click ID passed to the feed

Results page

Paid click

Conversion fired to ClickFlare

Revcontent API

Revenue matched

Pulled on a schedule and reconciled

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

cf_click_id passed to the offer

Revcontent

Offer or call

The network tracks the action

Revcontent

Conversion

Lead, sale, call or rebill

Postback

Payout in ClickFlare

Matched to the original click

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

A unique cf_click_id is created

Revcontent

Store or funnel

Click ID kept through checkout

Events

View, cart, checkout

Each step tracked

ClickFlare

Purchase recorded

Order value matched to the ad

Native ad network

API key, rc_uuid and amount: three required values

Revcontent appends rc_uuid to each click, and the template copies it into the visit with the {conversion_uuid} variable. On a conversion, ClickFlare sends it back with the payout as amount, authenticated with the API key from Account Settings.

Don't add rc_uuid to URLs by hand
Postback or Revcontent pixel, never both
Leave the campaign-level tracking code empty

Today, one campaign

example

Spend pulled from Revcontent

cost

$412.30

Conversions recorded

today

Sent back to Revcontent

per event

38/38

Profit

campaign

$227.70

Example numbers. Cost and conversions sit in the same report row.

Captured on every Revcontent click

key macros

rc_uuid, widget_id, content_id, boost_id, site_name

captured

From the Revcontent template in ClickFlare. Use them as report columns and rules.

Revenue for one click

example

Paid click

day 0

$0.00

First revenue pull

+1h

$0.41

Scheduled updates

next days

$0.58

Final pull

last sync

$0.62

Example amounts. Sync timing for Revcontent is in the facts above.

Events for one click

example

Lead

day 0

$0.00

Sale

day 0

+$40.00

Upsell

day 1

+$15.00

Refund

day 9

−$15.00

Example events. Each one arrives by postback and is matched to the click.

One visitor's path

example

Product view

step 1

—

Add to cart

step 2

—

Checkout

step 3

—

Purchase

step 4

$68.00

Example order. Each event is tied to the ad that brought the visitor.

Tracking fields captured

Required postback values

2.3B

Events tracked

Setup

Connected in four steps

You need a Revcontent account with its API key, Client ID and Client Secret from Account Settings, and a ClickFlare account with your own tracking domain.

Add the Revcontent traffic source In the campaign editor, add a traffic source from the Revcontent template. Turn on Traffic source postback URL and replace REPLACE_WITH_YOUR_API_KEY with your Revcontent API key.
Pick the one event to send Map the postback to the event Revcontent should count, usually your final sale. Use Event filter to send only conversions that carry a payout.
Launch the boost Create a boost in Revcontent and paste the ClickFlare campaign URL into each content item's Destination URL. Leave the campaign-level tracking code empty.
Connect Revcontent cost Add the Revcontent cost integration with the Client ID and Secret from Stats API Credentials, a matching timezone and your ad accounts. Select it on the traffic source and use Not Tracked.

Revcontent postback from the ClickFlare template

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

app.clickflare.com/integrations

Revcontent

Native ad network

Connected

Revcontent account connected

Signed in from ClickFlare

Cost syncing

Spend matched to campaigns

Conversions sent back

Your chosen events

Revcontent template selected

Macros pre-filled

Tracking URL in Revcontent

Click ID captured

Conversions reported

Payout included where supported

Revcontent connected

Credentials saved in ClickFlare

Conversion event set

Click ID passed to the feed

Revenue syncing

On the feed's schedule

Revcontent added

Offer URL carries the click ID

Postback set in Revcontent

Payout and event included

Conversions arriving

Matched to the click

Revcontent connected

Click ID kept to checkout

Events mapped

View, cart, checkout, purchase

Purchases tracked

Order value in reports

Ready to track

Use the postback or Revcontent's conversion pixel, not both. Running the two together reports every conversion twice.

Revcontent cost integration guide

Open the guide

In your reports

What you see once it's connected

ROI by widget
Results by content and headline
Results by boost
Results by site name
Results by traffic type
Cost by campaign and widget

Use cases

How media buyers run it

Revcontent → lander → offer

Send only the final sale with its payout, so Revcontent optimizes on buyers and leads don't inflate its conversion rate.

Revcontent → article → RSOC

Feed revenue arrives hours or days after the click. Send it to Revcontent with a delayed revenue postback.

Widget pruning

Group by widget_id and site name, then block the widgets where cost outruns payout.

Frequently asked questions

Questions about Revcontent

No items found.

Related integrations

More templates that plug into the same ClickFlare account.

MGo

MediaGo

Baidu's native ad platform

Native ad network

MGID

Native ad network

Outbrain

Native ads, now part of Teads

Native ad network

Taboola

Native advertising platform

Native ad network

AppLovin

Ad platform with a Conversion API

Ad platform

BIGO Ads

In-app ads on BIGO apps and network

In-app ad network

Browse all integrations ->

Setup guides

Revcontent cost integration guide

Revcontent postback setup guide

{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Revcontent?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare has a Revcontent traffic source template with an S2S postback, and a cost integration that pulls spend from Revcontent's API."}}, {"@type": "Question", "name": "Is the API key the same as the Client ID and Secret?", "acceptedAnswer": {"@type": "Answer", "text": "No. The API key authenticates postbacks. The Client ID and Secret, under Stats API Credentials, are for the cost integration. Both are in Account Settings."}}, {"@type": "Question", "name": "Why does Revcontent say my postback is invalid?", "acceptedAnswer": {"@type": "Answer", "text": "api_key, rc_uuid or amount is missing or empty, the API key placeholder wasn't replaced, rc_uuid was added by hand, or the payout was zero."}}, {"@type": "Question", "name": "Can Revcontent optimize for leads and sales separately?", "acceptedAnswer": {"@type": "Answer", "text": "Not through the postback. It has no event parameter, so send the one event you want Revcontent to optimize for."}}, {"@type": "Question", "name": "How do I test the Revcontent postback?", "acceptedAnswer": {"@type": "Answer", "text": "Revcontent has no test-conversion tool. Click your live content, convert, then check Logs → Postback Status for rc_uuid, amount and your API key."}}]}

Revcontent boosts,measured widget by widget

Find the Revcontent widgets that pay for themselves

Widget and content ROI

One clean conversion count

Spend straight from the API

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

API key, rc_uuid and amount: three required values

Connected in four steps

What you see once it's connected

How media buyers run it

Revcontent → lander → offer

Revcontent → article → RSOC

Widget pruning

Questions about Revcontent

Related integrations

Your Revcontent boosts, tracked to the payout.