First-Party Custom Attribution Architecture

Designed and deployed a resilient, first-party attribution engine to capture marketing source data across multi-domain funnels, eliminating compliance-driven data loss and securing end-to-end pipeline visibility.

The Context

The existing marketing infrastructure relied entirely on third-party tracking mechanisms to capture campaign touchpoints and pass them down the funnel. While functional in a legacy tracking environment, this setup created a critical single point of failure: it assumed uninterrupted access to the user’s browser storage across disparate platforms and domains.

The Challenge

When a robust cookie consent framework was introduced across all marketing properties, it exposed structural flaws in the legacy architecture.

Consent-Driven Data Loss: The moment a user opted out of non-essential cookies, all client-side third-party scripts were blocked. This severed the connection between paid ad spend and user actions.
CRM Attribution Blindspot: Because downstream CRM platforms relied on these third-party scripts to populate source tracking, the majority of inbound leads arriving in HubSpot and Salesforce were classified as completely uncalculated traffic.
Severed Pipeline ROI: Paid media teams lost visibility into which specific campaigns, creatives, or channels were generating pipeline and revenue, turning optimization efforts into guesswork.
Scale and Maintenance Bottlenecks: Manual, per-form configuration rules made it impossible to scale marketing operations to new domains without heavy developer intervention.
Bot traffic and low-quality sessions mixed into analytics with no filtering layer

The Approach

1^st Party Cookie Storage

Built a lightweight JavaScript script that runs independently of consent choices to instantly grab UTM parameters and traffic sources when a user lands on the site. This keeps the initial tracking data safe in a secure, first-party cookie instead of relying on fragile third-party networks.

Cross-Domain Persistence

Implemented cross-domain logic so attribution data follows a user across all marketing domains and landing pages. A visitor clicking a paid ad that lands on a campaign subdomain and navigates to the main site retains their original source data throughout — no session breaks, no dropped parameters between domains.

GTM Data Layer Enrichment

Configured the attribution script to automatically push the attribution payload into the Google Tag Manager data layer on every page load, making structured data instantly available for enriching Google Tag Manager tag parameters.

Universal Form Enrichment Script

Built a second modular script that reads from the attribution cookie and dynamically appends hidden fields to any form on the page based on a configurable field map. The script is provider-agnostic and works across HubSpot native forms, Marketo, and any other form implementation. New forms added to the site inherit attribution enrichment without any additional configuration.

The Outcomes

Restored source and campaign attribution across the majority of inbound leads

Eliminated blank UTM and source fields on lead records across all form implementations

Attribution data persists across cross-domain journeys without session breaks or parameter loss

New forms automatically inherit full attribution enrichment with no per-form developer involvement

The Reflection

This project exposed a gap that’s increasingly common: consent compliance and attribution infrastructure are often built by different teams with no awareness of how one affects the other. Treating attribution as a first-party data problem, rather than a cookie problem, was the shift that made the solution both consent-resilient and durable. The modular two-script approach means the system scales with the site rather than requiring rework as new forms or domains are added.