Events, goals and funnels

Native Analytics collects pageviews and explicitly registered custom events. Use events for actions that tell you whether a page or journey worked: an accepted signup, a completed purchase or a useful product interaction.

Register an event

Open Analytics → Events → Create event and register the event before adding its instrumentation. Declare the property names and types you need. Unknown events and undeclared properties do not automatically create catalog entries. Set up events with AI copies a prompt for your agent to choose useful events and connect them to real actions on your website.

Send a completion event from the actual success callback. A click on Submit can happen before validation or delivery fails, so it does not establish a successful submission. Avoid sending the same event through both JavaScript and a GTM trigger.

Event properties: List or Text

• List accepts predefined values, such as free, pro and team.
• Text accepts public strings of up to 256 Unicode characters without registering each value. Public product titles, article categories, website sections and plan names are examples.

For example, register product_opened with a title Text property ({ "type": "public_text" } in a CLI definition), then send the public label:

window.SiteOSAnalytics?.track("product_opened", { title: "Team workspace" });

Do not send visitor input, search queries, form answers, emails, account IDs, secrets or full URLs as properties. Text validation is not a personal-data detector. The People feature has a separate identity contract and permission.

Use the current Analytics script and reload the website after catalog changes. Declared properties also work through explicit HTML attributes and GTM mappings. Analytics does not automatically read page text or form fields.

Inspect events and received values

The Events table shows each event's daily trend, count and when it was last seen in the selected period. Search by name, or filter by source: Custom events or Automatic pageviews and Cookie interaction events.

Select an event to open its details: a chart, Filter by this event, Property values and the latest 50 Recent occurrences, followed by its color and the code to send it. In Property values, search received values, browse pages and select a value to filter reports. Exact values can also be used in goal and funnel conditions.

An existing List can be widened with Allow text values after review. This keeps saved events and consent settings intact; returning to a List is not supported by that action.

Delete an event

With permission to manage events, delete an obsolete custom event from the actions menu beside its title, after typing its exact name. New occurrences are no longer collected, while historical statistics and property values remain until normal retention removes them. Deletion cannot be undone and the name cannot be reused. Remove the matching call from your website too.

Define a goal

Open Conversions → Goals → Create goal and choose the page or registered event that represents success. Add a property condition when only a particular action counts, such as a signup for a specific plan. A website condition can distinguish the same path or event on different domains.

Goals show converted visits, the conversion rate and measured visits for the selected period and filters. A visit counts once per goal, and one visit can reach several goals, so goal rows do not add up to the overall conversion rate. Confirm that matching activity is arriving before interpreting conversion rates. A registered goal defines what to count; it does not generate the underlying action.

Follow an ordered funnel

Open Conversions → Funnels → Create funnel and define two to five ordered page or event steps. Native funnels follow the steps in order within one visit; other actions between steps are allowed. A useful example is a product page, a checkout-start event and a confirmed purchase event.

Use exact property conditions or website origins when needed. For a journey across domains, set up visit continuity first. Putting websites in one report does not by itself connect their visits.

Read completions and drop-off against the selected period and filters. A missing later step can mean the visitor left, permission changed, or the event was never implemented. Verify the event before treating the report as proof of a product problem.

Instead of creating definitions manually, Create goals with AI and Create funnels with AI copy a prompt for your agent. The agent reviews the website and the events actually arriving before it creates definitions; copying the prompt changes nothing.

Register campaigns

In Campaigns → Create campaign, register the intended utm_source, utm_medium and utm_campaign combination, then use Get link to build a campaign link for a landing page. The collector resolves registered combinations to a campaign ID; raw query strings are not sent as event properties. Unregistered combinations do not automatically create campaign categories. The table shows visits, converted visits and the conversion rate for each campaign.

Archiving a campaign from its row menu organizes the list. It does not stop collection, disable shared links or pause an advertising campaign. Use the Active, Archived and All filter to find archived campaigns and restore them. An environment can register up to 100 campaigns, including archived ones.

Read reports in context

Use Filter to narrow every report to a specific audience or outcome: domain, channel, source, visited, entry or exit page, country, region, city, device, browser, operating system, campaign, event, conversion, completed funnel or event property. Each filter can include or exclude values, and the selection stays in the report URL. A domain filter selects facts from that origin; path and origin together distinguish identically named pages on different websites.

Known AI referrers and supported campaign aliases can appear under AI Assistants. These are visits referred to your website, not a count of AI answers that mention your brand. Unavailable referral information cannot be reconstructed from Direct traffic. For mentions and citations, use SEO / GEO AI visibility.

Native funnels and connected GA4 funnels use different definitions. For Google event reports, custom dimensions, saved reports and Google-computed funnels, see Connect Google Analytics.