feat: add affiliate attribution extension#10
Conversation
Introduces the Affiliate Attribution extension for agentic commerce, including documentation, JSON schema definitions, and integration into the documentation site. This enables fraud-resistant affiliate tracking at checkout without cookies or redirects, supporting provider-agnostic attribution claims and privacy requirements.
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
Thank you for your contribution to the Universal Commerce Protocol! While we appreciate your enthusiasm for UCP, similarly to the response in #11 (comment), this doesn't align with our process for Enhancement proposals. We encourage you to explore either submitting a formal proposal for TC review or implementing this as a vendor specific extension and have it live & hosted on your own domain so they can be referenced in the profile as long as it follows UCP's governance model. |
…xtensions on Order capability (Universal-Commerce-Protocol#10)
Deleted the affiliate attribution specification, JSON schemas, and related documentation. Updated mkdocs navigation to remove references. The RFC was updated to reflect that implementation changes are pending TC approval and will be added in a follow-up PR.
|
Thanks for the guidance, @jingyli. I’ve updated this PR to be proposal‑only per the Enhancement Proposal process and removed implementation files. For context, I also have a separate RFC PR to add an intent trace extension. They’re independent, but I’m mentioning it so both can be considered in parallel. What’s the best next step for submitting the proposal discussion to the TC/public forum? Looking forward to collaborating! |
- Soften mismatch language; add continue_url as fallback option (#4) - Strengthen normative admonition with MUST/MUST NOT language (#5) - Scope fee IDs to session; clarify in schema description and docs (#7) - Mark description as plain text; reference Disclosures #222 (#8/#12) - Add messages[] guidance with fee_waived example for waived fees (#10) - Add readonly_field_not_allowed error code; reference in fee spec (#11) Co-authored-by: Dayton <31824+SVDEA001@users.noreply.git.target.com>
- Soften mismatch language; add continue_url as fallback option (#4) - Strengthen normative admonition with MUST/MUST NOT language (#5) - Scope fee IDs to session; clarify in schema description and docs (#7) - Mark description as plain text; reference Disclosures #222 (#8/#12) - Add messages[] guidance with fee_waived example for waived fees (#10) - Add readonly_field_not_allowed error code; reference in fee spec (#11)
Covers all 12 MCP-applicable changes with Spec Version, Shopify Impl Version, and Implemented status columns. Notes explain the two draft-only changes (Universal-Commerce-Protocol#2, Universal-Commerce-Protocol#4) and the deferred enforcement (Universal-Commerce-Protocol#10). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…(adjustment.amount minimum: 0) Was incorrectly attributed to Universal-Commerce-Protocol#246 (discount/cart). The actual change was introduced by Universal-Commerce-Protocol#55, which refactored all amount fields to $ref a shared amount.json type that enforces minimum: 0. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…(adjustment.amount minimum: 0) Was incorrectly attributed to Universal-Commerce-Protocol#246 (discount/cart). The actual change was introduced by Universal-Commerce-Protocol#55, which refactored all amount fields to $ref a shared amount.json type that enforces minimum: 0. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2 participants
Enhancement Proposal: Affiliate Attribution Extension
rfcs/affiliate-attribution.mdSummary
This proposal extends
POST /checkout-sessions/{id}/completeto accept an optionalaffiliate_attributionobject, enabling agents to transmit fraud-resistant attribution claims for crediting third-party publishers without relying on cookies, redirects, or client-side tracking.Type of change
Proposal Contents
Per the Enhancement Proposal process, the RFC (
rfcs/affiliate-attribution.md) includes:Implementation
This PR also includes a complete implementation ready to merge once the proposal reaches Implementable status:
source/schemas/shopping/affiliate_attribution.json— Extension schemadocs/specification/affiliate-attribution.md— Specification documentationmkdocs.yml— Navigation updatesChecklist
mkdocs build --strictpassesRequested Action
Requesting TC review to advance from Provisional → Implementable.