Website analytics architecture is the contract between a page, an interaction, a source, a person or account, a CRM record and a business decision. An audit should reveal which questions the system can answer, which signals are proxies, where consent limits the sample, who owns a correction and how a release can be rolled back. It is not a tag-counting exercise.
1. Start with business questions
List decisions: launch, budget, content, response capacity, sales quality, pipeline, delivery or cash. For each, define audience, date basis, market, currency, outcome, owner and stop rule.
Reject questions that use vague verbs such as “track everything.” A small team needs a short list of decisions and a clear statement of what the architecture cannot prove.
2. Map page and journey
Inventory templates, pages, forms, calendars, phone routes, portals, subdomains, redirects, translated variants and third-party steps. Record page ID, URL, version, owner, market, language, CTA, fallback and public status.
Draw the visitor path and the failure path. Include validation, consent refusal, timeout, double submit, closed calendar, missed notification and manual handoff. A page event without a destination state is incomplete evidence.
3. Define event states
Use GA4 event guidance to name page view, CTA, form start, error, submit, success, call, booking, cancellation and no-show events. Keep trigger, parameter, timestamp, consent, page version, server response and expected next state in the contract.
Do not use one event for click, attempt and successful write. Version the event when meaning changes. Mark test, duplicate, employee, existing customer and unsupported-location records.
Document whether an event is client-side, server-side or imported, and what happens when the browser is blocked, consent is refused or the network fails. If the server writes a lead but analytics does not receive a signal, the lead still exists; if analytics fires but the server rejects the request, it does not. The architecture should preserve both facts.
4. Document source and identity
Use traffic-source dimensions to state whether source is user-, session-, event- or campaign-scoped. Keep UTM, click ID, landing page, first user, direct, partner, shared phone, consent-limited and manual paths separate.
Define stable page, session, lead, account, deal, booking and location IDs. Test a record from source to CRM and back. If identity is missing, label the row unknown rather than using the nearest campaign or page.
5. Join the commercial system
Map page → event → lead → owner → accepted stage → opportunity → delivery → payment. Use the HubSpot data model builder guidance to name objects, associations and properties when HubSpot is in the architecture; the documentation does not validate local lifecycle rules.
Test duplicates, merges, reassignment, stage regression, amount changes, closed-lost reason, currency and records without a stable origin. Keep rejected, no-response, unsupported, cancelled and manually corrected records in the sample.
6. Audit consent and access
Record vendors, purposes, fields, consent states, redaction, retention, access, deletion, transfer and restricted data. Keep sensitive content out of event parameters. Separate measurement permission from marketing permission when the local policy requires it.
Assign a privacy reviewer and a system owner. A dashboard should show data loss or consent limitation rather than quietly fill it with a modeled value.
Separate permissions for analytics, advertising, CRM operations, recordings and reporting. Keep a field-level inventory for names, phone numbers, free text, IDs, location and sensitive attributes. Record who can export the data and when access is removed. Architecture quality includes the ability to delete or correct a record without breaking unrelated reporting.
7. Check quality and freshness
Measure event missingness, parameter coverage, duplicate rate, source loss, join success, late arrival, load delay, stage completeness and stale properties. Compare before and after migrations, template releases, CRM edits, consent changes and vendor outages.
Use raw samples, not only aggregates. Include positive, negative, error, mobile, translated, local, partner, test and fallback paths. Preserve denominators and the current schema version.
Test freshness at each hop. A browser event may arrive quickly while an offline stage update, booking, delivery or payment arrives days later. Add a lag field and a maturity window to the audit rather than judging a recent cohort as a permanent failure. Re-run the same sample after a migration and note any changed definition.
8. Use the audit map
| Layer | Evidence | Hold if | | — | — | — | | question | decision, audience, outcome | tracking has no use | | page | URL, template, version, CTA | route is unowned | | event | trigger, parameter, state | proxy is called success | | source | scope, campaign, consent | source is inferred | | identity | IDs, associations, stage | join is not reproducible | | quality | missing, duplicate, late, error | aggregate hides exceptions | | privacy | purpose, access, retention | sensitive field is exposed | | governance | owner, schema, rollback | change cannot be reversed |
Choose PASS, REPAIR, REDESIGN, PILOT, NARROW or HOLD.
Require a written reason for every exception. “Tracking broken” is not enough; record which page, event, source, identity, owner or stage failed, how the failure was observed and what evidence would release the hold. This keeps a technical patch from being mistaken for a business decision.
9. Close with public and local QA
Test the public page, mobile route, form, call, calendar, consent, confirmation, CRM write, owner notification and rollback. Save schema, event map, source register, sample IDs, reviewer notes, public evidence, change log and next review.
An analytics architecture passes when every important decision has a bounded signal, every signal has a source and owner, every limitation is visible and a reviewer can reproduce the path from page to mature outcome. More tags are not a substitute for that contract.
How did this article land?
Choose one reaction. You can change it anytime.
