docs(tracking): correct DSR-V3 to the GA4 Admin API submitUserDeletion - #609
Merged
Conversation
The spec's DSR-V3 and §3 cited the legacy v3 userDeletionRequests:upsert (id.type=CLIENT_ID/userId), which was sunset with Universal Analytics. Update to the current Analytics Admin API properties.submitUserDeletion (analytics.edit scope, flat clientId), matching the shipped buildGa4UserDeletionRequest. Refreshes §3, the DSR-V3 vector prose, data-subject-rights.json, and adds spec CHANGELOG 1.0.1 (citation refresh).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
thevuong
added a commit
that referenced
this pull request
Jul 18, 2026
…tion (#614) Final doc cleanup for the enterprise-hardening session. Three extension docs had stale status lines after their contracts were implemented this session. ## Changes (spec-only, non-normative) - **spec-destinations §5** — "design target, not yet implemented" → reference `{ ads, analytics }` mappings for **Meta / TikTok / Microsoft UET** now ship (consent-restriction mapping only; the Pixel/CAPI/`ttq`/`uetq` transports + credentials remain the integrator's). - **spec-consent-receipts** — records that the **durable store frame** (`createDurableReceiptStore` over an injected backend) and the **integrity `sign` seam** (HMAC wired in the reference app) now ship; what remains is a backend client, retention, and counsel review. - **spec-data-subject-rights** — "partially met" → **"largely met"**: the per-destination `onErasure` hook + `tracker.erase` and the GA4 delete delegation now ship alongside the gate + `clear()`. - **spec CHANGELOG 1.0.3** — status refresh (patch). Contracts and conformance vectors are unchanged across all three. `oxfmt` clean; no code change. Completes the spec-accuracy pass alongside #609 (DSR-V3 API correction) and #613 (ad-frameworks status).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes the spec-staleness finding from #608. The
spec-data-subject-rights§3 bullet and the DSR-V3 conformance vector cited the legacy v3userDeletionRequests:upsert({ id: { type: "CLIENT_ID", userId } }) — which was sunset with Universal Analytics.Changes (spec-only, no code)
properties.submitUserDeletion(migration doc link,analytics.editscope, flatclientIdas a oneof withuserId/appInstanceId/userProvidedData).submitUserDeletion" (was "the User Deletion API").POST .../v1alpha/properties/{propertyId}:submitUserDeletionwith body{ "clientId": "<client_id>" }; notes the legacy shape is retired.vectors/data-subject-rights.json—dsr.ga4.delete-bindingupdated toinput: { clientId, propertyId }→expect.request: { body: { clientId }, url }, matching the shippedbuildGa4UserDeletionRequest(feat(tracking): GA4 DSR delegation via the Admin API submitUserDeletion #608).No package behavior change (spec docs are versioned independently via their own CHANGELOG).
oxfmtclean; DSR vector is language-neutral reference (not wired into the TS test suite).