Skip to content

Commit 7b3bef5

Browse files
jamesandersenJames Andersen
authored andcommitted
docs: use event_id instead of session_id in Google example
Per review feedback — session is an Analytics-specific concept; UCP events should use event_id for deduplication.
1 parent 959b8b3 commit 7b3bef5

1 file changed

Lines changed: 3 additions & 4 deletions

File tree

docs/specification/event-context.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -158,7 +158,7 @@ purchase via Gemini's agentic checkout:
158158
"event_context": {
159159
"platform": "com.google",
160160
"dedup_keys": {
161-
"session_id": "GA1.2.1234567890.1710300000"
161+
"event_id": "evt_abc123def456"
162162
},
163163
"utm": {
164164
"utm_source": "google",
@@ -178,9 +178,8 @@ purchase via Gemini's agentic checkout:
178178
}
179179
```
180180

181-
Google Ads deduplicates conversions using `gclid` + `order_id` +
182-
`conversion_date_time`. The `order_id` is available via UCP's Order capability,
183-
so no separate `event_id` is required for Google's dedup model.
181+
The merchant includes this `event_id` when reporting the conversion via their
182+
server-side integration to prevent double-counting.
184183

185184
### Meta
186185

0 commit comments

Comments
 (0)