Using WeTracked or TrackBee with LatchPay

Why a purchase can count twice

WeTracked and TrackBee send a purchase to your ad platforms for every Shopify order. LatchPay creates a Shopify order for every paid checkout, and it can send the purchase itself too (from the checkout pixels and, with server-side tracking, from its server). The two purchases carry different event ids, so the platform cannot tell they are the same order.

So for each platform, exactly one of them should send the purchase. Each platform card on Tracking has the switch Another app already sends purchases to the platform, with Do you use WeTracked or TrackBee? right under it. This article has the same steps. LatchPay keeps sending the checkout steps either way: the other app never sees LatchPay's checkout, so those never count twice.

WeTracked

1. In WeTracked, set Type of checkout to External Checkout. You find it in the app.wetracked.io dashboard under your store, or in Shopify admin under Apps → wetracked.io Connect. This setting is for your whole store: orders from Shopify's own checkout are then also counted when they are created, before a manual or pending payment is received.
2. Nothing to do in LatchPay for the cart token: every LatchPay order already carries the shopify-cart-token WeTracked needs to match the order to the visit.
3. Turn on Another app already sends purchases to … when WeTracked sends purchases to that platform. Do the same on the card of every platform WeTracked sends to.

With External Checkout, WeTracked sends the purchase when LatchPay creates the order (LatchPay only does that once the payment is confirmed) and uses the cart token to credit it to the visit that brought the buyer.

TrackBee: choose one route

TrackBee has no external-checkout setting: it sends every Shopify order. Pick one route for your whole store; it applies to every platform card.

Both routes count every purchase once. The tag filter only applies to orders from the moment you save it. Excluded orders still show in TrackBee's own dashboard.

Which route to pick: one route for your whole store, because TrackBee's tag filter applies to every platform it sends to. Route 1 keeps TrackBee as the one source for all your orders, also those paid through LatchPay, on every platform TrackBee sends to. LatchPay copies your cart's data, TrackBee's included, onto the order; whether TrackBee then credits the purchase to the ad is something to check in TrackBee with a test order. Route 2 lets LatchPay's checkout pixels and server events report LatchPay's orders to Meta, TikTok, Google Analytics 4, Pinterest and Snapchat, as for a store without TrackBee. TrackBee then sends LatchPay's orders nowhere, so Google Ads, Klaviyo or any other platform LatchPay does not send to no longer gets them.

If you do neither

The same happens when you connect the app to one more platform later and do not change that platform's card. Check the switch on every card after such a change.

What LatchPay writes on the order

Every Shopify order LatchPay creates carries, besides the payment:

• the tag latchpay, which TrackBee's filter (Route 2) looks for;
• the note attribute shopify-cart-token (under Additional details), the storefront cart's token that WeTracked reads;
• every attribute your storefront cart had when the buyer went to checkout, exactly as Shopify's own checkout copies them: tracking data of apps such as TrackBee (also the hidden ones whose name starts with an underscore), gift notes, delivery dates, UTM fields. A value that is not text is written as text (a list or a group of values as JSON).

LatchPay's own attributes always win: a cart attribute never replaces latchpay_session, the payment id, shopify-cart-token, the gift message, the post-purchase links or the answers to your custom fields; a cart attribute with one of those names is left out. An order holds at most 250 attributes, the most a Shopify cart can have. A post-purchase second order carries no cart attributes and no cart token: it was never a storefront cart, and the first order carries them.

When the buyer changes the cart after opening the checkout (in another tab, or after going back to the store), the next checkout gets the cart's new attributes.

Check it with a test order

• Place a small test order through LatchPay after setting things up.
• In Shopify admin, open the order: the tag latchpay and, under Additional details, shopify-cart-token and your cart's attributes are there.
• A few minutes later, look at the Purchase events for that order in each platform's events tool: one purchase per platform. Two means the switch and the app's setting do not match yet; none means both are holding back.