How to track custom events with Modovisa

Named events fill the gaps the tracking script does not already record — signups, downloads, affiliate clicks, and custom storefronts. Markup, store helpers, or modovisa.track().

You may not need a custom event

Modovisa already records pageviews, link and button clicks, and form submissions. On a store it recognises product, cart, checkout and order-confirmation pages. Custom events are for the rest: a CTA that is not a form, a PDF, an affiliate click, a trial start.

Three ways to send one

Easiest first: add data-modovisa-event to the element (plus data-modovisa-* fields; the suffix is the field name, copied as-is). Clicks on a child still count. For a custom storefront call modovisa.cart(), checkout() or purchase(). For anything else call modovisa.track(name, null, fields). Queue with window.modovisaQueue if the script may load after the thank-you page.

What it costs and where it shows

cart() and checkout() move the funnel without a billed event. Markup, track() and purchase() each count as one event against the monthly allowance. Named events appear on the live journey and in page-by-page replay on paid plans and the trial. Match the name in Campaigns to count a conversion.

Verify it worked

DevTools Network should show POST /api/collect with event_type equal to the name you chose. Open the visitor in Live Insights. If nothing appears, the script is missing, the site selector is wrong, or the account is at its event cap.