Read analytics and conversions
The Analytics console brings traffic and conversion data together. It is read-only: use it to investigate what happened, then use an agent, the CLI, or the API to create goals and funnels. Published HTML already carries the first-party pageview beacon. To send custom events, see Collect analytics events.
Open a distribution
Go to https://app.edge.deca-dev.com/edge/{workspaceId}/analytics and choose a distribution from the site picker.
The overview shows visitors, visits, pageviews, views per visit, bounce rate and visit duration. Change the date range or graph interval to answer a specific question rather than comparing unlike periods.
Narrow the traffic
Use the filter control to narrow by page, source, channel, campaign, country, region, city, browser, operating system or device. Active filters become chips above the results.
Bots are excluded by default. Keep that default for product decisions; include bots only when you are investigating crawlers or collection behavior.
Read the Conversions card
The Conversions card has four views:
- Goals — conversion count, unique converting sessions, conversion rate and share.
- Properties — breakdowns for declared analytics properties.
- Funnels — how many sessions reached each configured step and where they dropped.
- Explore — session paths, expanded one column at a time, up to four columns.
Selecting a row changes the analysis rather than the stored definition. Creating or editing a goal, property or funnel is not available in the console.
Explore a session path
Open Explore, choose the first page or event, then select a value in each following column. The next column shows what happened after the path you selected.
Use Explore for questions such as “what did visitors do after pricing?” or “which path led to checkout?” It follows observed sessions; it does not define a funnel or rewrite a goal.
Ask an agent, use the CLI, or call the API
The console uses the same analytics contract available to agents and integrations.
Show visitors, visits, pageviews and bounce rate for the acme-marketing
distribution over the last 28 days, excluding bots.edge api POST /v1/analytics --input - <<'EOF'
{
"distribution_id": "d3f7a1c4-90b2-4e6a-8f15-6c2b7e0a9d38",
"metrics": ["visitors", "visits", "pageviews", "bounce_rate"],
"range": { "preset": "last_28_days" },
"include_bots": false
}
EOFcurl -s -X POST https://api.edge.deca-dev.com/v1/analytics \
-H "Authorization: Bearer $EDGE_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"distribution_id": "d3f7a1c4-90b2-4e6a-8f15-6c2b7e0a9d38",
"metrics": ["visitors", "visits", "pageviews", "bounce_rate"],
"range": { "preset": "last_28_days" },
"include_bots": false
}'The agent runs edge_analytics_query.
For path exploration, use edge_analytics_explore or POST /v1/analytics/explore.