Conversion event is missing
At least one declared step has arrived and no conversion has. Complete a test conversion and check that the event is sent from the confirmation page.
What was observed
TraceLog has received at least one declared step, so TraceLog's code is installed, consent was granted and delivery works. No conversion has arrived.
The conversion often fires on a page that behaves differently from the rest: an order-received page reached by redirect, a thank-you page shown after a payment provider hands control back, or a confirmation in a modal with no navigation. Code that runs everywhere else may not run there.
Trigger the declared conversion and check that its event is sent after the preceding steps.
What to check
- Complete the conversion yourself on a real environment, in the tab Open my site opens from the Installation page.
- Confirm the call runs on the confirmation page. If that page is a redirect from a payment provider, TraceLog's code has to be initialised there too.
- If the page can be closed before the call runs — a shopper who leaves at the moment of payment — confirm it from your backend instead. See the server API; one order number reconciles both sides into one conversion.
- Check the conversion's name matches the plan exactly.
Effect on verification
It reports. The install stays in receiving until the conversion arrives, and
TraceLog names the element it has not seen.