To see agent traffic in Google Analytics 4 as well, open Settings, GA4, and enter the Measurement ID (G-…) and a Measurement Protocol API secret from the same web stream (GA4 Admin, Data streams, Measurement Protocol API secrets). The secret is stored encrypted and never shown again; to change only the Measurement ID, leave the secret blank. Events are sent through the Measurement Protocol, up to 25 to a request and grouped by client: client_id is the journey key, else the session hint, else a hash of the account id. Each event keeps its name (cut to 40 characters) and carries these parameters, each left out when it has no value:
| Parameter | Value |
|---|---|
agent | the agent Track names for that request, as in PostHog |
agent_class | known_agent, declared_agent_assisted, suspected_automation, human or unknown. Left out if classification failed for that batch |
agent_type | crawler, assistant, browser_agent or other, as in PostHog. Left out for a human or unknown request, and if classification failed for that batch |
path | the request path as stored |
journey_id, journey_source | the journey key and where it came from |
identity_tier, source, occurred_at | as in PostHog; occurred_at as an ISO timestamp |
track_session_id, track_event_id | the session hint and the event id in Track |
outcome_name | only on an event that recorded an outcome |
value, currency | only on an outcome with a value: GA4's own value (a number, in major units: 49 for 4900 cents) and currency (the ISO code) |
value_minor | the same value in minor units, as sent (4900) |
A paid outcome with a value is sent as GA4's recommended purchase event instead of under its own name, so it counts in GA4's revenue reports (Purchase revenue, Total revenue, Monetization). It carries everything above plus:
| Parameter | Value |
|---|---|
transaction_id | the event id in Track. It stays the same if the event is sent again, so GA4 drops the repeat instead of counting the revenue twice |
track_event_name | the event's own name in Track, such as checkout_completed |
items | one item: item_name is the event's own name, price is the value, quantity is 1 |
The event is sent once, as purchase, not also under its own name, so no payment is counted twice in GA4. To report on the original name, register track_event_name as a custom dimension in GA4. A paid outcome without a value, and every other outcome, keeps its own name.
GA4 limits apply: text values, such as a long path, are cut to 100 characters, and an event takes at most 25 parameters. Track's take up to 15 (18 on a purchase, counting items), so at most 10 (7 on a purchase) of the event's own text, number and true/false properties are added, in the order the event sent them; the rest are not sent to GA4 (they are still stored here and forwarded to PostHog). The raw User-Agent is not sent. Events forwarded before 2026-10-24 lack agent, agent_class, journey_id, journey_source and the outcome parameters, and agent_type was added on 2026-10-24 (UTC): events forwarded before then lack it, and so may events forwarded that day before about 03:30 UTC. Events older than 72 hours, which GA4 will not backdate, are recorded at the time they are sent. Like PostHog, a GA4 failure never rejects an event, and its status is in GET /v1/traffic/sink under ga4, in Settings and in install-check.