Read your storefront's traffic

The Traffic page, under Growth, shows how people use your storefront over a range of days: how many visits it had, which pages they read and how many visitors became customers. Owners and admins also find Acquisition under Growth, which shows where your customers came from and what your ads returned, and Forum search, which shows how your community forum's threads and member pages fare with search engines. Today's figures and the visitors with the storefront open stay on the Overview page.

• Every member can read Traffic. Acquisition and Forum search need the owner or admin role.
• Your storefront counts its own visits. To count the visits to another site of yours, add the tracking script to it, as Count the visits to another site describes.

1. In the dashboard, open the organization, then Growth, then Traffic.
2. In the Storefront visits card, choose 7 days, 30 days, 90 days or 12 months. Every card on the page follows that range, and the range stays in the page's address, so a link or a reload opens the same view.

Storefront visits adds up the range's Sessions, Page views, Conversions and Conversion rate. A conversion is a visitor's first sign-in as one of your customers, and the rate compares conversions with the visitors in the range. Below it:

• The visits table has a row for each day, with its Sessions, Visitors, visits by customers who were Signed in, Page views, Average visit, Bounce rate and Conversions. Over 90 days it has a row for each week, and over 12 months one for each month. A bounce is a visit that left after one page. A narrow screen keeps the sessions, page views and conversions, and leaves the other columns out.
• Top pages lists the most viewed pages, busiest first, with their Views, Sessions and Time on page. It shows 25 at a time. When there are more, the foot of the card says which pages you are reading out of how many, and Next and Previous move through them.
• Before converting shows what visitors did before their first sign-in as a customer, on average: the Days from first visit, the Visits before and the Pages before.

The page counts days in UTC, so a day starts at midnight UTC. To count days in your own time zone, use the API as Count days in your time zone describes.

Acquisition adds up where your storefront's visits, sign-ups, orders and revenue came from, so you can see which channels, campaigns and pages bring customers who buy. It needs the owner or admin role, and your storefront has to run on Coritan so that its tracker records each visit.

1. In the dashboard, open the organization, then Growth, then Acquisition.
2. In the Acquisition card, choose 7 days, 30 days, 90 days or 12 months. Every card on the page follows the range.
3. When customers paid you in more than one currency, a second switch lists each currency. Money is never added across currencies, so the page shows one at a time, starting with the one that earned the most.

The range, the currency and your choice of Last touch or First touch stay in the page's address, so a link or a reload opens the same view. The page counts days in your organization's time zone, which you set as Timezone under Invoicing in Settings.

The top card shows six figures. Under each one it shows the change from the period just before, which has as many days as the range you chose.

Visits

The visits to your storefront, with robots left out.

Sign-ups

The customer accounts made on your storefront. A customer your team added in the staff console does not count.

Orders

The orders placed on your storefront that are not free and whose invoice is paid.

New customers

The orders that are a customer's first paid order.

Revenue

The invoice total of those orders without tax, in the currency you chose.

Conversion rate

Orders divided by visits. Its change is in percentage points.

Each order is credited to the channel of the customer's last visit before they ordered, which is its last touch.

Each table shows its ten busiest rows. The figures at the top always cover every row.

Channels

Each channel with its Visits, Sign-ups, Orders, New customers, Revenue and Share of orders. Last touch credits the channel of each customer's last visit before ordering. First touch credits the channel of the visit that first brought the customer, so it shows the channels that start a customer's journey, such as search or social media, which a last touch table tends to give to Direct.

First touch to last touch

The pairs of channels behind your orders: the channel a customer first came through, the channel they ordered after, and the Orders and Revenue for the pair. A pair with the same channel on both sides is a customer who ordered through the channel that first brought them. A pair with two channels is a customer who came back another way before they bought.

Sources

The site and medium each visit came from, as its link names them, with the channel we filed it under.

Campaigns

The campaigns named in the utm_campaign tag of your links. Add the tag to the links of your ads and emails to see them here.

Landing pages

The first page of each visit. The path has no query string, and a page in another language counts with the page it translates.

Devices

The kind of device each visit and order came from: desktop, mobile, tablet or unknown.

How customers heard about us

What customers answered when your storefront asked how they first heard about it after an order, with each answer's share of the answers.

Ad click IDs

How many orders arrived with the click ID an ad platform adds to its links, and the ad network of each. An ad platform uses the click ID to match a sale to the ad that brought the visitor.

Return on ad spend

What each ad platform cost and what it brought back in the chosen currency: Spend, Clicks, Orders, New customers, Revenue, CAC and ROAS. CAC is the spend divided by the new customers, and ROAS is the revenue without tax divided by the spend. The card shows No ad spend in this range until you connect an ad platform or enter spend by hand on the ad spend page.

