Fixing Cross-Domain Analytics Contamination: Separating JADA and QDN Properties

```html

During a routine audit of our multi-property infrastructure, we discovered a critical ownership and analytics configuration issue affecting two separate business entities: Sail Jada (JADA) and Quick Dump Now (QDN). While the Google Analytics tags themselves were correctly separated, the underlying Google Search Console and account ownership structure revealed a systemic problem that could lead to data corruption, compliance issues, and operational confusion.

The Problem

Our infrastructure hosts multiple independent web properties under a single AWS account:

sailjada.com (JADA business)
queenofsandiego.com (JADA-owned booking site)
quickdumpnow.com (QDN business — separate entity)
dangerouscentaur.com (separate business)
86from.com (separate business)
burialsatseasandiego.com (separate business)

During a Google Search Console audit, we found that quickdumpnow.com's GSC property was accessible and manageable via the jadasailing@gmail.com account — the primary Google account for JADA operations. This created a dangerous situation where:

QDN's search data, indexing decisions, and analytics were under JADA's account control
A single compromised JADA account would grant access to QDN's sensitive business data
There was no clear separation of duties between the two independent business operations
Analytics tracking was already partially fragmented (QDN inner pages at /book, /track, and /service-areas/carlsbad/ were missing GA tags entirely)

Technical Audit Findings

We systematically audited GA tag placement across all properties by scanning homepage and subpage assets:


# Verification scan across all production domains
# Checked  tags and script blocks for GA4 property IDs

sailjada.com (homepage):         G-N6HKL4KLKT (JADA ✓)
queenofsandiego.com (homepage):  G-N6HKL4KLKT (JADA ✓)
quickdumpnow.com (homepage):     G-539T97NM1Z (QDN ✓)
dangerouscentaur.com (homepage): G-GGP987FJSW (DC ✓)
86from.com (homepage):           G-YJWFKWVWNQ (85F ✓)
burialsatseasandiego.com:        UA-175171552-1 (Legacy UA — deprecated)

Critical gap discovered: Three QDN subpages lacked the QDN GA tag entirely:

quickdumpnow.com/book — Missing GA-539T97NM1Z
quickdumpnow.com/track — Missing GA-539T97NM1Z
quickdumpnow.com/service-areas/carlsbad/ — Missing GA-539T97NM1Z

This means conversion funnels, user flows, and booking behavior on QDN's most critical pages were not being tracked, creating blind spots in business intelligence.

Root Cause Analysis

The ownership problem originated from convenience rather than architecture:

Single AWS Account: All properties share one AWS account, which is operationally efficient but requires strict IAM role separation at the application layer
Single Google Account for GSC: Domain verification for quickdumpnow.com was completed using jadasailing@gmail.com instead of creating a QDN-specific Google account
Incomplete GA Implementation: Subpage GA tag deployment was likely done manually or via incomplete template synchronization, leading to gaps

Infrastructure Changes Required

We queued two primary remediation tasks:

1. Google Search Console Ownership Transfer (t-77babced)

The quickdumpnow.com GSC property must be transferred to a dedicated QDN Google account (to be created as admin@quickdumpnow.com or similar). This requires:

Creating a new Google account owned by QDN management
Using DNS verification (TXT record) or domain file verification instead of Google Analytics tag verification, which is less dependency-prone
Adding the QDN account as a property owner in the existing GSC property
Removing JADA account access from QDN property
Updating Route53 DNS records if TXT-based verification is used

2. GA Tag Completion on QDN Subpages

QDN's missing analytics tags must be added to all subpage templates:

S3 Structure: QDN content likely lives in an S3 bucket following pattern s3://qdn-prod-content/ or similar, with subpages at /book/index.html, /track/index.html, and /service-areas/carlsbad/index.html
GA Script Injection: Add GA4 property G-539T97NM1Z to the <head> section of each template via a shared header component
Deployment: Update S3 objects directly, then invalidate CloudFront distribution cache (exact distribution ID to be determined)

Why This Matters

Data Integrity: Shared Google accounts between unrelated businesses violate data governance best practices. If JADA's account is compromised, attackers gain immediate access to QDN's search data.

Compliance: Separate businesses should have separate audit trails. If QDN needs to comply with GDPR, CCPA, or industry-specific regulations, comminggled Google account access makes compliance audits ambiguous.

Analytics Accuracy: Missing GA tags mean blind spots in conversion funnels. QDN's most valuable user journeys (booking, order tracking, service inquiries) are invisible to analytics, making it impossible to optimize those flows.

Implementation Plan

Work is split into two categories:

Browser-Required (Manual): GSC property ownership transfer requires human authentication and domain verification. This is queued for manual completion with detailed step-by-step instructions.
Infrastructure (Automated): GA tag deployment to QDN subpages can be scripted. We'll update HTML templates, deploy to S3, and invalidate CloudFront caches.

What's Next

Immediate next steps:

Complete GSC ownership transfer (blocks on QDN account creation)
Deploy GA tag updates to QDN subpages and verify via page inspection
Run