Jump to a section
The event gap created by external checkout
Storefront tracking and completed checkout tracking are not automatically the same thing. A Shopify theme pixel can record that someone viewed a product or clicked Add to Cart, but it might not observe the payment confirmation on a separate checkout domain. Payment events must be connected to the authoritative outcome.
Check each integration on its own. A green “connected” indicator cannot replace a real test event observed in the relevant ad platform.
Already using WeTracked with Shopify?
Voss supports WeTracked External Checkout matching by passing the original Shopify cart token to eligible paid orders under shopify-cart-token. When WeTracked owns Purchases, you can keep Voss Meta/TikTok InitiateCheckout and configured Google Ads Begin Checkout events while suppressing Voss Purchase for that same destination.
Follow the WeTracked setup and deduplication guide → · Explore WeTracked-compatible checkout →
Which events should you validate?
| Event | When to check it | What to verify |
|---|---|---|
| PageView / ViewContent | Page and product view | Expected browser route and product identifiers. |
| AddToCart | Product added to cart | Product variant, quantity and correct value. |
| InitiateCheckout | Buyer begins checkout | One meaningful start, not a paid purchase. |
| AddPaymentInfo | Payment information is entered or attempted, where supported | Appropriate triggering; don't treat an attempt as success. |
| Purchase | Only after payment confirmation | Matching order amount, currency, and one logical purchase. |
How to test Meta Pixel and Conversions API
- Open Meta Events Manager and select the pixel or dataset connected to the store.
- Use the available Test Events tools and open your real storefront as a buyer.
- Visit a product, add it to cart, and continue to the external checkout.
- Complete an authorized test purchase where supported, then check for a Purchase event after successful payment confirmation.
- Where browser and server Purchase events are both sent, confirm they share the intended event identifier and are deduplicated rather than counted as two purchases.
- Compare the reported amount and currency with the actual paid order; inspect warnings about missing parameters or matching quality separately.
Important: Seeing an event in Test Events confirms ingestion, not necessarily future ad attribution or perfect event-match quality. Browser privacy settings, consent and attribution rules can affect reported results.
How to test TikTok Purchase tracking
- Open TikTok Events Manager and choose the correct pixel or events connection.
- Follow the storefront-to-checkout journey from a normal shopper session, including a test within TikTok's in-app browser if your ads use it.
- Confirm checkout-start and Purchase events appear with sensible values and currency.
- Investigate missing or duplicate events. Where browser and server tracking overlap, confirm the platform can deduplicate them using consistent event identifiers.
- Repeat on mobile and with consent settings relevant to your target markets.
Do not equate an event being sent with TikTok attributing it to a specific campaign. Those are different checks.
How to test Google Ads Purchase tracking with Voss
For complete setup instructions, see the Google Ads purchase conversion tracking guide.
Google Ads works differently from Meta and TikTok in Voss today: it uses a consent-aware browser conversion tag for confirmed purchases, not a server-side Events API and not a full PageView/AddToCart event feed.
- In Google Ads, open Goals → Conversions and choose your website Purchase conversion action. Copy its Conversion ID (starting with
AW-) and Conversion Label. - In Voss, open Dashboard → Tracking → Google Ads, or choose Google Ads during optional onboarding. Enter the two values, make sure the same conversion action is not already being sent by Shopify or another checkout tool, then enable tracking.
- Open your Shopify storefront as a real buyer, grant applicable marketing consent, add a product to your cart and continue to Voss checkout. Test the actual storefront-to-checkout path rather than opening a thank-you URL directly.
- Complete an authorized paid order. Voss queues the Google Ads conversion with the verified purchase value, currency and stable Shopify order transaction ID. Failed or pending payments must not count as purchases.
- Use Google Tag Assistant to inspect the conversion event and Google Ads to check receipt. Test another browser and a consent-denied journey. Voss cannot confirm Google's receipt from its own dashboard, and tag delivery is not the same as campaign attribution.
Important: Browser privacy features, consent and ad click attribution affect what Google Ads ultimately reports. Voss's transaction ID helps Google deduplicate repeated Purchase tags, but you must also avoid independent Purchase tags sending the same conversion action from Shopify.
Why tracking may disagree with Shopify sales
- Events are duplicated: both Shopify/theme scripts and external checkout scripts may independently send the same purchase.
- Wrong firing condition: a payment attempt or thank-you navigation may be counted before payment was verified.
- Different attribution: reporting windows, consent, browser blocking and cross-device journeys change what ad managers attribute.
- Missing shopper data: event matching can be limited by consent or missing eligible parameters. Do not send sensitive data without an appropriate legal basis.
- Order-sync delay: the payment can be confirmed before the Shopify order is visible. Reconcile against the confirmed payment, not only page navigation.
How Voss fits into the event flow
Voss supports checkout analytics, Meta Pixel/Conversions API, TikTok Pixel/Events API and Google Ads browser-based Purchase conversions for its separate Shopify-to-Whop checkout. Google Ads currently tracks completed purchases, not the full storefront event catalog handled by Meta/TikTok integrations. Purchase eligibility is based on verified payment and Shopify order confirmation—not merely reaching a thank-you page.
You should still verify your own pixel configuration, consent behavior, deduplication and final event values before buying traffic. Supported integrations and exact event coverage can change, so check the current dashboard and product documentation.
Run the full checkout launch checklist → · Connect Shopify and Whop → · Start Voss setup →
Keep Shopify. Use your own Whop account for checkout.
Your storefront stays where it is. Customers pay through a branded checkout, and successful paid orders are sent back to Shopify for fulfillment.
Whop processing fees, eligibility checks and account rules still apply.