Home
Connectors
Funnelish - RevContent

RevContent

Send Funnelish funnel events to RevContent

Q: How do I check that Funnelish events are reaching RevContent?

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

Q: Will a purchase be counted twice?

No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

Q: How long does it take to connect Funnelish to RevContent?

Most brands are live in under 20 minutes. Once Funnelish events reach Upstack, every destination receives the same resolved events, RevContent included.

Each event is resolved to a person against a 750M+ device graph before it reaches RevContent, with restored click IDs, deduplicated conversions and delivery you can audit.

Request a demo Start free trial

US device IDs in the graph: 750M+
Match rate on events: 90%+
Identity window, per customer: Lifetime
Most brands are live: <20 min

How it flows

How a Funnelish event reaches RevContent. Tracked on the funnel page, resolved to a person, then sent.

01 Capture

Captured from Funnelish

Add the Upstack Pixel to your Funnelish funnels to track what shoppers do there. When Funnelish creates the order in Shopify, Upstack records it like any other Shopify order.

See the Funnelish integration

FunnelishWhat it sends

page / eventsfrom the Upstack Pixel in each funnel’s head
fbclid / gclid / ttclidclick IDs kept on the way to checkout
order_idthe Shopify order Funnelish creates
order sourceshows as Funnelish in Upstack reports

02 Understand

Resolved to one person before it leaves

Every Funnelish event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.

How resolution works

Resolved 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.

Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.

03 Activate

Delivered to RevContent

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

See the RevContent integration

RevContentWhat it receives

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

The catch

Funnel pages sit outside your Shopify theme, so the Upstack app embed doesn't run on them, and click IDs such as fbclid, gclid and ttclid are easily dropped on the way to checkout.

Add the Upstack Pixel to each funnel and keep the click IDs on the links to checkout. The order itself reaches Upstack when Funnelish creates it in Shopify, counted once per Shopify order ID.

Where to check in RevContentDelivery you can audit

RevContent Campaigns Conversions

The postback log records each server-side conversion and its matched click.

What changes

What changes when Funnelish feeds RevContent. Two gains on the RevContent side, two on the Funnelish side.

RevContent

Server-side delivery

Events reach RevContent through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

RevContent

Identity-resolved events

Events sent to RevContent carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

Funnelish

Funnel pages tracked

The pixel loads in the head of every funnel page, so visits and the events you configure are recorded on pages your theme never touches.

Funnelish

One setup, every destination

Connect Funnelish once and forward to every ad platform and email tool you run.

Setup

Live in under 20 minutes.

Connect Funnelish once and every destination, RevContent included, is forwarded the same resolved events.

Upstack dashboardExample

RevContent Destination Healthy

Read the full RevContent setup guide

01

Add the Upstack Pixel to each funnel

In Funnelish, add the Upstack Pixel snippet to each funnel as a tracking code placed with Append To Page Head. If the funnel links to Shopify, add the script that keeps click IDs and UTMs on the link.
02

Add the RevContent destination

Under Destinations, add RevContent. Every resolved Funnelish event is then forwarded to it.
03

Check delivery to RevContent

Every conversion is inspectable from the moment it fires to the moment the platform confirms it.

FAQ

Questions about Funnelish and RevContent.

How do I check that Funnelish events are reaching RevContent?

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

Will a purchase be counted twice?

No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

How long does it take to connect Funnelish to RevContent?

Most brands are live in under 20 minutes. Once Funnelish events reach Upstack, every destination receives the same resolved events, RevContent included.