Visits arrive, but no step or conversion

What was observed

TraceLog receives sessions from the site, so TraceLog's code loads, consent was granted and delivery works. No declared step of the conversion path and no conversion has arrived.

The code that starts a session runs on every page; the calls that send the path's steps and its conversion run only where each happens, and they are a separate piece of the install. A site often has the first and not the second: the snippet or the Google Tag Manager tag is in place, and the calls for the path were never added.

TraceLog receives visits from this site, but no step or conversion has arrived yet. Call TraceLog.step where each step happens and TraceLog.conversion where the conversion completes.

What to check

1. Send each step where it happens and the conversion where it completes, with the calls the path's code on Installation and keys gives you.
2. With Google Tag Manager, each call goes in a tag of its own, fired by a Custom Event trigger on the event your site pushes at that moment. See Google Tag Manager.
3. Walk the path in the tab that opens when you press Open my site from the Installation and keys page, through to the conversion.

On Shopify, WooCommerce and PrestaShop the app, the plugin or the module sends the steps and the purchase. Add a product to your cart — on WooCommerce and PrestaShop in the tab that opens when you press Open my site — and if the row still stands, write to info@tracelog.io.

Effect on verification

It reports. The install shows Events are arriving until each step and the conversion arrive, and TraceLog names each element it has not seen.