Tracking overview
Dialog tracks user behavior to attribute conversion, measure engagement, and feed the dashboard you use to drive decisions. Most of it is automatic. A few site-level events (add-to-cart and checkout that happen outside the Dialog assistant) need to be wired depending on your install.
What’s automatic vs what you wire, per install path
Section titled “What’s automatic vs what you wire, per install path”| Install path | Events inside the assistant | Site-level add-to-cart (outside the assistant) | Checkout / purchase |
|---|---|---|---|
| Shopify app | ✅ Automatic | ✅ Automatic (web pixel) | ✅ Automatic (web pixel) |
| Prestashop module | ✅ Automatic | ✅ Automatic | ✅ Automatic |
| GTM install | ✅ Automatic | ⚠️ Wire via GTM bridge | ⚠️ Wire via GTM bridge |
| React, Vue, or SDK install | ✅ Automatic | ⚠️ Call registerAddToCartEvent | ⚠️ Call registerSubmitCheckoutEvent |
The registerAddToCartEvent and registerSubmitCheckoutEvent calls apply to all SDK-based installs, including the React and Vue component packages — they wrap the same SDK. Don’t skip them just because you’re using the components.
Why these two site-level events matter
Section titled “Why these two site-level events matter”Your Dialog dashboard surfaces three metrics that cannot be computed without these site-level events:
- Add-to-cart rate when Dialog is not used — your baseline to compare against. Needs
user_added_to_cartto fire site-wide. - Checkout / conversion rate (with and without Dialog) — needs
user_submitted_checkoutto fire on every order, regardless of whether the visitor used Dialog. - Revenue generated by Dialog — needs the order value on
user_submitted_checkout.
Skip these events and the dashboard under-counts add-to-cart, hides your real conversion baseline, and can’t compute the revenue attribution that justifies Dialog’s ROI to your team. Wire them on day one.
What’s next
Section titled “What’s next”- GTM tracking bridge — forward
add_to_cartandpurchasefrom GTM. Usable whether the widget itself was installed via GTM or via the SDK. - SDK custom tracking — call
registerAddToCartEventandregisterSubmitCheckoutEventfrom any SDK-based install (vanilla SDK, React, Vue).
Cookies and consent
Section titled “Cookies and consent”Tracked events respect the visitor’s cookie consent. Events fired while a visitor has refused tracking are dropped before they reach Dialog. The dashboard KPIs are computed on consented events only — keep that in mind when comparing to raw site traffic.