Store events
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.
Besides purchases, Tikra's pixel counts the steps before a purchase on Shopify stores: page views, product views, add to cart, checkout started and payment info. These are "store events". This article explains which ones are counted, the Events page, and the notices about them.
What store events are
- Page views, Product views, Add to cart, Checkout started and Payment info from your storefront and checkout.
- Only from visitors who allow marketing and have not opted out of the sale or sharing of their data. Your consent mode (strict or standard) does not change this: without a clear marketing consent nothing is counted for a platform, and such events appear only as a number under Without consent on the Events page.
- What visitors type into your store's search box is never collected.
- Store events start with a plan. On the free diagnosis Tikra only counts some of them by name and day, from customers who allow analytics, and sends nothing.
- Store events exist on Shopify stores only, where our web pixel collects them. A WooCommerce or custom store has no store events and no Events page. Its Meta card still asks for one tick on the Go live step, about what turning off the store's own Meta purchase tracking stops: on a WooCommerce store, its Meta plugin; on a custom store, whatever else sends purchases to Meta.
- Store events are not part of the 97 % check. It covers purchases only. They do not count toward your plan's order limit.
Store events are counted, not sent to any platform. The platform's card and the Events page say so.
Choose which store events are counted
- Go to Platforms.
- On the Meta card, click Store events to open it (a line under it shows what is on now). Each event has a tick box.
- Tick the events to count for Meta, and untick the others.
- Click Save store events.
All five are ticked when you connect Meta. An event you untick for every platform is no longer collected by the pixel at all.
Google Analytics 4 gets only purchases from Tikra. Its card says so. Page views, product views, add to cart and checkout steps reach Google Analytics 4 only from the store's own Google tag, if it is still on. If you removed the store's own Google Analytics connection when you connected Google Analytics 4 in Tikra, it gets none of them. Google Ads, TikTok, Pinterest and Snapchat are not available yet.
While a platform is paused or its key stopped working, no store events are counted for it; its card says so instead of the list. A store without a plan sees why nothing is collected yet; the choices it makes apply once a plan runs.
The Events page
Open Events in the app menu. The top line tells you how store events are doing:
| Line | What it means |
|---|---|
| Store events are arriving. | Tikra received store events since yesterday (UTC). |
| No store events yet. | Nothing has arrived in the last 7 days. They show up a few minutes after visitors who allow marketing browse your store. |
| No store events arrived since (a date). (A number) arrived in the days before. | Fewer than 100 arrived in the last 7 days and none since yesterday. With few visitors this happens; the counts below show what did arrive. |
| No store events arrived since (a date), although (a number) arrived in the days before. | At least 100 arrived in the last 7 days, then they stopped. Check that the Tikra app pixel is connected in your Shopify admin under Settings > Customer events. If it is, email support@tikratracking.com with your store address. |
| Store events stopped arriving. | Check that the Tikra app pixel is connected in your Shopify admin under Settings > Customer events. If it is, email support@tikratracking.com with your store address. |
| Store events need a plan, are paused by our team, or no platform counts them. | The reason is in the line. Nothing is collected until it changes. |
| Your store reached its monthly limit of store events... | See Monthly limit below. Nothing is collected until the date in the line. |
Below it, two periods: since yesterday and the last 7 days. The counts are kept per day in UTC, so each period shows its first and last day. The diagnosis on Home counts your store's own days instead, so its days can start a few hours apart from these.
For each period:
- Received: store events our server received from your store.
- Without consent: events that were not counted for any platform or sent, because the visitor had not allowed marketing. Only their number per event is kept.
- Filtered out: bots, requests from other websites, repeated requests and requests over the limits.
Then, for each platform:
- Sent: store events the platform got from Tikra. Today it shows none.
- Counted, not sent: store events Tikra counted for the platform and did not send.
- Repeat checkouts: checkout started or payment info again for the same checkout within 24 hours. The first one counts as the event; the others are counted here.
- Not delivered: the platform refused them, did not answer, or limited our requests for more than an hour. They are not sent again.
For the last 7 days the page also shows how many events carried each kind of matching data, such as the Meta browser ID, the ad click ID and the IP address.
Monthly limit
Each store has a monthly limit of store events: 5,000 store events for each order of your plan's order limit, or of your online orders that month when you have more, and never fewer than 5,000,000. On Start (1,000 orders) that is 5,000,000 a month, on Core (3,000 orders) 15,000,000 and on Full (10,000 orders) 50,000,000. Real visitors make far fewer: a store where 1 visit in 100 ends in an order makes about 400 to 1,300 store events per order. The limit is counted per calendar month in UTC, and an event sent to several platforms counts once. The limit stops bot traffic from filling your platforms with made-up visits. Only store events sent to a platform count; store events Tikra only counts do not.
When your store reaches the limit, Tikra stops collecting store events until the first day of the next month (UTC). Purchases are not affected: orders are still sent as usual. The Events page says so, and the addresses on the Account page get one email (see Notifications and contacts).
If real visitors caused it, email support@tikratracking.com with your store address and we raise the limit for your store.
Notice: Meta counted more store events than we sent
When Meta gets store events from Tikra, Tikra compares every day, for the day before, Meta's own count of page view, product view, add to cart, checkout started and payment info events from servers with what Tikra sent. Home shows a notice when Meta counted more than 1.5 times as many from servers as Tikra sent (at least 50 sent). Another server connection sends them too, for example another app or a server-side tag, so Meta counts them twice.
To fix it:
- Find the other connection that sends store events to Meta from a server: another tracking app, a server-side Google Tag Manager container, a Conversions API connection a developer set up for your store, or the Facebook & Instagram channel if its data sharing is set to Maximum.
- Turn its store events off. Or untick those events for Meta in Tikra (see "Choose which store events are counted" above).
The check runs again every day.
Still stuck? Email support@tikratracking.com with your store address and what the Events page shows.