Objective
This SOP outlines how to integrate your first-party business data with Google Analytics using Data Import and Measurement Protocol. By combining online and offline datasets, businesses can gain a more comprehensive view of user behaviour, product performance, and customer value.
Overview
This SOP covers:
- Benefits of using first-party business data
- How to use Data Import to enrich GA4 data
- How to send offline events using Measurement Protocol
- Data joining types and technical requirements
- Practical use cases to guide implementation
Step 1: Understand the Value of First-Party Data
First-party data refers to information collected directly from your customers—such as purchase history, loyalty status, or CRM records.
Benefits of using first-party data in GA4:
- Create tailored audiences and remarketing segments
- Understand the full customer lifecycle
- Measure cross-platform behaviour (web + offline)
- Use custom business metrics (like LTV or loyalty tier) in reports
Step 2: Use Data Import to Enrich Analytics Data
Data Import lets you upload external business data into GA4 using CSV files. These files are then joined with GA4-collected event data, enriching your reports, explorations, and audience-building tools.
Data types you can import:
- Cost data – From non-Google ad platforms (e.g., email, social ads)
- Item data – Product metadata like size, color, or category
- User data – CRM-based data like loyalty level or LTV
- Offline events – Sales, refunds, or leads captured offline
Step 3: Upload Data with CSV Files
- Go to Admin → Data Collection and Modification → Data Import
- Click Create data source
- Name the data source (e.g., “Clothing Metadata”)
- Select data type (e.g., Item data)
- Choose Manual CSV upload
- Upload your CSV file
- Map imported fields to existing GA4 dimensions (e.g., item_id → item_id, item_color → variant)
- Click Import
Once processed, your new data is combined with existing event data.
Step 4: Use Measurement Protocol for Offline Events
Measurement Protocol allows developers to send event data directly to GA4 servers via HTTP requests. This is useful for:
- Point-of-sale systems
- CRM-based conversions
- In-store refunds
- Other non-browser environments
To use:
- Use the Event Builder tool to structure your event
- Define required parameters (e.g., product_id, price, transaction_id)
- Validate event setup
- Send requests to GA4 using the Measurement Protocol endpoint
- Use Realtime report in GA4 to verify data is arriving
Step 5: Choose the Right Data Joining Strategy
GA4 supports two data joining methods:
Reporting/Query Time Join
- Used for: Cost data, item data
- When it joins: At report loading
- Limitation: Not available for audiences or explorations
Collection/Processing Time Join
- Used for: User data, offline events
- When it joins: During event collection
- Advantage: Fully usable in reports, explorations, and audiences
Practical Use Cases
Janelle’s Use Case (Retail Chain)
Janelle, a data analyst at a big box retailer, uses:
- Data Import to upload loyalty status and user LTV
- Measurement Protocol to send in-store purchase events to GA4
Result: A unified view of both online and offline customer behaviour.
Campaign Attribution
Use cost data import to enhance attribution from email or paid social channels that aren’t tracked via Google Ads.
Product Performance Analysis
Upload item metadata to understand performance differences between product types, such as T-shirts by color or size.
Custom Segmentation
Use user data import to build GA4 audiences by loyalty tier, last purchase date, or customer value.
Requirements and Best Practices
- For Measurement Protocol:
- Use the correct join keys (e.g., Client ID, User ID, App Instance ID)
- Web and app data streams use different join keys
- Most features require the use of gtag.js, Tag Manager, or Firebase SDK
- For Data Import:
- Use clean CSV formatting
- Align data field types correctly
Validate mappings before importing