Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.upstackdata.com/llms.txt

Use this file to discover all available pages before exploring further.

You’ve installed the pixel, verified events, and connected Meta CAPI. Now run a single end-to-end test to confirm the full pipeline is working: a storefront action should flow through Upstack and arrive as a matched conversion in Meta.

​
What You’ll Accomplish

Trigger a real event on your Shopify store and trace it through every stage — from the Upstack Live Event Stream to Meta Events Manager — confirming that server-side conversion data is being delivered correctly.

​
Prerequisites

Prerequisites:
  • An active Shopify store
  • The Upstack Data app installed from the Shopify App Store
  • Your Pixel ID (found in the Upstack dashboard under Settings → Pixel)
You should have completed Step 3: Connect a Destination.

​
Validation Steps

1

Prepare your test environment

Open three tabs:
  1. Upstack Dashboard — navigate to Events → Live Event Stream
  2. Meta Events Manager — navigate to Your Pixel → Test Events and enter your storefront URL
  3. Your Shopify storefront — use an incognito/private window for a clean session
Using Meta’s Test Events tab gives you real-time visibility into incoming server events. Events in Test Events show within seconds, while the main Overview tab can have a 20+ minute delay.
2

Trigger a test purchase or add-to-cart

On your Shopify storefront, perform a complete flow:
  1. Visit a product page (generates ViewContent)
  2. Add the product to cart (generates AddToCart)
  3. Begin checkout (generates InitiateCheckout)
  4. If possible, complete a test purchase using Shopify’s Bogus Gateway (generates Purchase)
If you can’t complete a test purchase, an AddToCart event is sufficient to validate the pipeline. The key is confirming the event appears in both Upstack and Meta.
3

Confirm the event in Upstack

Switch to the Upstack Live Event Stream tab. Within a few seconds, you should see the events you just triggered. Click on an event to expand it and verify:
  • Event type matches your action (AddToCart, Purchase, etc.)
  • Pixel ID is correct
  • User data is populated (especially if you entered shipping details at checkout)
  • Destination status shows the event was forwarded to Meta
4

Confirm the event in Meta Events Manager

Switch to Meta Events Manager → Test Events. You should see the corresponding server event within 2-5 minutes.Look for:
  • The event name matches (e.g., AddToCart or Purchase)
  • The source shows Server (not just Browser)
  • The event details include user data parameters like em (hashed email), ph (hashed phone)
If you see the event from both Browser and Server sources but only counted once, deduplication is working correctly.

​
You’ll Know It’s Working When…

Your end-to-end pipeline is validated when a single storefront action produces a matched event in both the Upstack Live Event Stream and Meta Events Manager. The Meta event should show Server as the source, include hashed user data parameters, and arrive within 5 minutes of the storefront action.
If any step fails, refer back to the relevant earlier step:

​
Next Step

What's Next

Your core pipeline is live. Explore what to do next — add more destinations, dive into attribution, or configure advanced identity resolution.

Events not reaching destination

Troubleshoot events visible in Upstack but not arriving at Meta, TikTok, or other destinations.

Duplicate events

Fix duplicate events, inflated revenue, and doubled conversion counts in your pipeline.

EMQ showing zeros

Understand why your Meta Event Match Quality panel may show zero values and how to fix it.