Connect your customer data stack

Server-side tags forward events. Upstack resolves identity first, then forwards enriched events. When someone clicks your ad on mobile and buys on desktop a week later, a server-side tag sees two anonymous events. Upstack sees one customer, stitches the journey, and sends a single identity-resolved conversion to your ad platform. That’s why EMQ scores jump and your Klaviyo flows reach more people.

Each destination is added once, with its own credentials: a Pixel ID and Conversions API token for Meta, for example, or a private API key for Klaviyo. Some platforms also ask you to turn off their own Shopify tracking so events aren’t counted twice. After that there’s no tag management or data layer to build: Upstack captures your store’s events once and sends every connected destination the same identity-resolved data, mapped to that platform’s own event names.

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Upstack includes a flexible webhook system for custom destinations. If your tool accepts incoming events via webhook or API, we can connect it. Contact our team and we’ll help you set it up, usually in the same onboarding call.

Most marketing tools rely on browser cookies that expire in 7 to 20 days. Upstack builds a persistent identity graph that lasts for the life of the customer and works across devices. The result: your ad platforms see higher Event Match Quality (EMQ), your email and SMS flows fire for customers who would otherwise be invisible, and your analytics reflect the real customer journey, not a fragmented cookie trail.