Track the events that matter, and prove they fire.
Send an event with one function call, define which events count as conversions, and let the platform check that the setup actually works.
| Event | Page | Source | Time |
|---|---|---|---|
| page_view | /pricing | google / organic | 12:41:08 |
| cta_click | /pricing | google / organic | 12:41:15 |
| form_submit | /demo | newsletter / email | 12:41:52 |
| purchase | /checkout/done | spring / paid | 12:42:20 |
Broken tracking fails silently.
A renamed button or a redeployed template can stop a conversion event without any error. The first sign is a strangely bad week.
Event names drift too, so the same action is recorded three ways.
Silent failures
Nothing alerts you when a conversion stops firing.
Inconsistent naming
Events multiply and reports fragment.
Unverified definitions
A conversion that was never tested is a guess.
From a line of code to a validated conversion.
Send events
Call martech.track with a name and properties from anywhere on your site.
Identify known visitors
Call martech.identify when someone signs in or submits a form to link them to a lead.
Define conversions
Choose which events, pages or values count.
Validate
The Conversion Debugger and tracking health scans check that events fire as defined.
Signals it reads
- Names, properties and timestamps
- Campaign context from the URL
- Conversion rules and values
- Event extraction and normalisation
- Tag detection per page
- Business-event coverage
Intelligence you can act on, with the evidence attached.
Intelligence produced
- A live event stream
- Conversion definitions with validation results
- Tracking health findings per page
- Alerts when tracking goes silent
Recommended actions
- Fix the event flagged as not firing
- Standardise an event name
- Add a missing business event
- Re-run the scan to confirm
What changes for the team.
Confidence in the numbers
Definitions are tested, not assumed.
Faster recovery
Tracking silence is signalled against a baseline.
Cleaner data
Consistent names keep reports usable.
Lead capture
Identify calls connect activity to known leads.
Who reaches for it, and why.
Developers
Instrument a product with a two-argument call.
Analysts
Verify a conversion before reporting on it.
Marketers
Confirm the thank-you event before a campaign launches.
Related capabilities, tools and reading.
Questions people ask first.
How do I send a custom event?
Call window.martech.track with an event name and optional properties once the snippet has loaded.
How do I link visitors to leads?
Call window.martech.identify with an email and optional external user ID after sign-in or a form submit.
What happens if consent is required?
When a site requires consent, linking anonymous visitors to leads is skipped until consent exists.
See what is moving your numbers.
Install one tracking snippet and start reading your own data. Or ask for a walkthrough first.