Uzstādīt vietnē analītiku, kas prioritāti dod privātumam

Kad izmantot

The company wants to measure traffic on a site it controls and has no working analytics yet, or wants to replace a tool that is heavier than needed. Not for connecting the site to Google Search Console — that is search visibility, not audience measurement: use tech.connect-search-console. Not for a brand-new site that has not launched — do it as part of growth.launch-website, before the announcement, so day one is measured.

Pirms sāc

• The site is reachable and the agent can edit it (access to the code, CMS or tag manager).
• It is known what the site already loads: any old analytics snippet, pixel or chat widget that sets cookies.
• The purpose is decided — "visits" needs far less than "funnels and goals", and less measurement means a
• The account will be owned by the company (a role address, e.g. web@company), never a personal mailbox.

Ko izpilde pieprasa2

Ceļš8 soļi

1. S1

   Inventory what is already on the siteaģents

   List every script on the pages that sets cookies or sends data anywhere (old analytics, pixels, chat, fonts).

   Izdarīts, kad the list is written down, with what each one is for and whether it still has an owner.

   ⛔ Removing nothing first means the new tool's numbers are quietly polluted by double counting.

2. S2

   Propose the tool and the legal basisaģents

   Shortlist privacy-first options (no cross-site tracking, no personal-data resale): a hosted cookieless tool, or self-hosted on the company's own infrastructure. For each: monthly cost, where data is stored (EU preferred), what it can measure, what it requires in the privacy notice. State the legal basis in one line — legitimate interest for strictly necessary, cookieless measurement, or consent if cookies are set.

   Izdarīts, kad the owner has a one-page comparison with a recommendation.

3. S3

   Choose the toolīpašnieksvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S3 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Decide: which tool, hosted or self-hosted, the budget, and what the first measured goals are.

   Izdarīts, kad the owner has named the tool and the goals.

4. S4

   Create the company-owned account and propertyaģents

   Register the tool with the company as owner (role address), create the property/site, note the measurement ID or snippet. If self-hosted: deploy it on the company's infrastructure, put it on a subdomain (e.g. stats.example.lv) as a record in the existing zone — use bc dns for the record, and do not register a new domain for it.

   Izdarīts, kad the dashboard exists, is reachable, and the login belongs to the company.

5. S5

   Install the measurementaģents

   Add the snippet or tag to every page template (not single pages), or install the plugin where the platform offers one. Remove the dead scripts found in S1 that this tool replaces.

   Izdarīts, kad the snippet is in the deployed template and a live page's HTML contains it exactly once.

6. S6

   Verify the dataaģents

   Open the site (use bc open for the page) and confirm the visit appears in the dashboard within the tool's stated delay. Check from a second network or device. Mark the company's own office/team IP or domain as excluded so internal traffic does not count.

   Izdarīts, kad the test visit is visible, internal traffic is excluded, and the goals defined in S3 exist as configured events.

   ⛔ A dashboard that shows only your own visits is not verified — confirm at least one external visit too.

7. S7

   Update the privacy noticeīpašnieksvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S7 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Draft the one-paragraph addition: what is measured, which tool, where data is stored, how long it is kept, the legal basis, and how to opt out. If the tool sets no cookies and no consent banner is needed, write that conclusion down explicitly with the reason.

   Izdarīts, kad the owner has approved the wording and it is live on the site's privacy page.

   ⛔ Publishing a privacy text the owner has not read is a GDPR problem, not a formality.

8. S8

   Record and hand backaģents

   Link the analytics property to the goal/task it serves (bc tasks add or bc goals add), store the account details and measurement ID in the company's records, and send the owner a three-line summary: what is measured, where the dashboard is, what the privacy notice now says.

   Izdarīts, kad the property is linked to its goal/task, the account details and measurement ID are stored in the company's records, and the owner has the three-line summary.

Pārbaudes — kā zinām, ka izdevās

• The live page HTML contains exactly one measurement snippet (read it back from the deployed page, not from the repo).
• A test visit from outside the office network appears in the dashboard; internal traffic does not.
• Every goal from S3 fires when triggered once by hand.
• The privacy notice on the live site names the tool and the storage location.
• The analytics account owner is the company (role address), confirmed in the tool's admin screen.

Ja noiet greizi

Ko atstāj katrs solis

1. S1the list is written down, with what each one is for and whether it still has an owner.
2. S2the owner has a one-page comparison with a recommendation.
3. S3the owner has named the tool and the goals.
4. S4the dashboard exists, is reachable, and the login belongs to the company.
5. S5the snippet is in the deployed template and a live page's HTML contains it exactly once.
6. S6the test visit is visible, internal traffic is excluded, and the goals defined in S3 exist as configured events.
7. S7the owner has approved the wording and it is live on the site's privacy page.
8. S8the property is linked to its goal/task, the account details and measurement ID are stored in the company's records, and the owner has the three-line summary.

Ko saglabāt

S1 script inventory · the owner's tool choice in S3 (who, when) · measurement ID and account owner · S6 test-visit screenshot with timestamp · the approved privacy-notice wording and its publish date · the goal/task link.

Kā šī procedūra uzlabojas

After every 10 runs ask: how long from ask to first verified data, and which step waited longest? Did any site keep a leftover script that polluted the first month's numbers? Did any privacy notice turn out wrong at the next review? A new version changes the step that caused the wait or the miss, and says so in its change note.