Funnelish to Outbrain
Forward every Funnelish event to Outbrain server-side, resolved to a person against a 750M+ device graph — with restored click IDs, deduplicated conversions and delivery you can audit.
Connection
Connect Funnelish to Outbrain with Upstack Data
Funnelish
Capture every Funnelish order and one-click upsell from the server, so funnel revenue is counted in full rather than at the first step.
Funnelish integration
Outbrain
Send conversions to Outbrain with the click ID recovered from the graph, so native placements are judged on orders rather than on sessions.
Outbrain integrationWhat changes
What changes when Funnelish feeds Outbrain.
Server-side delivery
Events reach Outbrain through its server API, not the browser — so ad blockers, ITP and consent banners don’t cost you conversions.
Identity-resolved events
Every event sent to Outbrain carries a resolved customer, matched against a 750M+ device graph.
Every event, server-side
Storefront and checkout events are captured from Funnelish on the server, independent of the browser.
One setup, every destination
Connect Funnelish once and forward to every ad platform, email tool and warehouse you run.
What actually moves
What Funnelish carries, and what Outbrain needs.
Funnelish and Outbrain describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Funnelish can put on an event, the right is what Outbrain can actually use.
Funnelish sends
- order_id
- Funnelish order, including the upsell sequence
- email / phone
- contact from the order form
- line_items
- initial offer plus every accepted upsell
- total / upsell_total
- the full amount taken, not the first step
- funnel_id / step
- which funnel and which step converted
- customer_type
- new or returning, resolved before send
Outbrain receives
- hashed email / phone
- identity matching on arrival
- ob_click_id
- credit the click that drove it
- external_id
- stable person across sessions
- event_id
- dedupe against the browser pixel
- value / currency
- value-based bidding
Delivery you can audit
How you know it is working.
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.
Per-event inspection
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.Deduplication
Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.Bot and fraud filtering
Automated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Where to check in Outbrain
OutbrainConversionsTracking. Server-reported conversions list the click ID they matched against.
Related connectors
Other places Funnelish can send to.
- FunnelishMeta Conversions API
- FunnelishGoogle Ads Conversions
- FunnelishTikTok Events API
- FunnelishPinterest
- FunnelishSnapchat
- FunnelishReddit
- FunnelishMicrosoft Ads
- FunnelishX
Other sources that feed Outbrain.
- ShopifyOutbrain
- WooCommerceOutbrain
- BigCommerceOutbrain
- Checkout ChampOutbrain
- RechargeOutbrain
- Custom stackOutbrain
- Lasso CommerceOutbrain
- Phoenix TechnologiesOutbrain
- SkioOutbrain
- Loop SubscriptionsOutbrain
- StripeOutbrain
- Everything Outbrain can take12 sources feed Outbrain, and the setup is the same for each one.Outbrain integration
- How resolution worksEvery event matched against a 750M+ device graph before it is forwarded.Upstack Signal
- What it costsThree plans that scale with your order volume. Every connector is on every plan.See pricing
Get Funnelish talking to Outbrain.
A 15-minute walkthrough of this connector on your own account.