Check your Shopify storefront’s tracking before installing another app
Before adding another tracking app, make a list of what your store already uses. Converlay’s free storefront scan can help you start that list. It reads one public landing page and looks for known tracking references in the HTML. You do not need an account, an app installation or Shopify admin permissions to run it.
Start with your own store
- Open the free storefront scan and enter your store’s public domain.
- Compare the detected tools with the apps, pixels and tag managers you have configured.
- Keep the result as a starting point for checking setup. A missing tool in this scan does not prove that it is absent from your store.
Read the results as clues
A detected pixel or tag is a reference found in the page markup. The scanner does not run your store’s JavaScript or confirm that a purchase event fired.
For recognised consent tools, the result includes the catalog’s documented Shopify consent integration. It does not test your banner’s settings or prove that an individual visitor’s choice reached Shopify.
Scripts loaded later, tags inside a tag manager, checkout tracking and server-side delivery may be outside this scan’s view. It cannot establish lost revenue, delivery rates, duplicate purchases or ad attribution.
Choose the next check
If you recognise both Meta and a tracking app, check which integration sends purchases before adding another sender. Their presence alone does not prove duplicate reporting. For a reporting discrepancy, compare Shopify orders, captured events and destination delivery evidence for the same date range. An accepted event does not prove that an advertising platform attributed a conversion.
See a clearly labelled sample purchase report
Know the Free plan’s limits
The Free plan includes 50 tracked orders per 30-day cycle, one destination and seven days of analytics history below the order limit. At 50 orders, destination forwarding and alert emails pause; analytics and health reports show today only. Upgrade or wait for the cycle to reset to restore access. Events continue to be captured and stored during a forwarding pause, but are not automatically sent later. An existing grace period can delay the forwarding pause; the reporting and alert limits still apply.
When you are ready to try delivery, start with one destination, follow its setup checks and inspect the resulting event evidence. Keep the storefront scan and the installed app’s delivery checks separate: they answer different questions.