We keep each visit for 180 days. When the range starts before that, a notice says Visits are partial in this range: orders and sign-ups are still counted in full, but the visits, and the conversion rate worked out from them, are not.

How customers and orders are attributed describes what the report counts and the API call that returns it.

The Tracking script card at the bottom of the Traffic page holds a snippet of HTML for a site that does not run on Coritan, such as a blog.

1. Select Copy snippet.
2. Paste it just before the closing </body> tag on each page of the site. The script only runs on pages served over HTTPS.

The site's visits then count on the Traffic page and on Overview, together with the storefront's.

A page is counted only when it loads the tracking script. A storefront on App Deployment or on its own domain loads the script from the API as /t/script.js?org=<slug>, and is counted the same way as one that runs on Coritan.

The live figures count a visitor for as long as any tab of their visit is open, whether the tab is in front or in the background, and for 5 minutes after the last tab stops reporting. A tab in front reports every 30 seconds, and a hidden tab about once a minute. A hidden tab does not change the visit's length, bounce rate or exit page.

These limits apply:

• A phone suspends a background tab. iOS does it almost at once, and Android Chrome after about 5 minutes. A page script cannot report from a suspended page, so that visitor drops off 5 minutes after the tab was suspended.
• A tab the browser discards, for example when Chrome's Memory Saver frees memory, counts as closed.
• A page the tracking script does not load on is not counted.

The tracker is the script that counts visits on your storefront. It sets three cookies on your storefront's own domain, and the cookie banner sets a fourth when a visitor makes a choice (see Add analytics and ad tags). Visits are kept in your organization's records and are not sent to any other site.

For each visit the tracker keeps:

• The page the visitor landed on, the site that sent them, and the tags on the address: utm_source, utm_medium, utm_campaign, utm_term, utm_content and utm_id.
• Any ad click ID on the address: gclid, gbraid, wbraid and dclid (Google), fbclid (Meta), ttclid (TikTok), msclkid (Microsoft), rdt_cid (Reddit), twclid (X), li_fat_id (LinkedIn), epik (Pinterest) and sccid (Snapchat). A visit with a click ID, or with a utm_medium of cpc, ppc, paid, paid-social, display, retargeting, cpm or banner, counts as paid.
• The visitor's country, region and city, worked out from their address, and their browser, system, device type, language, screen size and time zone.
• The pages they view, how long they stay on each, and the clicks and form submissions your storefront reports.

The tracker leaves some requests out. It never counts robots, requests a browser makes in advance to load a page faster, or requests for images, scripts and data. A visitor who moves from one page of your storefront to another does not make your storefront a new source, and neither does one who comes back from a payment or sign-in page. A link's secret, such as token or code, never reaches the stored address.

We keep page events for 90 days and visits for 180 days. 30 days after a visit, the stored address is cut to its network: 203.0.113.10 becomes 203.0.113.0, and an IPv6 address keeps only its first three groups.

We score every thread and member page on your storefront's community forum against an indexing policy. Only the pages that pass go in the sitemap that search engines read, and the best of them also go in llms.txt, the list that AI assistants read.

1. Open the organization, then Growth, then Forum search.
2. Search indexing shows, for Threads and for Member pages, how many are Indexed out of the total, how many are In llms.txt, their Average score and the Score to be indexed.
3. Why threads are held back lists the reasons the policy keeps threads out of search, most common first.
4. Indexing policy lists the bars a page has to clear, such as the Wait before indexing for a thread and the Fewest posts for a member page. Our support team sets the policy, so ask them when a bar does not suit your forum.
5. To score every page again, for example after you clean up old threads, select Rescore now at the top of Search indexing.

To find out why one member page stays out of search, enter the member's handle in Member handle under Check a member page, then select Check page. The handle is the last part of the member page's address. The answer shows the page's Score out of 100, the score it needs, each reason that holds it back, and the points it earned for each part of the score.

Moderate the forum, at the foot of Search indexing, opens the staff console on your storefront's domain, where your team handles reports, suspensions and hidden threads. The button shows once your organization has a custom domain.

"No community forum yet"

Your storefront has no community forum, so there is nothing to index. Ask support to turn it on.

"No member has that handle. Check the spelling and try again."

No member of your forum has that handle. Copy it from the end of the member page's address.

Growth has no Acquisition or Forum search, or their links open Overview

Your role does not include them, because only owners and admins see them. Ask the owner or an admin.

Acquisition says No visits or orders in this range

No visitor reached your storefront and nobody ordered in the range. Choose a longer range, and check that your storefront runs on Coritan, which is how its tracker records visits.

A campaign you run is missing from Campaigns, or its orders are in Direct

