Where visitors come from

Every site on the platform remembers where a visit began and attaches it to what the visitor then does. Nothing about the visitor is tracked: there is no cookie of its own, no identifier, and the visit is forgotten with the browser session. What stays is one row per thing sent.

What is read

• Campaign parameters on the landing URL — utm_source, utm_medium, utm_campaign, utm_term, utm_content. Tag the links you post (LinkedIn, a newsletter, an ad) and the platform reads them.
• Click ids of ad platforms (gclid, gbraid, wbraid, msclkid, fbclid, ttclid, li_fat_id) — paid traffic without UTM tags still names its source and medium. Since 2026-09-09 the value is kept as well, next to the name of the parameter that carried it, and it is read whether or not the link was also tagged.

WHY the value matters: Google Ads appends gclid to the landing URL by itself (auto-tagging), on top of whatever tags you wrote. The tags say what you CALLED the campaign; the click id identifies the single click that was paid for. Without it a sale cannot be handed back to the ad that produced it, so the ad platform never learns which clicks are worth buying. Until now only the FACT of a paid click survived, as source google and medium cpc — and a properly tagged campaign lost the id entirely, because it was read only when nothing else was there. - The referring site, when no parameter is present: a well-known host names the source and the medium by itself (LinkedIn → social, Google → organic, GitHub → referral, a newsletter client → referral); any other external site is a referral. The site's own host is nothing — an internal link never counts and never overwrites the origin of the visit.

The first touch of the session wins.

Where it lands

One row on Structure → Where visitors come from per:

• enquiry (and the CRM lead made from it carries utm_source, utm_medium, utm_campaign as the visit gave them),
• web form submission,
• customer registration,
• order placed at the checkout,
• download of a release (the program's installer).

The view is a shipped view: filter by source, medium, campaign or kind, group by campaign, reshape or revert it like any default view; only the firm's own rows, ever. Claudia answers the same question with seo_sources (the last 30 days by default).

Click id and Click id kind are columns of that view, available but not shown by default — they are for handing a sale back to an ad platform, not for reading. Add them to the display (Structure → Views → Where visitors come from) when you need to export them; the time in the When column is the conversion time an offline import asks for.

Handing a sale back to the ad platform

An ad platform only learns what works when the sale is reported back to it. On this platform that happens on the server, from these rows, not in the visitor's browser:

1. Add the click id columns to the view and filter to the kind you count — usually order, or download while a free version is the way in.
2. Export the rows: the click id, its kind, and the time.
3. Import them at the ad platform as offline conversions (Google Ads: Tools → Conversions → Uploads), with a conversion action of your own.

WHY not in the browser: the Google integration keeps every advertising consent signal denied and ad-vendor hosts out of the site's Content-Security-Policy. That boundary is deliberate. It means browser-side ad conversion tracking will not work here by design, and the click id kept on these rows is the path that does.

UTM values in the CRM

The CRM's UTM value catalogue governs what a person types on a lead. The visit writes what happened — a value from a tagged link is kept as it came, so a campaign you never registered still shows up under its own name.

Privacy

The privacy page of every site names this processing (legitimate interest): the campaign parameters and the referring site of the visit, kept for the visit and attached to what the visitor sends. Nothing is shared and nothing follows the visitor to another site.

The click id is part of the same processing and is named the same way. It is worth knowing what it is and what it is not: it identifies the ad click, not the person — it is issued by the ad platform, it arrives in the address the visitor was sent to, and this platform neither sets it, extends it, nor sends it anywhere on its own. It sets no cookie and it does not follow the visitor to another site. It leaves the platform only when a firm exports rows deliberately, and then only to the platform that issued it in the first place. A firm that adds click ids to an export a person can open should say so on its privacy page.