Home
Connectors
Loop Subscriptions - PostHog

Send every Loop Subscriptions event to PostHog, server-side

Q: How does Upstack identify users in PostHog?

Upstack assigns each visitor a consistent distinct_id that persists across sessions, devices and browsers when it can resolve the visitor’s identity. Anonymous visitors get a temporary ID that Upstack tries to merge once the visitor is identified.

Q: Will I see duplicate events if I also have PostHog installed via another method?

Possibly. If PostHog’s JavaScript snippet or another integration sends the same events, you may see duplicates, so disable overlapping event types in either Upstack or the other integration.

Q: Which events does PostHog receive?

PageView as $pageview, ViewContent as view_item, AddToCart as add_to_cart, InitiateCheckout as initiate_checkout and Purchase as purchase.

Q: Which customer parameters are sent to PostHog?

Each event carries Upstack’s resolved distinct_id, which persists across sessions, plus email when the visitor is identified, IP address, user agent and device details.

Q: How do I check that Loop Subscriptions events are reaching PostHog?

Visit your store, view a product or add to cart, and confirm the event appears in PostHog under Activity, Live Events.

Q: How long does it take to connect Loop Subscriptions to PostHog?

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

Each event is resolved to a person against a 750M+ device graph before it reaches PostHog, so records and reporting reflect the person, not the device.

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 PostHog. 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.
DeduplicationOne person, one record, across devices and identifiers.
Bot and fraud filteringAutomated traffic never becomes a contact.

A CRM is only as trustworthy as its worst duplicate. These controls exist so the record reflects the person.

03 Activate

Delivered to PostHog

Stream resolved product and commerce events into PostHog for analysis on a person, not a session.

See the PostHog integration

PostHogWhat it receives

distinct_idthe person, across devices
event name and propertiesfunnels and retention
$set person propertiesuser-level attributes

Which events reach PostHog

Each Upstack event is mapped to the PostHog event below before it is sent.

Upstack event	Sent to PostHog as
Page view	$pageview
Product view	view_item
Add to cart	add_to_cart
Checkout	initiate_checkout
Purchase	purchase

Each event carries Upstack’s resolved distinct_id, which persists across sessions, plus email when the visitor is identified, IP address, user agent and device details.

The catch

Cancel-flow outcomes are the most valuable CRM field in a subscription business and the least likely to be synced, so churn reasons live only in Loop.

Where to check in PostHogRecords you can audit

PostHog Activity

then check that a single person shows events from more than one device.

What changes

What changes when Loop Subscriptions feeds PostHog. Two gains on the PostHog side, two on the Loop Subscriptions side.

PostHog

Server-side delivery

Upstack always sends events to PostHog from its servers as well as through the PostHog snippet, so an event an ad blocker or browser privacy setting stops in the browser still arrives from the server.

PostHog

Identity-resolved events

Events sent to PostHog carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

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.

You need your PostHog Project API Key from Project Settings and the data region, US or EU, where your project is hosted.

Upstack dashboardExample

Loop Subscriptions Data source Connected

PostHog Destination Healthy

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

Under Destinations, add PostHog with your Project API Key, which starts with phc_, and the Data Region (US or EU) that matches where your PostHog project is hosted.
03

Check Live Events in PostHog

Visit your store, view a product or add to cart, and confirm the event appears in PostHog under Activity, Live Events.

FAQ

Questions about Loop Subscriptions and PostHog.

How does Upstack identify users in PostHog?

Upstack assigns each visitor a consistent distinct_id that persists across sessions, devices and browsers when it can resolve the visitor’s identity. Anonymous visitors get a temporary ID that Upstack tries to merge once the visitor is identified.

Will I see duplicate events if I also have PostHog installed via another method?

Possibly. If PostHog’s JavaScript snippet or another integration sends the same events, you may see duplicates, so disable overlapping event types in either Upstack or the other integration.

Which events does PostHog receive?

PageView as $pageview, ViewContent as view_item, AddToCart as add_to_cart, InitiateCheckout as initiate_checkout and Purchase as purchase.

Which customer parameters are sent to PostHog?

Each event carries Upstack’s resolved distinct_id, which persists across sessions, plus email when the visitor is identified, IP address, user agent and device details.

How do I check that Loop Subscriptions events are reaching PostHog?

Visit your store, view a product or add to cart, and confirm the event appears in PostHog under Activity, Live Events.

How long does it take to connect Loop Subscriptions to PostHog?

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