Eventos de sistema
Os nomes que começam por $ pertencem à plataforma: os SDKs enviam-nos por si e a consola mostra-os ao lado dos seus eventos. Esta é a única lista do que cada um significa e do que transporta.
| Event | Sent by | What it means | What it carries |
|---|---|---|---|
| <code>$autocapture</code> | Web SDK and Flutter | A click anywhere on the page, with the element that was clicked. The web SDK sends it by default; autocapture: false or autocaptureOptions.clicks: false turns it off. A Flutter app sends each tap as this event too, under TelemetryTapCapture. | <code>$event_type</code>, <code>$el_description</code>, <code>$el_description_source</code>, <code>$el_action</code>, <code>$el_tag</code>, <code>$el_text</code>, <code>$el_id</code>, <code>$el_classes</code>, <code>$el_href</code>, <code>$current_url</code>, <code>$pathname</code>, <code>$host</code>, <code>$title</code>, <code>$referrer</code>, <code>$screen_name</code> |
| <code>$pageview</code> | Web SDK | A page shown, including every client-side navigation the History API makes: one per distinct path and query. | <code>$current_url</code>, <code>$pathname</code>, <code>$host</code>, <code>$title</code>, <code>$referrer</code> |
| <code>$pageleave</code> | Web SDK | A landing page left the visitor's sight, by a tab switch, a closed tab or a navigation away, with the seconds it was in front of them so far. A page returned to and left again sends it again with the larger total. | <code>$engaged_seconds</code>, <code>$page_id</code>, <code>$page_view_id</code>, <code>$page_variant</code> |
| <code>$web_vitals</code> | Web SDK | A page's Core Web Vitals, sent once per page load the first time the page leaves the visitor's sight: largest contentful paint, first contentful paint, cumulative layout shift, interaction to next paint and time to first byte, each only when the browser measured it. autocaptureOptions.webVitals: false turns it off. | <code>$lcp_ms</code>, <code>$fcp_ms</code>, <code>$cls</code>, <code>$inp_ms</code>, <code>$ttfb_ms</code>, <code>$pathname</code> |
| <code>$screen</code> | Flutter | A named route pushed or replaced in a Flutter app, the mobile counterpart of $pageview. | <code>screen</code> |
| <code>$identify</code> | Every SDK | A person becomes known by a distinct id. The anonymous trail before it is joined to them, and any traits ride along under $set. | <code>$anon_distinct_id</code>, <code>$set</code> |
| <code>$create_alias</code> | Every SDK | A second id for the same person, so events sent under either resolve to one profile. | <code>alias</code> |
| <code>$group</code> | Every SDK | The person is placed in a group such as a company or a team; group properties ride along under $set. | <code>$group_type</code>, <code>$group_key</code>, <code>$set</code> |
| <code>$set</code> | Every SDK | Person properties written without an identify: $set overwrites, $set_once fills only what is still empty. | <code>$set</code>, <code>$set_once</code> |
| <code>$feature_flag_called</code> | Every SDK | A flag was evaluated for this person, sent once per distinct answer. Experiments attribute exposure from it. | <code>$feature_flag</code>, <code>$feature_flag_response</code> |
| <code>$marketing_event_registered</code> | The platform | A person registered for a meetup: a webinar, a conference or an in-person gathering. The platform writes it when a registration is recorded in the console or arrives from a connected webinar or ticketing account. | <code>$marketing_event_id</code>, <code>$set</code> |
| <code>$marketing_event_attended</code> | The platform | A person came to a meetup, with the minutes they stayed when the platform that ran it reports them. | <code>$marketing_event_id</code>, <code>$attended_minutes</code> |
| <code>$marketing_event_cancelled</code> | The platform | A person withdrew their registration for a meetup, or the meetup itself was called off. | <code>$marketing_event_id</code> |
A leading $ is reserved: the ingest API accepts any such name from an SDK and rejects one from your own code, so a product event is always a lowercase dotted name like order.completed. The same rule marks the reserved property keys above, and $set, $set_once and $unset are the three that write user state; how they fold into a profile is on the Data model page, and the wire bounds are on Ingest API.
In the console, every one of these appears beside your own events on Events, in the catalog behind every event picker, and in the top movers on Home. $autocapture is the busiest of them on a web property: one row per click, so a product with autocapture on sees it lead the volume band.