The GA4 Measurement Protocol is an API for sending events from places the web tag cannot reach, such as your backend, a billing system or an offline process. It supplements browser tracking, and does not replace it.
Need help with SEO?
Comppound runs SEO and AI search for SaaS companies. We plan what to publish, produce it with AI, and every page passes automated checks, and a person reviews samples and anything high-risk.
- Published to your site and tracked in Search Console
- One person answers for your account
- Plans from $400 a month, terms from 3 months
Typical uses
- Recording a subscription renewal or refund
- Sending a conversion that happens after a call or demo
- Reporting events from a mobile or desktop app backend
Requirements
Events must carry a client ID or user ID that ties them to a real user, plus an API secret. Without a matching ID they cannot be linked to earlier sessions.
Common mistakes
Sending events with no matching client ID
They appear as unattached traffic and break attribution.
Frequently Asked Questions
No. Server-side tagging moves tag processing to a server. The Measurement Protocol is a direct API for sending events.
Keep reading
- Server-side tagging: Server-side tagging moves tag processing from the visitor's browser to a server you control, which then forwards data to analytics and ad platforms.
- Google Analytics 4: Google’s current web and app analytics product, which records visits and actions as events and reports where visitors come from and what they do.
- Offline Conversion Import: Offline conversion import sends CRM outcomes like qualified leads and closed deals back to ad platforms, so bidding and reporting reflect real pipeline.
- Analytics event: An analytics event is a recorded interaction, such as a page view, click, sign-up or download. In GA4 every interaction is stored as an event with parameters.
- Consent Mode: Consent Mode is Google's API for passing a visitor's cookie consent choices to Google tags, which then adjust what they store and send.
- Cross-domain tracking: Cross-domain tracking keeps one visitor's session intact as they move between your domains, such as a marketing site and an app or checkout.
- Data thresholds: Data thresholds are GA4 limits that hide rows with small user counts so individuals cannot be identified, mostly when Google signals or demographics apply.
- Data-driven attribution: Data-driven attribution uses a statistical model of converting and non-converting paths to share credit across touchpoints. It is GA4's default model.
