Turn off the store's own tracking
Names in bold such as Home, Orders, Platforms, Events, Incidents, Billing and Help are pages and buttons of the Tikra app. You open it from Apps in your Shopify admin.
If the store's own connection to a platform still sends purchases, the platform counts each purchase twice: once from that connection and once from Tikra. Turn it off before the platform goes live in Tikra, whether it is Meta Conversions API for Shopify or GA4 purchase tracking on Shopify. For Meta, Tikra checks this for you with a check before sending. The steps below are for a Shopify store. On a WooCommerce store, the purchases come from a WordPress plugin: see WooCommerce stores further down.
What turning it off stops
The store's own connections send more than purchases. The Facebook & Instagram channel, the Google & YouTube channel and the TikTok, Pinterest and Snapchat apps also send page views, product views, add to cart and checkout events. None of them has a switch for purchases alone. When you turn one off, all of these events stop, purchases included. On WooCommerce, some plugins have a switch for the purchase event alone, so you can keep the other events: see WooCommerce stores.
What Tikra sends today:
| Platform | Tikra sends | What you lose when you turn off the store's own connection |
|---|---|---|
| Meta | Purchases only. | Page views, product views, add to cart, checkout started and payment info in Meta. Retargeting audiences, catalog ads and Meta's campaign optimisation use these events. |
| Google Analytics 4 | Purchases. | Page views, sessions and traffic sources, product views, add to cart and checkout steps in Google Analytics 4. Without the store's own Google Analytics tag, Google Analytics 4 also cannot show where buyers came from. |
| Google Ads | Nothing: Google Ads is not offered yet. | Every conversion the store's own conversion tracking reports, purchases and the others. |
| TikTok, Pinterest, Snapchat | Nothing: they are not offered yet. | Page views, product views, add to cart and checkout events in that platform. |
Because of this, Go live asks you to tick a box that says you understand that the platform then gets only purchases from Tikra. You tick it once for each platform. When our team goes live for you, we ask you to confirm the same in writing first.
Meta: the check before sending
A new Meta connection starts in the check before sending. The card shows the badge Check before sending.
- During the check, Meta gets nothing from Tikra. The orders are held. On the Orders page they show Skipped with "Held during the check before sending".
- Every day Tikra reads Meta's own count of Purchase events and compares it with the paid orders it expected to send to Meta. Any purchase Meta counts in this time came from another connection.
- Tikra decides after at least 48 hours, once the check covers full days (UTC) with at least 10 expected orders.
What happens then:
| Meta counted | Result |
|---|---|
| Meta counts almost none of the expected orders | Nothing else sends your purchases. If you ticked I understand that Meta then gets only purchases from Tikra earlier (an older connection), Meta goes live on its own. Tikra also sends the held orders from the first day that showed this count onward. Home shows a notice that starts with "Meta is live." If you have not ticked it, Meta stays in the check and Home shows a notice that starts with "Meta is ready to go live." Click Go live and tick the box there. |
| Meta counts about as many as expected | Another connection still sends your purchases. Meta stays in the check. The card shows Meta still gets purchases from another connection with the steps below, and Home shows a notice with Meta's count. Tikra checks again every day. Once these purchases stop, Home says Meta is ready, and you start with Go live and the tick. |
| Meta counts some of them | Meta stays in the check. If the card says Meta still gets purchases from another connection, follow the steps below. Otherwise email support@tikratracking.com. |
The box is on the Go live step of the Meta card, above the button. Tikra sends nothing to Meta before you tick it there.
If Tikra cannot read Meta's count, email support@tikratracking.com. You can go live yourself at any time.
Turn off the store's own Meta tracking
- In your Shopify admin, go to Sales channels > Facebook & Instagram.
- Click Settings, then Data sharing settings.
- In the Customer data sharing section, turn customer data sharing off.
- Also remove any other Meta pixel code that sends Purchase (theme code, Google Tag Manager, another app).
This stops all the events the channel sends to Meta, purchases and the others (see the table above).
Go live yourself
If the store's own Meta purchase tracking is already off, you do not need to wait for the check.
- Go to Platforms and click Go live on the Meta card.
- Under Date you turned it off, choose one option:
- Just now: send new orders only. Tikra sends new paid orders. The orders held during the check stay unsent.
- Before I connected Meta here: also send the orders held during the check. Tikra also sends the held orders, as far back as Meta accepts them (7 days).
- Tick I understand that Meta then gets only purchases from Tikra above the button, if you have not ticked it before. Nothing is sent to Meta until you do.
- Click Go live.
The card says Meta is live. Choose the second option only if the store's own Meta tracking was off during the whole check. If it was on for part of the time, Meta already counted some of those orders, and sending them again counts them twice.
Google Analytics 4: confirm when you connect
Tikra cannot read the Google count today, so there is no check before sending. The Google Analytics 4 card asks you to tick one box before it saves: The store's own Google Analytics 4 purchase tracking is off. I understand that Google Analytics 4 then gets only purchases from Tikra. Google Analytics 4 then gets orders from Tikra at once.
The Google & YouTube sales channel has no switch for purchases alone. Its Google Analytics connection sends every event, so do not remove it to stop its purchases. Choose one of these:
- Keep the store's own Google Analytics connection. It keeps sending page views, sessions, product views, add to cart and checkout steps, and its own purchases. Then do not connect Google Analytics 4 in Tikra, or pause it on its card.
- Stop only its purchases. If your Google Analytics tag runs in Google Tag Manager, a custom pixel or your theme code, remove only its purchase event there, and keep the page view and the other events. Then connect Google Analytics 4 in Tikra.
Also remove any other Google Analytics tag that sends purchase events (theme code, Google Tag Manager, a custom pixel).
Google Ads
Google Ads is not available in Tikra yet. Keep the store's own Google Ads tracking on.
WooCommerce stores
A WooCommerce store has no sales channels. Its events reach Meta, Google Analytics 4 and Google Ads through a WordPress plugin, or through a Google Tag Manager container. The plugins differ: some have a switch for the purchase event alone, and you keep the other events. The others only turn the whole pixel off, which also stops the page views, add to cart and checkout events (see the table above). The Tikra cards, notices and emails give the same steps for a WooCommerce store. If the plugin file is version 0.3.0 or later, it reports the names of the plugins active on your site once a day, and the cards, notices and emails name your store's own plugin. Until it has reported, or with an older plugin file, they name the common ones. The paths and setting names below were checked in each plugin's documentation on 30 September 2026.
Meta on WooCommerce
| Plugin | Purchase alone? | What to do |
|---|---|---|
| PixelYourSite (free and Pro) | Yes | Go to PixelYourSite, open the WooCommerce tab. Under Track Purchases, turn off Enable the Purchase event on Facebook. In PixelYourSite Pro, untick Meta (Facebook) under Send Purchase to instead. Keep Enable Pixel on: the pixel keeps sending page views, product views, add to cart and checkout. |
| Meta for WooCommerce | No | Its settings (Marketing > Facebook) have no switch for the purchase event and no pixel switch. Its documentation turns the pixel and the Conversions API off with the filter facebook_for_woocommerce_integration_pixel_enabled in your site's code (ask your developer). This stops all the events it sends to Meta; the catalog and the connection stay. |
| Pixel Manager for WooCommerce | No | Go to WooCommerce > Pixel Manager, open the Tracking Pixels tab. Under Meta, clear the Pixel ID and save: this stops all the events it sends to Meta. To stop only the purchase, your developer can use its filter pmw_conversion_prevention in your site's code instead. In Pixel Manager Pro with server-side events on, also pmw_skip_s2s_purchase_event. |
| Meta pixel for WordPress | No | Its settings are under Settings > Meta. Its WooCommerce events stop only when you disconnect the pixel there or deactivate the plugin. This stops all the events it sends to Meta. |
| GTM4WP (Google Tag Manager) | Yes, in Tag Manager | In Google Tag Manager, pause or remove only the tag that sends the Meta Purchase event. Do not turn off Track e-commerce in the GTM4WP settings: it is the master switch of the whole WooCommerce integration. |
Also remove any other Meta pixel code that sends Purchase (theme code, Google Tag Manager, another plugin). Then click Go live on the Meta card and tick I understand that Meta then gets only purchases from Tikra there. If you turned the whole pixel off, Meta loses the other events (see the table above).
Google Analytics 4 on WooCommerce
Keep your Google Analytics plugin or tag on. It sends the page views, sessions and traffic sources, and without it Google Analytics 4 cannot show where buyers came from. Stop only its purchase event:
| Plugin | Purchase alone? | What to do |
|---|---|---|
| Google Analytics for WooCommerce | Yes | Go to WooCommerce > Settings > Integration > Google Analytics. Untick Purchase Transactions and save. Keep the Measurement ID and the other event boxes as they are. |
| PixelYourSite (free and Pro) | Yes | Go to PixelYourSite, open the WooCommerce tab. Under Track Purchases, turn off Enable the purchase event on Google Analytics. In PixelYourSite Pro, untick GA4 under Send Purchase to instead. Keep the Google Analytics tag itself on: it keeps sending page views and the other events. |
| Site Kit by Google | No | Go to Site Kit > Settings > Connected Services > Analytics and click Edit. Turn off Plugin conversion tracking. This stops the WooCommerce events Site Kit sends to Google Analytics 4 and Google Ads (add to cart and purchase). The Google Analytics tag and its page views stay on. |
| MonsterInsights | No | Go to Insights > Addons and turn off the eCommerce addon. This stops the shopping events it sends (product views, add to cart, checkout and purchases). Keep MonsterInsights itself on: its Google Analytics tag keeps sending page views. |
| GTM4WP (Google Tag Manager) | Yes, in Tag Manager | In Google Tag Manager, pause or remove the Google Analytics 4 tag that sends the purchase event, or remove purchase from its trigger. Keep the Google Analytics tag and its page views. Do not turn off Track e-commerce in the GTM4WP settings. |
| Pixel Manager for WooCommerce | No | Keep its Google Analytics Measurement ID: clearing it stops page views and every other event too. To stop only the purchase, your developer can use its filter pmw_conversion_prevention in your site's code. In Pixel Manager Pro with server-side events on, also pmw_skip_s2s_purchase_event. |
If you cannot stop only its purchases and want to keep the plugin, do not connect Google Analytics 4 in Tikra, or pause it on its card. Also remove the purchase event from any other Google Analytics tag (theme code, Google Tag Manager, another plugin), and keep its other events.
Google Ads on WooCommerce
Google Ads is not available in Tikra yet. Keep the store's own Google Ads tracking on.
Conversios and other plugins
Conversios (Conversios > Pixel & Analytics, Pixel Integrations in some versions) says its GA4, Google Ads and Meta events can be turned off in its settings, but its documentation names no purchase switch. If you find one for the purchase event, turn only that off. If you do not, clearing the pixel ID stops all the events it sends to that platform; for Google Analytics, keep the Measurement ID and pause Google Analytics 4 in Tikra instead. For any other plugin: turn off its purchase event if it has a switch for it. If it has none, turning its pixel off stops all the events it sends. Never remove the Google Analytics plugin or tag itself.
TikTok, Pinterest and Snapchat
TikTok, Pinterest and Snapchat cannot be connected yet, so there is nothing to turn off for them.
Klaviyo: nothing to turn off
Klaviyo is not offered to new stores. A store that connected it earlier keeps it: you can pause it, resume it and save a new key. If you disconnect it, it cannot be connected again and its card is removed. Klaviyo keeps the orders from Tikra apart from the orders of its own Shopify app, as a separate metric, so no purchase is counted twice. Keep Klaviyo's own Shopify app on: flows built on its Placed Order metric use it.
Platforms connected on the free diagnosis
On the free diagnosis no card asks for these confirmations. Every platform you connect stays in the check and gets nothing from Tikra, so keep the store's own tracking on. Orders paid on the free diagnosis are not held for later: Tikra keeps only what the diagnosis needs and never sends them. Once you choose a plan:
- Meta's check before sending runs as described above.
- The other platforms wait for Go live on their card. Google Analytics 4 asks you then to confirm that the store's own tracking is off, and to tick that you understand what that stops. Turn it off just before you click Go live.
- Klaviyo, on a store that connected it earlier, needs no confirmation. Under Orders held during the check, choose Send new orders only or Also send the orders held during the check, then click Go live.
Other tags
Purchases can also reach a platform from code outside the sales channels:
- code in your theme;
- a Google Tag Manager container;
- a custom pixel. Custom pixels are listed in your Shopify admin under Settings > Customer events;
- another app.
Remove the purchase event from each of them for every platform Tikra sends to. Keep their other events. Leave Tikra's own pixel connected. It sends no purchases to any platform.
After Meta is live: the daily duplicate check
Every day Tikra compares Meta's count for the previous day (UTC) with the orders it expected to send there. If Meta counted clearly more purchases than the orders Tikra expected to send there:
- Home shows a notice that starts with "Meta counted ... Purchase events", followed by the steps to turn off the store's own tracking and what that stops.
- The Incidents page shows an incident with the cause "A change on your store". Its 12-hour clock does not run, because the fix is on your side.
The incident closes on its own after the first day where Meta's count no longer exceeds the expected orders.
Only Meta has this daily count today. For the other platforms, Tikra relies on your confirmation.
Still stuck? Email support@tikratracking.com with your store address and the platform name.