MatchToken binds intent, proposal, and merchant
It is not a UTM. It is the signed transaction identity agents, merchants, and settlement can agree on.
SellToAI does not stop at a tracked link. Each accepted proposal carries a recId and MatchToken through checkout, then Shopify/TikTok order webhooks attach the outcome back to the original intent, evidence card, merchant, and channel.
intent_id
proposal_id
match_token_id
checkout_url
attribution_orders
What becomes measurable
This page is the public version of the loop. The protected ops console still exists for raw dashboards, but the core value must be understandable before anyone logs in.
It is not a UTM. It is the signed transaction identity agents, merchants, and settlement can agree on.
Order webhooks attach paid, cancelled, and refunded outcomes to the original recId and MatchToken.
Once clicks and orders return, SellToAI can compare creator proof, community proof, risk, and merchant SLA against actual outcomes.
Intent, proposal, match session, MatchToken, click, and order are separate records, so failures are debuggable.
Closed loop
The strategic wedge is not checkout ownership. It is making proof-backed recommendations measurable after the shopper leaves the AI surface.
Channel, intent, product fit, and merchant response live together instead of disappearing into a generic redirect.
Evidence Card fields make the recommendation auditable before the buyer clicks.
SellToAI keeps the merchant-owned checkout path and carries attribution metadata through it.
Webhook events turn clicks into paid, cancelled, refunded, or missing-order signals.
Evidence quality, merchant reliability, and channel performance become ranking inputs.
Why it matters
Catalog access and checkout will become table stakes. The hard part is proving that a specific evidence-backed recommendation created a specific order.