What the SDK tracks without you
The web SDK sends apageview on load and on every SPA route change. That’s the whole
list. Clicks, scrolls, form submits, outbound links, and errors are yours to send, so call
track() for each one.
Name the event
Use one lowercase, stable name per action. Put the variation in properties.purchase_ord_4821 creates a new event name per order, and no conversion rule can match
it.
Reserved names
Datalyr sends these names itself. Passing one totrack() corrupts the data behind that
feature.
Every name starting with
$ is reserved. Never send one.
Properties a revenue event needs
A conversion rule reads these four properties. Send all four on any purchase-like event.Limits
Datalyr enforces no event-name length limit, no property count limit, and no per-property
size limit. Datalyr drops an event that has no workspace ID, event name, event ID, or
visitor_id. A request returns 400 only when every event in it is invalid.
Verify
- Deploy to a staging environment.
- Perform the action once as a known test user.
- Open Events.
- Filter by your event name.
- Confirm the row shows the right
distinct id, timestamp, and properties.
When it does not work
Next
- Web SDK: the full
track()signature and every config option. - Conversion delivery: forward the event to an ad platform.
- Identity: attach the event to a known user.