Measurement Protocol Payload Builder for GA4 Purchase Events

How to send GA4 Measurement Protocol purchase events in bulk

A GA4 Measurement Protocol purchase event tells Google Analytics about a sale your website tag never saw: a phone order, an in-store payment or a deal closed in your CRM. Google's Measurement Protocol reference sets strict limits, and the endpoint doesn't return an error when a body is wrong. For one test event, Google's own Event Builder is fine. This tool is for many orders at once.

1. Export your orders. One row per order, or one row per line item like a Shopify or WooCommerce export. You need the GA client ID saved with each order, the order ID, date, items and prices.
2. Load the file. Rows with the same order ID become one purchase with several items.
3. Check the columns and options. Add your Measurement ID and pick the time zone and currency. Choose refund to send refunds instead.
4. Read the checks. Orders without a client ID or items, older than 72 hours, in the future or with bad numbers are left out with a reason.
5. Download the requests and the script. The requests file holds one JSON body per line, grouped by client and capped at 25 events. The script checks them on Google's validation server, then sends them when you say so.

Checks that go beyond a single-event builder

• Value: worked out as price × quantity without shipping or tax when you have no value column, and checked against it with a warning when you do.
• Transaction ID: required and never empty, because GA4 merges every purchase with an empty ID into one.
• Time: written as timestamp_micros (microseconds), within the 72-hour window.
• Size: 25 events per request, up to 200 items per purchase and request bodies under 130 kB.

Validate and send the requests

1. Create an API secret. In GA4, open Admin › Data collection and modification › Data streams, choose the web stream, open Measurement Protocol API secrets and click Create.
2. Check first. Save both files in one folder and run GA4_API_SECRET=your_secret node send-ga4-purchases.mjs ga4-mp-requests.ndjson. On Windows PowerShell, first run $env:GA4_API_SECRET="your_secret", then the node command. Every request goes to the validation server; fix anything it reports.
3. Send. Run the same command with --send at the end. Each request should return HTTP 2xx. If one doesn't, fix the request instead of sending it again.
4. Look in GA4. Purchases appear in the monetization reports once GA4 has processed them. GA4's create and modify event rules don't apply to Measurement Protocol events, so send the final event names.

Google also added a Data Manager API in 2026 that can send events to GA4 from a server. The Measurement Protocol remains the simplest option for a daily file.

Measurement Protocol problems and fixes

Events not showing in reports

The collect endpoint answers with success even for a broken body. Run the requests through the validation server first, and remember that events sent to the validation server never appear in reports.

NAME_INVALID or NAME_RESERVED

Event names must start with a letter, use only letters, numbers and underscores, and be 40 characters or fewer. Names like session_start are reserved.

VALUE_REQUIRED for client_id

Web streams need a client_id. Use the value saved from the visitor's GA cookie, not an order number or email. App streams use app_instance_id instead, which this tool doesn't build.

Purchases counted twice

Send each order once with the same transaction_id your website tag used, so GA4 can drop duplicates. Deduplication by transaction ID works for web streams only.

Revenue on the wrong day

An order older than 72 hours is dated 72 hours ago. Send purchases every day, and check the time zone option so recent orders don't look older than they are.

Purchases without a traffic source

Google warns that events sent only through the Measurement Protocol may give partial reports. Capture the session_id of the visit with the order and send it with the event, so GA4 can connect the sale to that session.