The links of the campaign carry no utm_campaign tag, or a browser removed it. Add utm_source, utm_medium and utm_campaign to the links of your ads and emails.

Return on ad spend shows CAC and ROAS as a dash

A dash means the figure has nothing to divide by: no spend, or no new customers. An ad account that bills in one currency and customers who pay in another also give no figure, because spend and revenue are only compared in the same currency.

The tables stay empty

No visitor reached a page that counts visits in the range. Choose a longer range, or add the tracking script to a site that does not run on Coritan.

• Read your organization's overview
• How customers and orders are attributed
• Connect ad accounts and see what ads return
• Run a community with a server list, forum and guides
• The staff console

Any member can read the traffic routes. The forum routes take the owner or admin role, and answer 404 while your storefront has no forum. The paths are under /api/v1/orgs/acme.

curl "https://api.coritan.com/api/v1/orgs/acme/tracking/stats?start_date=2026-08-01&end_date=2026-08-31&granularity=weekly" \
  -H "Authorization: Bearer $CORITAN_TOKEN"

The script counts page views, referrers and devices, and follows navigation in single-page apps. It also sends a heartbeat every 30 seconds while a page is visible, about once a minute while it is hidden, when a hidden page is shown again and when a page closes. The visitor stays counted as live until 5 minutes after the last one. Only the platform's staff can change the forum's indexing policy.

A storefront that runs on Coritan answers two routes at its own address, for the cookie banner and for any page of your own that needs the same answer. They need no sign-in, and their answers are never cached.

curl https://store.example.com/t/consent

{
  "required": true,
  "default": { "analytics": false, "marketing": false },
  "stored": null,
  "gpc": false
}

• required is true in the European Economic Area, the United Kingdom and Switzerland, and when we cannot tell where the visitor is. Elsewhere it is false.
• default is what applies until the visitor chooses. Where a choice is required, both are false. Elsewhere both are true, except that marketing is false when the browser sends Global Privacy Control.
• stored is the choice in the visitor's _ct_consent cookie, or null when they have not chosen.
• gpc is true when the browser sent Sec-GPC: 1.

POST /t/consent takes { "analytics": true, "marketing": false }, and both must be true or false; anything else is a 422. While the browser sends Global Privacy Control, marketing is stored as false. The answer carries the new choice as stored.

curl -X POST https://store.example.com/t/consent \
  -H "Content-Type: application/json" \
  -d '{"analytics": true, "marketing": false}'

The cookie is _ct_consent=v1.a1m0: a is analytics and m is marketing, each 1 or 0. It lasts 6 months and scripts on the page can read it.

Both GET /tracking/stats and GET /tracking/today count days in UTC. A store that trades in another time zone adds tz, so that a day starts at its own midnight.

• tz is an IANA time zone name, such as America/New_York or Asia/Kolkata. An old name such as US/Eastern works, and the answer gives the name it has today. A name we do not know gives a 422 that names tz.
• A day starts at the zone's midnight, daylight saving time included, so a day can last 23 or 25 hours. start_date and end_date are dates in the zone, the period of each row is one of those dates, and GET /tracking/today counts from the zone's midnight. A visit at 02:30 UTC on 10 October counts on 9 October in America/New_York and on 10 October in UTC.
• The answer adds timezone, the name of the zone it used. Without tz the answer has no timezone and counts in UTC, as it always did.
• For a zone other than UTC, GET /tracking/stats counts each day from the visits themselves, and we keep them for 90 days. It needs granularity=daily and a start_date within the last 90 days. Hourly, weekly and monthly rows, and an earlier start_date, give a 422 that names tz, and for an earlier start_date it says the first date you can use. An end_date after today in the zone reads up to today.
• A day with no visits has no row. In a zone, each row's unique_visitors counts a visitor once for the day, and conversion_count counts the visitors who became customers that day.
• tz=UTC answers as no tz does, with timezone added, for any granularity and any range.

curl "https://api.coritan.com/api/v1/orgs/acme/tracking/stats?start_date=2026-10-08&end_date=2026-10-09&tz=America/New_York" \
  -H "Authorization: Bearer $CORITAN_TOKEN"

The answer holds one row for each day with visits, and names the zone:

{
  "rows": [
    {
      "period": "2026-10-09",
      "total_sessions": 120,
      "unique_visitors": 96,
      "authenticated_visitors": 14,
      "guest_visitors": 106,
      "total_page_views": 410,
      "avg_session_duration_seconds": 142,
      "bounce_rate_percent": 38.33,
      "conversion_count": 3
    }
  ],
  "timezone": "America/New_York"
}

To read today's figures since New York's midnight, call GET /tracking/today?tz=America/New_York. The answer carries the same figures as without tz, and adds "timezone": "America/New_York".