Site settings

Access

The page is the Settings leaf of the rail's Site group, the group that closes a site's rail. The group is listed for owners and admins only: a member who follows the link is sent back to the site's root, which is Overview, or the setup screen while the site is waiting for its first event. The breadcrumb ends in Settings.

While you are on one of the five pages, the rail lists all five under Settings. Each page's header carries the eyebrow Site, the page's name as its title and the line Settings for followed by the site's address. The Docs link beside the eyebrow opens this page in a new tab, or the privacy page from Privacy. At the right of the header sits the site's status pill, with the same four readings the site switcher and the workspace home use:

General is at /settings; the other four add their name to it: /settings/installation, /settings/data-collection, /settings/conversions, /settings/privacy.

On a wide screen the body is two columns: the page's sections on the left, the facts card and the Help links on the right. On a phone the card follows the sections.

Two rules hold on every page. A switch applies the moment it is toggled and goes back if the save fails; a field or a list waits for its card's Save.

General

Identity

The section's line: How this site is named across the workspace. One card, three fields, and a Save changes button that stays disabled until something differs from what is stored, reads Saving… while it runs and shows a Saved mark when it is done. A failed save shows its reason in an alert at the top of the card. The footer notes that the card is Visible to every member of the workspace.

What you paste is cleaned up before it is stored: lowercased, a leading http:// or https:// removed, anything from the first /, ? or # dropped, a trailing dot removed. Two sites of one workspace cannot share an address; the save is refused with A site with this domain already exists in this organization.

Changing the address needs no re-install, because the snippet carries the workspace id and the site id, never the address. It does reset the matched hosts to the new address alone. The breadcrumb and the switcher show the new name and address as soon as the save lands.

Danger zone

Shown to the owner only; an admin does not see the section. Its line reads Owner only. Acts on the whole site, for every member.

The card has one row, Delete this site, with a Delete site button. The first press replaces it with Delete followed by the address permanently, beside a Cancel link; the second press deletes. You land on the workspace home, or on the create-a-site screen when no site is left.

What goes: the site leaves the switcher, the roster and the rail; its visitor pins and notes, UTM rules, conversion names, campaigns and their stars go with it; and anyone who follows its old URL is sent to the workspace root.

Its events are erased too: deleting a site records an erasure instruction, listed in the workspace's ledger as Site and the address. A tag still on your pages keeps sending, and those events count toward the workspace's monthly allowance until an erasure pass removes them, so the instruction cannot finish while the tag sends. Turning Accept incoming events off beforehand does not help, because the switch belongs to the site that is being removed: remove the tag.

Installation

Tracking snippet

The section's line says the tag carries both ids, so the site is recognized whatever host serves it.

Install method holds the same snippet the setup screen hands out, with the two tabs Directly on the site and Google Tag Manager, both ids already filled in, and a copy button. The tag and its attributes are on Install the tracker.

Verification shows the site's status pill and, under it, the type of the last event this site received, the host it came from and when, as in page_view from www.example.com followed by Oct 5, 2026, 14:03 UTC. Before the first event it reads Nothing received yet. The host shown is the host to confirm under Matched hosts.

Events you send

The section's line: Page views, outbound clicks and scroll depth are automatic. These two calls are yours to add. Two rows, each with a snippet to copy.

Conversions, with the help A primary conversion with its declared value. The id dedupes a reloaded confirmation page.

window.iads('conversion', {
  type: 'primary',
  value: 49,
  currency: 'EUR',
  id: 'ORDER-1042', // dedupes a reloaded thank-you page
})

Consent, with the help The visitor's choice on your own banner, recorded as an observed signal. It does not change what is collected.

window.iads('consent_update', {
  analytics: true,
  marketing: false,
  action: 'custom',
})

Both calls and every field are on The tracking API. Consent is observed, never enforced.

Data collection

Two cards, three controls. They decide what the site accepts; a change takes effect within a minute, not instantly.

Ingestion

The section's line: Whether the collector accepts this site's traffic at all.

Accept incoming events is a switch, on for a new site. Its help: When off, this site's events are dropped at the collector within a minute. What is already stored is untouched.

