Skip to main content

Analytics

Aglyn tracks how your site is doing out of the box — pageviews, referrers, devices, and per-page traffic — so you don't need a third-party tool to see the basics.

Plan availability

Free dashboard traffic panel. Per-page traffic and the screenAnalytics entitlement are Pro+.

The site analytics page

Pageview tracking​

A lightweight pageview beacon records visits into daily counters. The site dashboard shows a traffic panel summarizing your site's activity. Tracking is cookieless — no visitor IDs, no fingerprinting. (Funnels are the one exception, and only with the visitor's analytics consent: they tie one browser tab's steps together.)

Visitors (approximate)​

Alongside raw pageviews, the traffic panel shows an approximate visitor count. It is deliberately imprecise so it can stay cookieless: each browser tab counts once per day, so a visitor using two tabs — or returning on another day — counts again. Nothing links one day's visits to the next.

The Traffic card​

The Traffic card on a site's dashboard is the one most people read. Its range picker offers 7 days, 14 days, 30 days and 90 days, and defaults to 14.

It shows six figures for the window you picked:

FigureWhat it means
Page viewsTotal views in the window, with a growth figure beside it
VisitorsThe approximate count described above
Avg / dayPage views divided by the days in the window
Mobile / DesktopThe share of views from each, largest first
Top pageThe most-viewed path, with its view count
Top referrerWhere most visits came from, with its count

What the growth figure compares against​

The +12.4% vs prior beside Page views compares the window you selected against the window of the same length immediately before it — 7 against the previous 7, 90 against the previous 90. Change the range and the comparison changes with it; hovering the figure says which one, in words.

It is green above zero, red below, and neutral at exactly zero.

A first window shows no growth figure at all. When there is no prior period to compare against — a site published last week, asked for 30 days — Aglyn renders nothing rather than +100% or +0%, both of which would be claims it cannot support. The same rule applies to every delta in the product, including the ones on the Orders page.

Percentages in the device split are each rounded on their own, so they need not add to exactly 100. A device with no views is left out rather than shown as 0%.

Insights​

Dig deeper with top referrers and full device breakdowns over the same selectable ranges.

Campaign tracking (UTM)​

Links tagged with utm_source, utm_medium, and utm_campaign are broken down on the analytics page, so you can see which newsletters, ads, or campaigns actually bring visitors. Tag your links as you would for any analytics tool; Aglyn records the labels from the URL — nothing about the visitor.

Per-page traffic​

Pro+ sites get a per-page traffic panel in each page's detail view, with pageviews attributed to the page and broken down by referrer and device — and a Pages table on the site's analytics page comparing pageview share across all your pages over a selectable window. Plan cards surface analytics as an upsell for lower tiers.

To find it: open a site, go to Pages, open a page, open the version you want, and look for the Page traffic (14 days) card.

Average time on a page​

Beside Page views, that card shows Avg. time on this page — how long a visitor stayed before leaving it. It reads as 45s, 2m 04s or 1h 05m.

Things worth knowing before you draw a conclusion from it:

  • It is an average over the visits that reported one, not over all views. A visitor whose tab is killed, or whose browser closes before it can send, reports nothing. The figure divides by the visits that were measured.
  • It is capped at 30 minutes. A tab left open all afternoon is counted as 30 minutes rather than as an afternoon, so one abandoned tab cannot dominate the average.
  • Visits under a second are ignored. A bounce through a redirect is not time on the page.
  • It appears only once there is something to average. A page with no measured visits shows no figure at all — not a zero, not a dash.
  • Time is collected on every plan, including Free. Only reading it is Pro+, so the history is already waiting the moment an organization upgrades.

Aglyn stores a running total and a count of measurements per page per day. It never keeps an individual visit's duration — that would be a behavioral record of a person, and the average is the whole of what the feature needs.

Google Analytics​

Prefer your own tooling? Add a Google Analytics measurement ID under Site → Setup → Tracking and Aglyn injects it alongside the built-in tracking. There is a Google Tag Manager container field beside it, and both are gated on the visitor's analytics consent — the tag never loads for a visitor whose recorded state does not grant it.

Your site then sends a defined set of events to your own property: form submissions, CTA and outbound clicks, the full ecommerce funnel, overlay and A/B events, and Core Web Vitals. Google Analytics events lists every one of them with the exact parameters it carries — read it before you build a report, because GA4 will not surface a custom dimension you have not registered.

The Tracking card​

The Tracking card in a site's Setup connects your own analytics and advertising tags — Google Analytics, Tag Manager, a Meta pixel, Google Ads and LinkedIn — each loading only where the visitor's consent allows it.

Every field is optional; fill in the ones for the tools you use, then Save. In the UK, EU and EEA, and anywhere the visitor's region cannot be determined, nothing loads until the visitor accepts; elsewhere the tags load from the first visit and the visitor can turn them off at any time. The Cookie consent card below it sets that posture.

Google Analytics measurement ID​

Paste your GA4 measurement ID (it looks like G-XXXXXXXXXX, under Admin → Data streams in Google Analytics) to track the site in your own property alongside the built-in pageview analytics.

The field refuses anything that is not shaped like a measurement ID, so a saved one is one that will load. The events your property then receives are listed in Google Analytics events.

Google Tag Manager container ID​

Paste your container ID (it looks like GTM-XXXXXXX) to load a Tag Manager container on the site, with Consent Mode signals set before it loads.

A container is a loader: whatever tags it carries load with it, on the same consent terms as the other fields, and advertising tags in it stay denied until the visitor allows advertising. Do not put a Google Analytics or Google Ads tag in the container if you filled in those fields here — the same measurement would load twice and count every visit and conversion twice.

Meta pixel ID​

Paste the numeric pixel ID from Meta Events Manager to run a Meta pixel for ads and remarketing; it waits for advertising consent, a separate choice from analytics.

The ID is 8–20 digits. When a visitor withdraws consent, the pixel is removed and its cookies are cleared.

Paste your conversion ID from Google Ads (it looks like AW-123456789) to run Ads conversion tracking and remarketing without Google Analytics or Tag Manager.

It is a separate field from the measurement ID because they are separate products with separate IDs. Consent works the same way as the Meta pixel.

LinkedIn partner ID​

Paste the numeric partner ID from LinkedIn Campaign Manager to run the LinkedIn Insight Tag for ads and remarketing, under the same consent as the other advertising tags.

The ID is 4–10 digits. LinkedIn also sets cookies on its own domain, which only LinkedIn can clear.

Ask Aglyn AI​

You can ask Assist to fill in or clear this card, such as connect Google Analytics G-4R7KX2PQ9Z or remove the Meta pixel. Give the ID itself: Aglyn AI never guesses one. When your message has none, the build pauses and shows a box for it, named for the tag, such as Meta pixel ID. Enter the ID and choose Continue, and the plan comes back for you to confirm. Nothing has failed and nothing is charged while it waits. Each ID is checked against the same shape the field checks, and the change is saved to your live site when you confirm the plan, just as a save here is. Assist never changes the Cookie consent card, so every tag still loads only where a visitor's consent allows. It cannot connect anything that needs a token or a secret, such as the Conversions API on the Ad conversions card.