Home
Connectors
Funnelish - Your warehouse

Send Funnelish funnel events to your warehouse

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

Query the events table directly: count distinct resolved person IDs against count distinct sessions, and compare the ratio to what your analytics reports.

Q: Will re-runs or backfills duplicate rows?

No. Stable event IDs, so re-runs and backfills do not double rows.

Q: How long does it take to connect Funnelish to your warehouse?

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

Each event is resolved to a person against a 750M+ device graph before it reaches your warehouse, as a full-fidelity event stream you can query yourself.

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 your warehouse. 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.
DeduplicationStable event IDs, so re-runs and backfills do not double rows.
Bot and fraud filteringFiltered before load, with the filter decision recorded.

Warehouse data is only useful if you trust it enough to base a decision on it. These controls exist so you can reconstruct how any row got there.

03 Activate

Delivered to your warehouse

A clean, resolved event stream into BigQuery, Snowflake or Redshift: the same data your dashboards run on.

See the warehouse integration

Your warehouseWhat it receives

event_idprimary key you can join on
resolved person IDstitch sessions to customers
full property payloadnothing dropped, nothing sampled
ingest timestamprebuild any point-in-time view

The catch

Upsell revenue lands as additional rows after the initial order, so a warehouse query that reads the first row per order under-reports the value of every funnel purchase.

Where to check in your warehouseA stream you can audit

Query the events table directly: count distinct resolved person IDs against count distinct sessions, and compare the ratio to what your analytics reports.

What changes

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

Your warehouse

One resolved event stream

The same identity-resolved events that reach your ad platforms, landed in your warehouse.

Your warehouse

Nothing sampled

Full-fidelity events, not an aggregate or a sample.

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, your warehouse included, is forwarded the same resolved events.

Upstack dashboardExample

Your warehouse Destination Healthy

Read the full warehouse 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 warehouse destination

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

Check delivery to your warehouse

Every row traceable to the event that produced it and the time it landed.

FAQ

Questions about Funnelish and your warehouse.

How do I check that Funnelish events are reaching your warehouse?

Query the events table directly: count distinct resolved person IDs against count distinct sessions, and compare the ratio to what your analytics reports.

Will re-runs or backfills duplicate rows?

No. Stable event IDs, so re-runs and backfills do not double rows.

How long does it take to connect Funnelish to your warehouse?

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