Skip to main content
Request a demo
  1. Home
  2. Integrations
  3. RevContent
Upstack Data

RevContent integration: identity-resolved conversions, sent server-side

Server-side conversions to RevContent, resolved to a person and deduplicated so a purchase is counted once.

Request a demo Start free trial
Role
Destination
Category
Ad platforms
Pre-built connectors
12 sources
Plans
All plans

What Upstack sends

Every conversion reaches RevContent with the identifiers it matches on. Captured on the server, resolved to a person, then sent.

In: from Shopify1 of 12 sources
  • order_idShopify order and checkout token
  • email / phonecustomer contact from checkout
  • customer_idShopify customer record, if they have one
  • line_itemsproducts, variants and quantities
  • total / subtotal / discountorder economics

Storefront events from the Upstack Pixel, orders directly from Shopify.

Upstack DataResolved before it is sent
  • IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
  • customer_typeNew or returning, resolved before send.
  • DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
  • Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Out: to RevContentOn every event
  • hashed email / phoneidentity matching on arrival
  • rc_click_idcredit the click that drove it
  • external_idstable person across sessions
  • event_iddedupe against the browser pixel
  • value / currencyvalue-based bidding

Native conversions, deduplicated.

See the set-up reference See all 12 sources How resolution works

About RevContent

Upstack forwards conversions from the server with hashed identifiers and the click ID restored, resolved to a person first.

Deduplication happens before the send, so RevContent and a paid-search campaign do not both claim the same order.

What RevContent is

RevContent is a native advertising network placing recommendations across publisher sites.

Its traffic converts on a delay, the standard problem for discovery channels.

How RevContent works

RevContent attributes conversions through its pixel and postback API within a click window. Conversions the browser fails to report, or that arrive after another touch, are not counted.

What you can do with it

Three jobs this connector does inside RevContent.

01

Send complete conversions

Conversions reach RevContent through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

02

Optimize on the customer you want

Map any order attribute to the conversion RevContent receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

03

One order, one owner

Conversions are deduplicated against every other channel before they are sent, so reported performance adds up to the revenue that actually exists.

Pre-built connectors

12 sources connect to RevContent. Whichever of these you run, RevContent is one switch away.

See all connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for RevContent as a destination.

FAQ

RevContent integration questions.

What does Upstack send to RevContent?

Server-side conversions to RevContent, resolved to a person and deduplicated so a purchase is counted once.

How do I check that events are reaching RevContent?

Open RevContent › Campaigns › Conversions. The postback log records each server-side conversion and its matched click.

Which plans include the RevContent integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which sources can send events to RevContent?

12 sources: Shopify, WooCommerce, BigCommerce, Checkout Champ, Recharge, Custom stack, Funnelish, Lasso Commerce, Phoenix Technologies, Skio, Loop Subscriptions and Stripe. Each one has its own pre-built connector.

Will Upstack slow down my store?

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Similar integrations

Other Ad platforms integrations.

See all integrations

Get RevContent tracking right.

A 15-minute walkthrough tailored to your stack and channels.

Request a demo Start free trial