Skip to main content
Upstack Data

Funnelish to Taboola

Forward every Funnelish event to Taboola server-side, resolved to a person against a 750M+ device graph — with restored click IDs, deduplicated conversions and delivery you can audit.

What changes

What changes when Funnelish feeds Taboola.

Server-side delivery

Events reach Taboola 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 Taboola 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 Taboola needs.

Funnelish and Taboola 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 Taboola 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

Taboola receives

hashed email / phone
identity matching on arrival
taboola_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 Taboola

Taboola AdsTrackingConversions. The conversions view shows the source of each event, so server-side arrivals are distinguishable.

Get Funnelish talking to Taboola.

A 15-minute walkthrough of this connector on your own account.