The Anonymized Configuration Record

This appendix records the state of GA4 property 534525683 after the reconstruction described in Chapters 6 through 13, captured in July 2026. It is a reference, not a narrative. Each setting appears with its value and a one-line justification so that a future engineer, or the property owner, can read the configuration and understand not only what is set but why it holds that value. The reasoning behind each decision lives in the chapter cited alongside it; this record is the flattened result.

Anonymization follows the convention used throughout the dissertation. The client is {COMPANY}, a pest-control operator serving Monterey, Santa Cruz, San Benito, and Santa Clara counties in Central California. The production domain is {company-domain}. The brand string inside identifiers is {company}. Numeric identifiers that a reader would need to reconcile against Google's own consoles (property, stream, measurement ID, Cloud project, service account project) are preserved verbatim, because they carry no personal data and anonymizing them would break the record's usefulness as a worked example.

Values here reflect the post-Phase-2 state. Settings that Google's API refused to change (the inert purchase key event) are recorded as they stand, with the refusal noted, because a truthful configuration record shows what an operator cannot alter as well as what they can.

A.1 Property and Stream Metadata

A.2 Custom Dimensions

Eleven custom dimensions are registered. Eight predate the reconstruction; service_type, cta_label, and error_message were added in Phase 1 to give the corrected server event and the click and error events queryable dimensions. Scope is load-bearing: user-scoped dimensions describe the person across the session, event-scoped dimensions describe a single hit. The taxonomy rationale is in Chapter 8, Event Taxonomy and Custom Dimensions.

A.3 Key Events

Five events are marked as key events, plus the GA4 default purchase, which remains registered but inert. generate_lead was promoted to a key event in Phase 1 once the server-side Measurement Protocol path was corrected and verified to reach GA4. cta_click was deleted as a key event because a click is an engagement signal, not a conversion, and counting it as one inflated the conversion figure. Conversion design is argued in Chapter 7, Conversion Architecture.

Two API behaviors are recorded for the next engineer. The cta_click key event was deleted cleanly. The purchase key event could not be deleted: the Admin API returned "The event cannot be deleted" with INVALID_ARGUMENT. It is harmless because no code path emits a purchase event, so it will never register a false conversion.

A.4 Data Retention

The 14-month cap matters only for Explorations and funnels keyed on event- or user-scoped custom dimensions, since GA4 standard aggregate reports retain effectively indefinitely. That is precisely the by-service and by-county seasonal analysis this business runs, so the raise is not cosmetic. See Chapter 12, Warehousing and Reporting, for why BigQuery export makes even 14 months a soft floor.

A.5 Enhanced Measurement

All seven Enhanced Measurement options were on at audit. Two were switched off in Phase 1 because they double-fired events the site already emits from its own gtag calls: pageChangesEnabled duplicated page_view on client-side navigation, and formInteractionsEnabled auto-fired GA4's own form_start and form_submit, colliding with the site's custom form events. Site search stays on although the site has no search box; it emits nothing without a query parameter, so it is inert rather than harmful.

The page_view centralization that made pageChangesEnabled redundant is documented in Chapter 7. A single RouteAnalytics client component now fires one page_view per route with send_page_view:false set in the config.

A.6 Google Signals

At this property's volume the harm from Signals is not privacy exposure but reporting suppression: cross-device modeling adds little, while thresholding withholds rows to protect anonymity. Chapter 10, Privacy and Consent by Design, sets out the trade.

A.7 BigQuery Link

The link was created in the UI, not the Admin API, on purpose. bigQueryLinks.create returned HTTP 403 for the service account even after GA4 Administrator and roles/bigquery.admin were granted, because the flow makes GA grant its own export service account project-level IAM, which needs project-IAM-admin permission the automation account should not hold. The Admin API then confirmed dailyExportEnabled: true and streaming off. The permission boundary is analyzed in Chapter 15, Access and Permissions Model.

A.8 Consent Mode v2 Defaults

Two gtag('consent','default',...) calls run before the config. The global default grants analytics and ad storage so US collection is unaffected; a region-scoped default then denies storage for 32 EEA, UK, and Switzerland region codes, with wait_for_update set to 500 ms so late consent signals still apply.

gtag('consent', 'default', { analytics_storage: 'granted', ad_storage: 'granted' });
gtag('consent', 'default', {
  analytics_storage: 'denied', ad_storage: 'denied',
  region: ['AT','BE','BG','HR','CY','CZ','DK','EE','FI','FR','DE','GR',
           'HU','IE','IT','LV','LT','LU','MT','NL','PL','PT','RO','SK',
           'SI','ES','SE','IS','LI','NO','GB','CH'],
  wait_for_update: 500,
});

Consent Mode v2 is an EEA, UK, and Switzerland Google Ads requirement, not a US legal mandate for this California-only business. The defaults are a posture that costs nothing in the US and stays compliant if the business ever advertises into those regions. No cookie banner was added; Chapter 10 explains why the defaults suffice for a US-only local operator.

A.9 Per-Service Lead Value Map

The corrected server generate_lead sends a per-service value instead of the flat 150 the old code sent. Every figure is a provisional internal estimate, never shown to a customer, used only to weight conversions for future value-based reporting and bidding. The mechanism lives in Chapter 9, Identity, Attribution, and Value.

A.10 Not Linked (Recorded for Completeness)

These two absences are deliberate and are the highest-leverage open items. The reconstruction laid the foundation (corrected conversions, wbraid and gbraid capture, a lead_id per lead, and stage and job_value columns) so that linking Google Ads becomes a configuration step rather than an engineering project. Chapter 11, The Offline-Revenue Loop, and Chapter 16, Lessons, Limitations, Future Work, carry these forward.