Crediting a booking to the AI agent that sent it, without cookies

说明与用途

TableJourney 通过在合作伙伴链接中嵌入唯一标识符（使用签名重定向和客户端脚本）实现了无 Cookie 的归因系统，从而准确地将佣金支付给代理商。

问题

Ensuring that commission payments for bookings made via partner links can be attributed to the AI agent that generated the link, without relying on browser cookies.

结果

TableJourney achieved cookie‑free, end‑to‑end attribution of bookings to AI agents by embedding a unique sub‑id in partner links via signed redirects and client‑side stamping, enabling accurate commission payouts.

工作流

• 1. Agent requests a partner key via MCP calls (partner_join → partner_confirm).
• 2. Agent uses the key to call TableJourney APIs; each returned booking link is a signed redirect (https://tablejourney.com/go/<payload>.<hmac>).
• 3. The redirect writes the agent’s sub‑id into the partner’s free‑text field (e.g., cmp, campaign, cid).
• 4. The agent forwards the link to the user unchanged.
• 5. On the user’s side, if the user shares a page, a ?ref= code is stored in a first‑party cookie for 30 days and used to rewrite partner links on page load.
• 6. A MutationObserver stamps any partner link added or modified after load.
• 7. The user clicks the link; the redirect logs the click, writes the sub‑id, and forwards to the partner.
• 8. Partners report commissions with the sub‑id; TableJourney imports these reports daily and matches sub‑ids to agents for payout.

证据

The payload names the key, the kind of link and the destination. The redirect checks the signature, looks up the key's campaign, writes it into that partner's sub-id field and sends a 302.

来源

A person shares any page with ?ref=<code></code> on the end. On arrival, a first‑party cookie set by our server holds the code for 30 days, and the page rewrites every partner link's href on load.

来源

The fix is a MutationObserver that stamps any partner link added to the page or whose href changes.

来源