Analytics

RouteSeam records every request that hits the edge for one of your domains and rolls it into per-domain analytics. The intent is deliberately simple: honest counters that answer “is the redirect being used, and from where” — not a data-science dashboard.

Where to find it

Open a domain from the Domains list to reach its detail page. The traffic section shows the domain’s analytics alongside its DNS and TLS status. Analytics are per domain; there is no separate analytics product to configure.

What RouteSeam tracks

Each request to a RouteSeam-hosted hostname is logged with:

• timestamp
• hostname and path
• response status code
• country
• referrer
• user agent

From these events the domain detail page reports:

Redirect counts. Totals for today, the last 7 days, and the last 30 days. Use these to confirm a migration is carrying traffic and to watch the old domain’s volume decay after a rebrand.

Top paths. Which paths on the old domain are requested most. During a migration, this shows you which URLs still have inbound links or bookmarks pointing at them — the pages where a correct, path-preserving redirect matters most.

Top referrers. Which sites send visitors through the old domain. Useful for finding the sources of stale links you may want to update at the source.

Top countries. The geographic split of redirected traffic.

Status codes. The split of redirect responses the edge returned — for example how much traffic follows a 308 versus hits an error. A sudden shift here is an early warning that something upstream changed.

Note

Only requests that reach RouteSeam’s edge are counted. Traffic that never resolves to RouteSeam — for example requests served from a browser’s cached 301/308 — does not appear. Cached permanent redirects are expected and desirable; just know the counters show requests the edge actually handled, not total human visits to the old URL.

Off the critical path

Analytics collection never delays a redirect. The edge answers the request immediately and records the event asynchronously afterward. If analytics processing is ever degraded, redirects keep working and counts catch up — redirecting traffic is the product; counting it is secondary.

Retention by plan

How long analytics data is retained depends on your plan:

Plan	Analytics
Free	7-day analytics
Starter	30-day analytics
Pro	Advanced analytics
Business	Longer analytics retention

The Free plan shows the last 7 days; Starter extends the window to 30 days. Pro unlocks advanced analytics, and Business retains data longer for audits and long-running migrations. See plans and billing for the full comparison.

Using analytics during a migration

A typical rebrand reads like this in the data:

1. Cut over: counts jump as traffic starts flowing through the redirect.
2. Weeks after: top referrers show which sites still link to the old domain — update the ones you control.
3. Long tail: the 30-day count declines as search engines and browsers adopt the new domain, but rarely reaches zero. Keep the redirect (and the domain) alive for as long as the old URLs keep receiving requests.

For managing many domains’ limits and quotas, see plans and billing. For the states a domain can occupy while analytics accumulate, see the domain lifecycle.