Off, every new event the site sends is dropped. Nothing already stored is touched, and nothing is deleted. The site reads Disabled wherever its status is shown, and the email that reports a quiet site skips it.

Hosts

The section's line: The pages allowed to report as this site.

Matched hosts is the list of page hosts this site is expected on. The address is always one of them: its chip is marked address and has no remove control. Every other host carries one. To add a host, type it in the Add a host field, whose placeholder is shop.example.com, and press Enter or Add. The value is cleaned up like the address, must be at least three characters and contain a dot, or the field says Enter a host such as shop.example.com., and a host already listed is not added twice. The list waits for Save hosts, disabled until it differs from what is stored, and its footer reminds you that Changing the address resets this list.

A new site's list starts as its address alone. No www. variant is added for you: www. is part of a site's identity. Other hosts appear under Verification as they report; confirm them here.

Only accept matched hosts is a switch, off for a new site. Its help: Drop events from any other host — a copied snippet, a staging server, a translation proxy. Add every host you serve first. On, an event whose page host is not in the list is dropped, and so is an event that carries no host at all. It is off by default because the list starts as the address alone, and a site registered on its apex would otherwise lose its www. traffic.

What a drop means

A dropped event is your own setting at work, not an error. It is not stored and does not count toward the monthly allowance.

Nothing here reads your plan. Every accepted event is kept, on every plan; the allowance governs what the screens may read back, which Plans and billing explains.

Conversions

One section, Tying conversions to ads: Which conversions the Conversions screen counts as brought by your ads. One row, Conversion window, a select of 1, 7, 14, 30, 60 or 90 days, 30 being the default. Its help: How long after an ad click a conversion made outside ads, in another session of the same browser, is still tied to that click. A conversion inside the visit the ad brought always counts. Choosing a value saves it at once, and the Conversions screen reads with the new window in every period.

Privacy

Retention

The section's line: How long this site's events are kept. One row, Event history, and it reads Unlimited. Its help: Kept for as long as the site exists, on every plan. Your plan decides how far back you can read, never what is stored. Nothing is deleted on a schedule or to make room. Privacy, retention and erasure has the rest.

Erase a visitor

A visitor is a browser. The row takes a Visitor ID, the identifier a visitor's own screen is reached by on Visitors. Its help: The instruction is recorded at once. Recent rows are deleted on the next pass, once storage allows it.

Request erasure is disabled until an id is typed. Pressing it shows Every event of this visitor on this site, and its pin and note, will be deleted. This cannot be undone. beside Erase this visitor and a Cancel link. Once recorded, the row reads Instruction recorded — it appears in the ledger below.

What the instruction covers, and does not:

• Every event of that browser on this site. The daily baselines are left alone: they hold nothing that singles a browser out.
• The instruction is recorded at once; the rows are gone after a later pass.
• Instructing the same browser again while an instruction is pending shows the existing one.
• An owner or an admin can give it, on any plan.
• The id is 1 to 64 characters.

Erasure instructions

The ledger the workspace settings page shows, filtered to this site. The card is titled Erasure instructions, with N on record at the end of its bar when there are rows. Each row names its subject, Browser followed by the visitor ID, with a status pill at the right and a line under it saying what happened and when:

Instructed is a waiting state, not a failure. A row reads Erased only once a check finds nothing left for it, and Not completed only after repeated real failures.

Two states can replace the rows: No erasure instructions on this site, with the note Every event stays until someone asks us to remove it. When that happens, the instruction and what became of it appear here., and The ledger could not be read just now, with the note that instructions already given are unaffected.

About this site

The card on the right states what the site is. Under it, Help carries three doors: Installation guide and Tag your ads, which open Install the tracker and Tag your ads, and Contact support, which opens the support form.

What this page does not do

• It does not delete anything on its own. Turning Accept incoming events off stops new events and leaves what is stored; every deletion is an erasure instruction.
• It does not read your plan. The plan governs the readable window, never what is accepted or kept.
• It carries no other collection rule. The two switches and the host list are the whole of it.
• It does not add a www. host for you, and it does not enforce the host list unasked.
• It does not grant access through the Group label, and it does not change who may open the site: access is the workspace's, see Members and roles.
• It does not hold the per-site UTM rules. Those are on UTM tags.