Home
Connectors
Loop Subscriptions - Your warehouse

Send every Loop Subscriptions event to your warehouse, server-side

Q: How do I check that Loop Subscriptions 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 Loop Subscriptions to your warehouse?

Most brands are live in under 20 minutes. Once Loop Subscriptions is connected, 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 Loop Subscriptions event reaches your warehouse. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Loop Subscriptions

Capture Loop Subscriptions events server-side (new subscriptions, renewals, swaps and cancellations), each as what it actually is.

See the Loop Subscriptions integration

Loop SubscriptionsWhat it sends

subscription_idthe Loop subscription across its whole life
email / phonesubscriber contact
event_typerenewal, swap, skip, pause, cancel or save
line_itemsproducts after any swap
total / intervalcharge amount and billing cadence

02 Understand

Resolved to one person before it leaves

Every Loop Subscriptions 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

Renewals, swaps and pauses are separate event types that a warehouse schema built for orders has nowhere to put, so retention analysis is reconstructed by inference rather than read.

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 Loop Subscriptions feeds your warehouse. Two gains on the warehouse side, two on the Loop Subscriptions 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.

Loop Subscriptions

Every event, server-side

Storefront and checkout events are captured from Loop Subscriptions on the server, independent of the browser.

Loop Subscriptions

One setup, every destination

Connect Loop Subscriptions once and forward to every ad platform, email tool and warehouse you run.

Setup

Live in under 20 minutes.

Connect Loop Subscriptions once and every destination, your warehouse included, is forwarded the same resolved events.

Upstack dashboardExample

Loop Subscriptions Data source Connected

Your warehouse Destination Healthy

Read the full warehouse setup guide

01

Connect Loop Subscriptions

Capture Loop Subscriptions events server-side (new subscriptions, renewals, swaps and cancellations), each as what it actually is.
02

Add the warehouse destination

Under Destinations, add your warehouse. Every resolved Loop Subscriptions 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 Loop Subscriptions and your warehouse.

How do I check that Loop Subscriptions 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 Loop Subscriptions to your warehouse?

Most brands are live in under 20 minutes. Once Loop Subscriptions is connected, every destination receives the same resolved events, your warehouse included.