Loop Subscriptions to PostHog
Forward every Loop Subscriptions event to PostHog server-side, resolved to a person against a 750M+ device graph — so records and reporting reflect the person, not the device.
Connection
Connect Loop Subscriptions to PostHog 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 integrationPostHog
Stream resolved product and commerce events into PostHog for analysis on a person, not a session.
PostHog integrationWhat changes
What changes when Loop Subscriptions feeds PostHog.
Server-side delivery
Events reach PostHog 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 PostHog carries a resolved customer, matched against a 750M+ device graph.
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 PostHog needs.
Loop Subscriptions and PostHog 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 PostHog 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
PostHog receives
- distinct_id
- the person, across devices
- event name and properties
- funnels and retention
- $set person properties
- user-level attributes
Records you can audit
How you know it is working.
A CRM is only as trustworthy as its worst duplicate. These controls exist so the record reflects the person.
Per-record inspection
Trace any property back to the event that set it.Deduplication
One person, one record, across devices and identifiers.Bot and fraud filtering
Automated traffic never becomes a contact.
Where to check in PostHog
PostHogActivity, then check that a single person shows events from more than one device.
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 PostHog.
- ShopifyPostHog
- WooCommercePostHog
- BigCommercePostHog
- Checkout ChampPostHog
- RechargePostHog
- Custom stackPostHog
- FunnelishPostHog
- Lasso CommercePostHog
- Phoenix TechnologiesPostHog
- SkioPostHog
- StripePostHog
- Everything PostHog can take12 sources feed PostHog, and the setup is the same for each one.PostHog 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 PostHog.
A 15-minute walkthrough of this connector on your own account.