Revcontent

Revcontent is a traffic source (native). Its own documentation: https://api.revcontent.io/docs/stats/index.html.

What it connects

• Sends your conversions back to Revcontent.
• Pulls your spend from its API.
• Blocks placements in a source campaign.
• Pauses and resumes its campaigns and ads.
• Sets bids on its campaigns and placements.
• Sets daily budgets on its campaigns.
• Checks the connection with a harmless request when you test it.

How to connect it

Client credentials. Tallyray gets an access token with the client id and secret you set below, and gets a new one when it expires.

Postbacks take a credential of their own (postback), apart from the one above, so conversions go without the API’s credentials.

Set these on the connection:

Field	Name	Kind	What to enter
API key	api_key	string, required, secret	Your account’s API key, from Revcontent’s Account Settings, which its conversion postback takes
Account time zone	time_zone	string	For spend, the time zone Revcontent reports your account’s days in, such as America/New_York; it can’t change once spend is reported
Stats API client id	client_id	string, secret	From Revcontent’s Account Settings, Stats API Credentials, once your representative opens the API to your account; for spend, widgets and pauses
Stats API client secret	client_secret	string, secret

A secret is set by the workspace’s owner alone and never shown again. A required secret that is missing holds the connection’s deliveries until it is set; one that is optional holds only what reads it.

Tracking macros

Each token is a query parameter on the campaign URL; the source replaces its macro with the value when it sends the visitor. The columns say which part of the visit it fills and which report column (v1 to v20) it lands in.

Parameter	Macro	Fills	Report column
rc_uuid	added by the platform itself	The source’s click id
widget	{widget_id}	Placement	v1 (Widget)
boost	{boost_id}	Source campaign	v2 (Campaign)
content	{content_id}	Creative	v3 (Content)
site	{site_name}	Site	v4 (Site)
adv_targets	{adv_targets}	Custom value	v5 (Traffic type)

The campaign URL you paste into the source is the tracking domain, the campaign’s key and the tokens the source fills, in this order (the domain below is an example, and {url_key} stands for the campaign’s own key):

https://trk.example.com/{url_key}?widget={widget_id}&boost={boost_id}&content={content_id}&site={site_name}&adv_targets={adv_targets}

Cost models, the first the default: cpc (cost per click), cpm (cost per thousand visits), api (the spend pulled from the source’s API).

Preview the campaign URL

Your tracking domain

Campaign URL

https://trk.example.com/{url_key}?widget={widget_id}&boost={boost_id}&content={content_id}&site={site_name}&adv_targets={adv_targets}

Copy

Paste the campaign URL into the source's ad. {url_key} stands for the campaign's own key, which the portal fills in; the macros are the source's, which it replaces with each visit's values.

How conversions get back to it

Tallyray sends a conversion to Revcontent when it enters one of these statuses: approved. A conversion is sent once per status it enters; an adjustment, with revenue moving and its status not, isn’t sent. A conversion older than 30d isn’t sent.

Tallyray’s event kinds, and the name each is sent as. A conversion of a kind not listed isn’t sent:

Tallyray event	Sent to Revcontent as
sale	sale

The request: GET https://trends.revcontent.com/api/v1/conversion.php.

A conversion is sent only when this holds:

=visit.external_click_id != ''

Conversions are retried when the source can’t be reached or answers with an error that can pass; see the limits below.

Spend

Tallyray pulls spend from the source’s API every 1h, covering the last 2d again, as sources restate spend, 1d at most per request, by day, in the zone =conn.time_zone != '' ? conn.time_zone : 'set the account time zone'. With api among the cost models, a campaign is priced by it.

The request: GET https://api.revcontent.io/stats/api/v1.0/boosts/performance.

Pulling spend needs the API’s credential. A connection without it goes on sending conversions and pulls no spend.

Placements

Placements are the visit’s placement value, as the tokens above fill it.

Blocking: POST https://api.revcontent.io/stats/api/v1.0/boosts/{…}/targets/blacklist/widgets/add. Mode append: Tallyray sends the placements to add. Lifting a block is sent too.

Pausing and resuming

Rules and reports can pause and resume the source’s own objects at these levels. Tallyray reads an object before it writes, and writes only what isn’t so already, so a repeated pause never toggles anything.

Level	Named by
campaigns	boost
ads	boost + content

A write may take up to 2m to show in a read; a read within that time that disagrees is read again later, not taken for a person’s change at the source.

Bids

Rules and reports can set the source’s bids at these levels. Each value is read before it’s written, in the account’s currency, never converted; a value the source sets itself isn’t written.

Level	Named by	Prices	Bounds	Notes
campaigns	boost	cpc	step 0.001
placements	boost + widget	cpc	min 0.001, max 3, step 0.001	takes its campaign’s value unless it has its own; can be reset to the inherited value

Daily budgets

Rules and reports can set the source’s daily budgets at these levels, read before they’re written, in the account’s currency.

Level	Named by	Prices	Bounds	Notes
campaigns	boost	daily	min 50, step 0.01

Limits

• Rate: at most 2/s per connection, 2 at once.
• Retries: up to 15 attempts, waiting from 30s and doubling up to 6h, longer when the source’s Retry-After asks, and never past the conversion’s age limit.
• Hosts it reaches: trends.revcontent.com, api.revcontent.io. No other.
• What a connection may override: /tokens, /conversions/events, /conversions/send_on, /cost. Hosts, authentication and requests never are, and an override may only lower the limits.

This page describes version 2 of the Revcontent template, the latest published. The version your connection runs is the one your administrators approved, and the portal shows it.