E-commerce
July 1, 2026
Affiliate partner: "My sale #4521 is not counted." The bot promises a commission or responds off-topic. Ticket utmattr_sale_missing.
An e-commerce partner attribution AI chatbot qualifies link UTM source code, collects order_id from UTMATTR-MAP #935, deflects tier 1 and handoffs to agent in case of credit or dispute.
This guide #936 covers intents bot_utmattr_*, workflow UTMATTRBOT UAB-1 to UAB-8, and guardrails NO-AUTO-CREDIT-BOT. Bot pair of the UTMATTR playbook (#935). Use case: qualify widget sale source link code.
Summary
Why botify attribution qualification?
Partners and clients quote ref codes or links without structured order_ids. Without qualification, the agent receives incomplete tickets. ATTR-REGISTRY-GATE aligns widget and agents #935.
What the tier 1 attribution bot solves
Qualify source: utm_source ref partner code
Collect proof: order_id link click date
Classify gap: sale_missing coupon_override utm_stripped
Explain rules: last-click registry window
Credit handoff: agent #935 if lookup required
DTC retail example
DTC 80 partners. Bot sync registry. utmattr_bot_deflect +47%, incomplete tickets -52% in 6 weeks.
UTMATTRBOT #936 vs UTMATTR #935, ADSFEED #934, STACK #870 and PARTDATA #852
Seven bot attribution contents, seven distinct roles.
Quick Matrix
#936 UTMATTRBOT: tier 1 bot qualifier code source sale widget link
UTMATTR #935: agents lookup credit deny UA-3
ADSFEED #934: feedback ad marketing distinct affiliate partner
STACK #870: stackable codes distinct coupon override ref
PARTDATA #852: partner data sharing bot distinct commission
ADLC #932: mismatch funnel distinct sales attribution
LOYALTY bot: loyalty referral distinct affiliate program
Pipeline: partner reports sale → #936 qualify classify tier 1 → handoff #935 if credit dispute.
Which bot_utmattr_* intents should be configured?
Eight attribution intents mapped UTMATTR-MAP #935.
Eight bot_utmattr intents
bot_utmattr_partner_detect: detect affiliate partner ambassador message
bot_utmattr_info_collect: order_id UTM link click date
bot_utmattr_code_qualify: validate ref code format registry
bot_utmattr_link_qualify: qualify partner link UTM params
bot_utmattr_gap_classify: utmattr_* sale_missing coupon_override
bot_utmattr_rules_explain: last-click window coupon policy map
bot_utmattr_handoff_credit: credit lookup → agent #935
bot_utmattr_feed_loop: consume LOG #935 attr_registry
Each session logs partner_id intent utmattr_* deflect_or_handoff.
How to consume UTMATTR-MAP #935?
The bot reads UTMATTR-MAP #935 + bot fields: attribution_rules, utm_standard, ref_code_map, coupon_override_policy, attribution_window_days, partner_id_lookup, info_fields_required, rules_explain_copy, agent_handoff_url, attr_registry_active.
Bot Partner Attribution Guardrails
ATTR-REGISTRY-GATE: rules from program registry only
NO-AUTO-CREDIT-BOT: do not credit commission without agent #935
INFO-COLLECT-BOT: order_id link before handoff
CODE-QUALIFY-BOT: ref registry map format
RULES-GROUNDED-BOT: coupon window from registry
GAP-CLASSIFY-BOT: utmattr_* before response
OPS-FLAG-BOT: utm_stripped pattern → #935
UTMATTR-FEED-LOOP-BOT: LOG #935 enriches attr_registry widget
UTMATTRBOT-SUP policy in six rules
Six rules for partner attribution responsible on the widget side.
ATTR-REGISTRY-GATE: registry lookup before explain
INFO-COLLECT-BOT: info_collect minimum fields
NO-AUTO-CREDIT-BOT: handoff agent credit dispute
RULES-GROUNDED-BOT: rules_explain registry only
GAP-CLASSIFY-BOT: classify before tier 1 response
UTMATTR-FEED-LOOP-BOT: LOG #935 review widget within 48 hours
Flow UTMATTRBOT UAB-1 to UAB-8
Eight-step flow: partner detect collect qualify classify explain handoff log.
UAB-1 Ingest: missing sale message link commission code
UAB-2 Partner detect: affiliate ambassador customer ref code
UAB-3 Info collect: order_id UTM link click date
UAB-4 Qualify: code_qualify link_qualify registry
UAB-5 Classify gap: utmattr_* gap_classify
UAB-6 Tier 1 explain: rules_explain coupon window
UAB-7 Handoff: credit dispute lookup agent #935
UAB-8 Log: deflect info_complete handoff_rate
Example TPL-UTMATTR-INFO
"To verify attribution: order number, link used and click date."
TPL-UTMATTR Templates and Touchpoints
Four short attribution embed templates.
TPL-UTMATTR-INFO
[info_fields map.] order link date. INFO-COLLECT.
TPL-UTMATTR-RULES
[rules_explain_copy map.] Last-click window. RULES-GROUNDED.
TPL-UTMATTR-COUPON
[coupon_override_policy map.] Priority customer code.
TPL-UTMATTR-HANDOFF
[agent_handoff_url.] Verification in progress. NO-AUTO-CREDIT.
Touchpoints
"Sale not counted": info_collect + classify
Ref code provided: code_qualify registry
Commission dispute: handoff_credit agent
LOG UTMATTR #935: feed_loop attr_registry
Edge cases: end customer, bulk sales, Collabs app
Five cases out of the standard flow.
Client cites partner code: distinct promo path and handoff if purchased
Bulk 10 missing sales: immediate handoff period export
Shopify Collabs: qualify specific registry app_id
Incomplete info 3 reminders: agent handoff #935
utm_stripped pattern: ops_flag #935 without credit promise
Essential bot exhaustion KPIs
Five UTMATTRBOT steering metrics and correlation #935.
utmattr_bot_deflect : qualifications resolved without incomplete ticket
utmattr_bot_info_complete_rate : % sessions with order_id link
utmattr_bot_classify_accuracy : % gap aligned agent review
utmattr_bot_handoff_rate : % sessions requiring agent lookup
utmattr_bot_auto_credit : bot promised credits target 0
Target: auto_credit at zero and info_complete above 70 %.
UTMATTRBOT anti-patterns
Five common bot attribution errors.
Promising commission: NO-AUTO-CREDIT handoff #935
Handoff without info: INFO-COLLECT minimum
Invented rules: RULES-GROUNDED registry only
Ignoring coupon override: GAP-CLASSIFY coupon_override
Duplicating #934: #936 distinct partner commission feedback ad
UTMATTRBOT with Qstomy
Qstomy on Shopify: UTMATTR-MAP sync #935, ref code map, templates INFO RULES HANDOFF, partner detect, KPI utmattr_bot dashboard.
Scenario: DTC 80 partners. Registry sync. utmattr_bot_deflect +47%, incomplete utmattr_ tickets -52% in 6 weeks.
Explore AI support and request a demo.
Checklist, FAQ and going further
Checklist UTMATTRBOT (8 steps)
Sync UTMATTR-MAP #935: ref rules codes coupon window
Policy UTMATTRBOT-SUP: 6 rules REGISTRY-GATE NO-AUTO-CREDIT
8 intents bot_utmattr_*: flow UAB-1 to UAB-8
4 templates TPL-UTMATTR-*: INFO RULES COUPON HANDOFF
info_fields: order_id link minimum date
partner_detect: affiliate vs final customer
Red team attribution: auto credit incomplete info test
Dashboard KPI: utmattr_bot_* section 9 + delta utmattr_
FAQ
Difference #935?
#935 = agents lookup credit deny ops. #936 = bot qualifier tier 1 widget.
Difference #934?
#934 = feedback ad marketing. #936 = attribution partner commission.
Difference #870?
#870 = stack codes customer. #936 = ref affiliate overwritten explain.
Can bot credit?
No. NO-AUTO-CREDIT. Handoff agent #935 UA-3 UA-5.
Going further
This week: sync UTMATTR-MAP #935, info_collect flow, partner_detect, measure utmattr_bot_deflect.
Enzo
July 1, 2026
