Site Analytics
Browser event model
Review supported events, URL normalization, safe identifiers, and server matching.
The Site Insights collector accepts a small, versioned event envelope. The server resolves tenant and origin scope from the public site key and authorized request origin; the browser cannot select an organization or claim that an event matched a goal.
Event types
| Event | Meaning | Typical goal quality |
|---|---|---|
page_view | A page or supported client-side route was viewed | Destination reached when a destination rule matches |
link_click | An eligible link destination was selected | Engagement |
form_submit | An eligible native form submitted | Engagement |
custom_conversion | Customer code declared a validated success event | Confirmed outcome when configured that way |
The beacon may retain the legacy conversion call shape at the browser API boundary while the collector normalizes it to the current custom-success event model.
URL handling
Optimly normalizes URLs into allowed hostname and path fields. The browser event model does not send query strings or fragments. Referrers are reduced to hostnames before collection.
Safe element and form identity
When a goal test needs an interaction candidate, the beacon prefers:
- an explicit
data-optimly-idvalue; - a stable HTML
id; - a normalized link destination or form action;
- a bounded signature based on safe structural attributes.
Generated CSS class names, arbitrary DOM text, and entered form values are not durable identifiers.
Server-authoritative matching
The collector matches normalized events against rules that are effective at the event's occurrence time and stores the resulting match. A browser cannot submit a conversion: true claim or choose a signal-quality label.