1. Check monitoring and store access.
Open Blokk Bot from the correct store in Shopify admin. In Settings, check the store agreement and Data collection status. If monitoring is paused, turn it on when you are ready and the required consent setup is in place. Wait for the saved state before continuing.
If the app asks you to reconnect, reopen it from Shopify admin or use its reconnect action. If your store has a password page, the browser making the visit must pass that page first. Seeing your store while signed into admin does not give a separate test browser the same access.
2. Check the storefront and shopping-event connections.
In Settings, select Check connection. Open Finish connection setup or Manage connections to see the connection actions.
- Storefront: save the Blokk connection, open the theme editor, enable the Blokk app embed in your published theme and save. A saved connection alone does not enable the theme embed.
- Shopping events: connect the app’s shopping events and confirm the connected state. These provide supported cart and checkout observations separately from the storefront connection.
Shopify’s theme editor controls app embeds. Check the embed again after changing your published theme; Shopify does not activate the old theme’s apps in the new theme automatically. App pixels are listed under Shopify’s Settings → Customer events. Use that view to inspect permissions or test the pixel with Shopify’s Pixel Helper if the connection still needs attention.
3. Make one ordinary visit with the required consent.
Open the actual storefront in a separate browser tab. Pass the store password if needed, make your consent choice, then view a public page and a product. You do not need to place an order to check basic storefront collection. Return to Blokk’s Dashboard to check for new activity.
Shopify loads an app pixel only when the visitor permissions match the pixel’s required privacy settings. A declined or unresolved consent choice can therefore explain missing activity. Keep those preferences intact: a successful test should respect them, not bypass them. See Shopify’s pixel privacy documentation.
Browser extensions, network errors or scripts that do not run can also prevent observations. Try your own ordinary browser as a comparison, with the same deliberate consent choice. Missing browser events do not prove that the visitor was a bot.
4. Compare the right time and measure.
- Choose a period that includes the visit. The latest activity time describes received events. Refreshing the Dashboard does not create a new visit.
- Separate events, sessions and findings. One visit can produce several events. Ordinary sessions can contribute to totals without creating a finding card.
- Check for marked test activity. Owner-marked tests are excluded from normal totals. The Dashboard notes these exclusions; use the private test report to inspect that run’s receipts.
- Read any capacity warning. A reached allowance can reduce collection. Follow the app’s status and reset information; repeating the same visit is not a remedy.
Blokk’s observed sessions are not a replacement for Shopify Analytics. Collection sources and consent can differ. Compare the same source and period before treating different totals as a fault.
5. If you ran a scripted test, check what actually completed.
Read the test report in order: attempts, successfully loaded pages, accepted observations, then findings. A run can finish with every visit stopped at a password page. In that case there is no storefront behaviour for Blokk to assess.
The private Blokk Bot Test workspace uses its own browser sessions. Password-protected stores need a prepared guest profile; account scenarios need the appropriate signed-in test profile. A permitted account also needs a separately configured exception. Treat saved profiles as sensitive access files and keep them out of support messages. Test only stores you control or have permission to assess.
A crawler that never runs JavaScript does not use this browser observation path. Concealed automation may leave too little evidence for a finding. Those are coverage limits to record, not successful detections to add to your totals. A page-visiting test also cannot prove the signed-in cart policy or an actual checkout restriction.
6. Share a small, useful support report.
If activity is still missing, contact support with the store domain, approximate visit time and time zone, the connection states and the exact error shown. Say whether the real page loaded, monitoring was on and the required consent was granted. Share a screenshot of the status if helpful, without customer information, passwords, session files or access tokens.
Monitoring does not enable checkout protection. Once observations are arriving, the account protection guide explains eligible previews, approval and recovery. For first-time setup, use the getting-started guide.