Visitors and pageviews for the range, change vs the previous equal-length period, plus top sources, pages and events. Start here.

Pageviews and unique visitors over time, bucketed by hour or day.

Detected traffic jumps (hourly pageviews far above the same hour in prior weeks), biggest first, each with its likely causes.

Ranked causes for one spike: which referrers/UTM sources, landing pages and custom events rose above baseline (with lift, % and share of the spike), plus annotations (deploys, posts, emails) in the preceding 24h.

Traffic sources (UTM source, else referrer host, else direct) ranked by pageviews.

Pages ranked by pageviews.

Visitor countries ranked by pageviews, with the country name ("XX" is unknown).

Browsers ranked by pageviews: Chrome, Firefox, Safari, Edge, Opera, Samsung Internet, Other. Visits recorded before browser tracking began are Unknown.

Operating systems ranked by pageviews: Windows, macOS, iOS, Android, Linux, ChromeOS, Other. Visits recorded before this tracking began are Unknown.

Answer questions about this site's visits: count pageviews (or custom events) and unique visitors that match filters, optionally grouped. Examples: iOS visitors from the US last week (os=iOS, country=US); where Firefox users come from (browser=Firefox, group_by=source); signups per country (event=signup, group_by=country); /pricing views per day (page=/pricing, group_by=day). Only counts are returned; the site stores no IP addresses or user agents.

The most recent individual visits (newest first) matching the same filters as query_visits: time, page, source, country, browser, OS and event properties. visitor is a short code that changes daily, so it only shows which rows on one day came from the same browser. No IP addresses or user agents are stored.

Custom events (from agentlytics.track) ranked by count.

Save a funnel: an ordered list of 2-8 steps visitors move through, e.g. ["/", "/login", "signup"]. A step starting with / is a page (exact path, or a prefix ending in , like /docs/); anything else is a custom event name (from agentlytics.track or an element with data-agentlytics-event). Returns the funnel with its first results. Visitors are matched within a single UTC day.

Where visitors drop off. Shows, for each step, how many visitors reached it, the share of the first step and of the previous step, how many were lost, and the biggest drop. Pass name or id for a saved funnel, steps to try an unsaved one, or nothing to get every saved funnel.

Delete a saved funnel by name or id.

Evidence for marketing planning: channels ranked by conversions with growth and conversion rate, growing pages, and spike causes that recur. Use this before proposing marketing ideas.

Ranked, concrete growth actions derived from this site's data (channels to double down on, pages to promote, what caused past spikes, best time to publish), each with evidence, steps, a suggested tracked link and how to measure it. Use this to build and then execute a marketing plan.

Create a UTM-tagged link to a page on this site for one campaign, and log it so later traffic, spikes and conversions are credited to it. Use a new link for every post, email or ad you publish. After it is published, call add_annotation so a spike that follows lists it as a cause.

Traffic and same-day conversions per tracked campaign (from create_tracked_link), newest first. Omit campaign for all.

Record something that may move traffic (deploy, launch, post, email, ad). Future spikes within 24h after it list it as a possible cause. Log what you ship or run.