Loop Subscriptions to Your warehouse
Forward every Loop Subscriptions event to Your warehouse server-side, resolved to a person against a 750M+ device graph — as a full-fidelity event stream you can query yourself.
Connection
Connect Loop Subscriptions to Your warehouse with Upstack Data
Loop Subscriptions
Capture Loop Subscriptions events server-side — new subscriptions, renewals, swaps and cancellations — each as what it actually is.
Loop Subscriptions integrationYour warehouse
A clean, resolved event stream into BigQuery, Snowflake or Redshift — the same data your dashboards run on.
Your warehouse integrationWhat changes
What changes when Loop Subscriptions feeds Your warehouse.
One resolved event stream
The same identity-resolved events that reach your ad platforms, landed in your warehouse.
Nothing sampled
Full-fidelity events, not an aggregate or a sample.
Every event, server-side
Storefront and checkout events are captured from Loop Subscriptions on the server, independent of the browser.
One setup, every destination
Connect Loop Subscriptions once and forward to every ad platform, email tool and warehouse you run.
What actually moves
What Loop Subscriptions carries, and what Your warehouse needs.
Loop Subscriptions and Your warehouse describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Loop Subscriptions can put on an event, the right is what Your warehouse can actually use.
Loop Subscriptions sends
- subscription_id
- the Loop subscription across its whole life
- email / phone
- subscriber contact
- event_type
- renewal, swap, skip, pause, cancel or save
- line_items
- products after any swap
- total / interval
- charge amount and billing cadence
- customer_type
- new or returning, resolved before send
Your warehouse receives
- event_id
- primary key you can join on
- resolved person ID
- stitch sessions to customers
- full property payload
- nothing dropped, nothing sampled
- ingest timestamp
- rebuild any point-in-time view
A stream you can audit
How you know it is working.
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.
Full lineage
Every row traceable to the event that produced it and the time it landed.Deduplication
Stable event IDs, so re-runs and backfills do not double rows.Bot and fraud filtering
Filtered before load, with the filter decision recorded.
Where to check in 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.
Related connectors
Other places Loop Subscriptions can send to.
- Loop SubscriptionsMeta Conversions API
- Loop SubscriptionsGoogle Ads Conversions
- Loop SubscriptionsTikTok Events API
- Loop SubscriptionsPinterest
- Loop SubscriptionsSnapchat
- Loop SubscriptionsReddit
- Loop SubscriptionsMicrosoft Ads
- Loop SubscriptionsX
Other sources that feed Your warehouse.
- ShopifyYour warehouse
- WooCommerceYour warehouse
- BigCommerceYour warehouse
- Checkout ChampYour warehouse
- RechargeYour warehouse
- Custom stackYour warehouse
- FunnelishYour warehouse
- Lasso CommerceYour warehouse
- Phoenix TechnologiesYour warehouse
- SkioYour warehouse
- StripeYour warehouse
- Everything Your warehouse can take12 sources feed Your warehouse, and the setup is the same for each one.Your warehouse 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 Loop Subscriptions talking to Your warehouse.
A 15-minute walkthrough of this connector on your own account.