This page covers what to check in each client store, how to show the client which orders reached Meta, Google and the others, and how access to a client's Tikra works.
Why the numbers differ
A gap between Shopify and an ad platform has a few causes. Each one points at a different fix.
- The browser did not report the purchase. An ad blocker, a privacy setting, a declined cookie banner or a closed tab stops a browser pixel.
- The orders were never meant to count. Point of sale sales, draft orders marked as paid and subscription renewals never passed through the storefront.
- The buyer said no. A buyer who declined marketing cookies is held back from Meta by a setup that follows consent.
- Two senders, or none. A second app or theme code can send the same purchase again. An expired key can stop a server connection without anyone noticing.
- The platform's own rules. Meta's attribution setting and reporting delay change what Ads Manager shows for a given day.
Only the first cause is a tracking failure a server connection fixes. The others are settings, consent or reporting. The full list for Meta is on why Meta shows fewer purchases than Shopify, and the general picture on Shopify server-side tracking.
What to check in each client store
Run the same check in every store. Then you can compare stores and spot the odd one.
| Check | Where | What a problem looks like |
|---|---|---|
| Paid online orders vs. platform purchases, last 7 full days | Shopify orders and the platform's purchase count, in the store's time zone | The platform counts clearly fewer, and consent does not explain it |
| Orders that should not count | Shopify order source | Point of sale, draft or subscription renewal orders in the Shopify figure |
| Who sends purchases | Settings > Customer events (app pixels and custom pixels), theme code, other apps | Two senders for one platform, or more purchases than orders |
| Consent | Settings > Customer privacy and the store's banner | A banner that does not pass the buyer's choice to Shopify |
| Keys and logins | Each platform's connection | A token that stopped working, a disconnected account |
| Test orders | Shopify's test payment gateway | Test orders in a live platform's count |
Two stores with the same gap can have different causes. Write the cause per store before you change anything. The client then sees what you found and what you changed.
Duplicates need their own care. When a store moves from one tracking app to another, both can send the same purchase for a while. See duplicate purchases after switching tracking apps and two Meta pixels on one Shopify store.
How to prove an order reached a platform
The client's real question is "did my sale get to Meta?". A platform's totals cannot answer that for one order. A record per order can.
In Tikra, the Orders page lists the store's paid orders. Click an order to open its proof. Each platform has one line that says what happened, for example "Accepted 3 min after payment." with the pill Received: the platform accepted the order.
Under Proof, each platform that got the order shows Sent to with the time, Value sent, the consent the order was sent with, and the platform's reference with a Copy button. Meta gives a trace ID. For Google Ads the reference is the Google Ads request ID. Google Analytics 4 gives no reference, so its line shows the time only and stays at Sent, because Google gives no confirmation per order.
When Tikra did not send an order, the line says why. "Not sent: the buyer did not allow marketing." is the buyer's choice, not a fault. "Test order, not sent." is a test. An order placed at a point of sale is stored and never sent. That answers most client screenshots: which orders went, which did not, and the reason for each.
If you contact a platform's support about an order, give them the reference from Proof.
For your own reporting, the store owner or an admin can make a read-only API token under Account > Advanced > API tokens > Open. The help names one "Agency export" as an example. It lets a tool read the store's order records as a CSV file and never includes customer details. Revoke stops it at once.
What Tikra does in each store
Tikra is a Shopify app that sends a store's paid online orders from our server to Meta, Google Analytics 4, Google Ads, TikTok, Pinterest, Snapchat, ChatGPT Ads and Klaviyo, as the buyer's consent allows. Each store installs it on its own and pays on its own Shopify invoice.
- Meta: at connect, Tikra reads Meta's own count of purchases for the 7 days before and shows whether anything else already sends them. Go live is one click. For the first 48 hours after Meta goes live, Tikra checks every hour that Meta does not get a second copy.
- TikTok and Pinterest can connect with a login. Snapchat connects with a pixel ID and a Conversions API token.
- Consent: the store chooses Strict, Standard or My store manages consent. The choice is the store's.
- The hourly check: every hour Tikra checks that each platform got at least 97 % of its eligible orders in the last 24 hours, and opens an incident when one falls below.
- Alerts: incidents and key errors go to the addresses on the store's Account page. A store can have 5 addresses, and each starts getting alerts once its owner confirms it. The agency's address can be one of them.
- Guarantee: a written guarantee for eligible orders: at least 97 % reach each platform, fixed within 12 hours or a month's fee credited (Terms, section 8). Terms apply.
A new store starts on the free diagnosis. It shows what is wrong with the store's tracking and sends nothing. That gives you a first read on a new client before anyone pays.
Price: from $99 a month with 500 orders, with setup by our team included. A yearly plan has no charge for extra orders. The first 100 paying stores keep their prices for the lifetime of their subscription (Terms 5.10a). Shopify charges our fees in US dollars and converts them at its own rate where the store's bill is in another currency.
Run the free diagnosis on a client store: install from the Shopify App Store
Access to a client's Tikra
The store decides who works in its Tikra. Our partner page says: "The programme gives you no access to a store's data. A store decides itself whether you may work in its account."
There are two ways in. The store opens both.
Inside the Shopify admin. If the client gives you access to their Shopify admin, open Tikra from Apps. Our help says: "You need no other sign-in there." Shopify's Partner help describes the collaborator route: "After the merchant approves your access, the store is added to your list of stores", and "As a collaborator, the merchant controls which areas of the store you can access."
Outside the Shopify admin, with a login. Our help says: "Each login is an owner, an admin or a viewer. A viewer sees every page but gets no buttons that change settings, choose a plan or send orders again. To add or remove a login, email support@tikratracking.com with your store address and the person's email address." A viewer login suits an agency that reports on a store and does not run its settings.
Two steps stay with the store. The Terms and the Data Processing Agreement are accepted once: "The store owner or an admin of the store does this; on Shopify, a staff account that can open the app may do it only if the store owner allowed it, and by ticking the box that person confirms this." And when our team takes a platform live for a store, "we ask you to confirm the same in writing first": that the store's own purchase tracking for that platform is off.
Frequently asked questions
Does each client store need its own Tikra plan?
Yes. Each Shopify store installs Tikra, chooses its plan on its own Billing page and pays through its Shopify invoice. Plans start at $99 a month with 500 orders.
Can I open a client's Tikra without the client?
No. The store decides. Inside the Shopify admin you need access the store gave you. Outside it, a login is added when someone emails support@tikratracking.com with the store address and the person's email address.
What can a viewer login do?
A viewer sees every page but gets no buttons that change settings, choose a plan or send orders again. It can open each order's proof.
How do I show a client which orders reached Meta?
Open Orders and click the order. Meta's line says whether Meta accepted it, and Proof shows the time, the value sent and Meta's trace ID. An order Tikra did not send says why, for example no consent or a test order.
Can Tikra answer questions in a Slack channel we share with the client?
No. Our help says: "Tikra does not answer in channels shared with another company." Slack is included from the Core plan, and only the store's owner or an admin can connect it, to a channel they choose.
Do you have a partner programme for agencies?
Yes, on our partner page. It gives a partner no access to a store's data: each store decides that itself.
Check a client store
Install Tikra from the Shopify App Store
Check that your tracking works
Related: Shopify server-side tracking · Meta shows fewer purchases than Shopify · Which Shopify orders count in Meta · Meta Conversions API on Shopify · Reading an order's proof
Sources, checked 2026-11-08
- Shopify Help Center: Client transfer stores and collaborations: "After the merchant approves your access, the store is added to your list of stores." and "As a collaborator, the merchant controls which areas of the store you can access."
- Tikra: Partner page (live, HTTP 200): "The programme gives you no access to a store's data. A store decides itself whether you may work in its account."
- Tikra: Get started, Connect Meta, Turn off the store's own tracking, Consent, 97 % check and guarantee, Order proof, Plans and billing, Notifications and contacts, Check it works, Connect Slack, Terms, section 8