Documentation
Guides to install TraceLog, send the conversion path and resolve what blocks verification.
Install and use
Installation on each platform, the public methods, and what to do when verification is blocked.
Install on WooCommerce
The plugin sets up the purchase path and connects with a pairing code.
Install on PrestaShop
The module, downloaded from the guide until the PrestaShop Marketplace lists it.
Install on Shopify
The app sets up the purchase path; you confirm it.
Install with a script tag
Paste the snippet on your site and send the path you define.
Install through Google Tag Manager
The same snippet, as a tag in your container.
Install with npm
Import the package into your own build.
Use the SDK reference
Check the public methods, payloads and consent controls.
Identify Google AI Mode and Gemini carts
What to add to the link your store returns, and when to add nothing.
Resolve a blocked verification
Find the exact condition, its effect and the next action.
Evaluate TraceLog
What TraceLog records, what it keeps, and the limits of each plan.
What TraceLog verifies
See how the conversion path you define becomes the reference for every check.
Get an alert when conversions stop arriving
When an alert comes, what it says, and the Monday digest that arrives regardless.
Follow an illustrative record
See a fictional path, the day a step goes missing and the figures it leaves incomplete, before you install.
Plans and their limits
Compare what each plan opens, its monthly sessions and its projects.
Plans and billing
The session limit and what pauses past it, changing plan, VAT and cancelling.
For agencies
A project per client, the client contact who sees only theirs, and the portfolio.
Ask from your own assistant
AI explains. TraceLog computes. An AI assistant you connect asks the same read-only questions TraceLog does.
Conversions and sessions, row by row
A connector of your own copies each conversion and session into your data store over HTTP, picking up where it left off.
Privacy and data
Review what is captured, excluded, stored and retained.
Security and access controls
Review tenant separation, credentials, request limits and retention.
Server-confirmed conversions
Understand how browser and server evidence is counted once.
Confirm conversions from Stripe
Have Stripe confirm each payment through a signed webhook, with no connection to your account.
Why TraceLog differs from GA4 or Meta
Each tool counts its own record with its own rules; here is what TraceLog’s is.
All documentation
Installation, reference and diagnostic guides, by category.
Install
Reference
- Tracking checklist after a migration
- SDK reference
- Server API
- Confirm conversions from Stripe
- Asking from your own assistant
- Conversions and sessions, row by row
- The path a conversion takes
- Privacy and data
- Get an alert when conversions stop arriving
- TraceLog for agencies
- Plans and billing
- Why TraceLog differs from GA4 or Meta
- GA4 not tracking purchases: how to check
- Conversions dropped suddenly: sales or tracking?
- GA4 double counting purchases: how to check
- Meta pixel not active: how to check
- Google Ads "Awaiting conversions": how to check
- WooCommerce orders missing in GA4 after payment
- Google AI Mode and Gemini carts
- AI referral sources: hostnames and UTM values
Diagnostics
- No signal from TraceLog on the verification page
- TraceLog is waiting for consent
- Invalid TraceLog configuration
- TraceLog is rejecting events
- Visits arrive, but no step or conversion
- Conversion event is missing
- Conversion is missing its identifier
- Duplicate conversion identifier
- An identifier arrived with another value
- Conversion arrived without a declared step
- Conversion arrived again under its identifier
- Conversion value needs review
- No conversions recorded on one device type
- The server confirmation is missing
- Stripe's payments match no conversion
- TraceLog service issue