Page body
What this page shows
Visits CTR Cohort is the cohort report for first visits versus same-cohort registrations.
It groups users by the date or period of the first tracked visit and then shows how visits, registrations, and CTR behave across later cohort periods.
When to use it
- compare click or visit cohorts over time
- evaluate registration conversion after traffic acquisition
- segment cohort performance by PID, country, domain, or landing page
How to read it
The table is cohort-based, not a plain daily traffic report.
- the first column is the cohort start date or period
Registrations on Cohort Day (Users)shows the user count assigned to that cohort- every later period cell contains
V / R / CTR - the last row is a totals row, recalculated from summed totals rather than averaged per-cell CTR
Action and filter behavior
- filter controls are staged locally until
Apply Filtersis pressed Refreshreruns the current active cohort query without promoting newly typed filter valuesExport CSVuses the active cohort snapshot, ignores visible pagination, and requests page1with a hard export cap of10,000cohort rowsCustom Period (days)is only visible whenCohort ModeisSelected period (custom)Mirror Domainsis only visible whenMirror / Domainis set toSpecific mirror(s); switching back toAll sites combinedorMain domain onlyclears those selected ids from the active request
Known caveats
- the default backend window is the last 30 days through today when no custom range is supplied
Domain modeis backend-defined:all,main, andmirrordo not behave like a simple label filterMain domain onlyis implemented as the inverse of all known mirror-domain URLs plususers.mirror_domain_fk IS NULL, not as a dedicated first-party-domain flag- landing-page suggestions come from affiliate-link groups and intentionally hide obvious admin or system paths like
wp-admin,dashboard,default, andimages; operators can still enter custom free-text paths manually - bot traffic is excluded by default
- suspicious traffic and traffic-quality logic can still affect the dataset in backend filtering even though those controls are not exposed in the FE
- restricted countries are excluded by backend settings
- the backend uses visitor identity fallback
owner_uuid -> affiliate_link_token -> click_id -> ip_address, soVisitsis not a raw pageview counter - the CSV export writes raw decimal CTR ratios rounded to 4 decimals, not the FE
%formatting shown in the table
Filters that change the result
- start date
- end date
- PID
- country
- cohort mode
- custom period days
- domain mode
- domain ids
- landing pages
Verification status
- status:
verified_backend - FE route, container, hook params, dynamic cohort grid, and export flow are mapped
gs-admin-backendowns cohort building, identity fallback, traffic filtering, and CTR calculationnx-workspaceis not required for the current operator meaning