Measurement Maps

Hybrid Measurement Architecture

How browser events and business events move through a hybrid measurement architecture — one common pattern, not a universal blueprint.

Event Sources
Browser-Side Sources
Website / Web App Data Layer Browser Tag Manager Browser Pixels / SDKs
Business-System Sources
Shopify / Commerce CRM Product Backend Subscription App Offline / Sales Systems
Two Parallel Paths
Path A: Browser-Side Delivery
Website / Browser
Data Layer or Browser Tag Manager
Browser Pixels / SDKs
Advertising & Analytics Platforms
Meta Pixel Google tag / GA4 Google Ads TikTok Pixel LinkedIn Insight Tag Pinterest Tag Reddit Pixel

Browser-side events sent directly from the visitor's browser

Path B: Server-Side Delivery
Browser-Originated
Browser Event
First-Party Endpoint
Business-System
Shopify / CRM / Backend
Webhook, API, or Native Integration
Server-Side Processing Layer
Server-side GTM, backend service, middleware, native integration, or another server-operated environment
Validation Transformation Consent & Data Minimization Routing Deduplication Coordination Logging & Monitoring

Not every implementation performs every function — this is one common pattern

Destinations
Browser Destinations
Meta Pixel Google tag / GA4 Google Ads browser tag TikTok Pixel LinkedIn Insight Tag Pinterest Tag Reddit Pixel
Server / API Destinations
Meta Conversions API Google Ads API / Conversion Upload GA4 Measurement Protocol TikTok Events API LinkedIn Conversions API Pinterest Conversions API Reddit Conversions API Data Warehouse

Each destination should receive only the data that is useful, appropriate, and permitted

Legend
Browser-side events may be sent directly from the browser.
Browser-originated events can also be routed through a server environment.
Shopify, CRM, and backend systems may create or confirm business events.
Not every event needs to travel through both paths.
Each destination receives data according to the implementation and platform requirements.
Critical Distinction

A server-routed browser event is not automatically a backend-confirmed event. Browser-originated data and business-system-confirmed data serve different purposes and carry different levels of reliability. A hybrid architecture lets you coordinate — not conflate — these two types of signals.