E-commerce
July 1, 2026
"The bot promises zero ads after opting out." "The AI refuses my cookies on my behalf without explaining the Meta delay." "Chatbot confuses email unsubscribing and pixel retargeting." Three failures where a miscalibrated tracking bot creates unrealistic expectations.
An e-commerce tracking opt-out AI chatbot does not replace TRACKOPT agents (#853). It reads TRACKOPT-MAP, guides CMP, quotes delay_copy and impact_copy, without executing API consents or promising zero advertising.
This guide #854 covers intents bot_trackopt_*, flow TRACKOPTbot and KPI trackopt_bot. Bot pair of the TRACKOPT playbook (#853). AI use case: explaining opt-out and tier 1 limitations.
Summary
Why automate bot opt-out tracking?
"Stop following me", "Instagram ads persist", "impact if I turn off tracking" arrive in the CMP footer, help widget, and post-visit. A calibrated bot reads TRACKOPT-MAP, quotes cmp_copy and delay_copy, without NO-ZERO-ADS violation or CMP execute API.
What the bot resolves tier 1 opt-out tracking
Guide CMP: cmp_copy cookie banner map path
Explain retargeting: retarget_copy delay_copy delay audiences map
Clarify channels: channel_diff_copy cookies emails push map
Cite impact: impact_copy limited personalization map
Handoff Support: #853 payload trackopt_* persistence 48 h
TRACKOPTbot vs TRACKOPT #853, PRIVPREFbot #850, PARTDATAbot #852 and anti-hallucination #123
Seven contents, seven distinct marketing consent paths.
Quick Matrix
#854 TRACKOPTbot: tier 1 bot explain opt-out limits handoff
#853 TRACKOPT: CMP agents pixels TO-5 escalate ops
PRIVPREFbot #850: separate account toggles tracking pixels
PARTDATAbot #852: distinct Meta partners technical opt-out
TXNPREFbot #834: separate emails retargeting cookies
PUSHNOTIFbot #836: separate push browser pixels
Anti-hallucination #123: policy map whitelist not legal LLM advice
Pipeline: #854 bot explain tier 1 → #853 agents execute TO-5 or ops if 72-hour persistence.
Which bot_trackopt_* intents should be configured?
Eight bot tracking intents mapped to trackopt_* typologies #853.
Eight bot_trackopt intents
bot_trackopt_retarget: retarget_copy delay_copy stop ads map
bot_trackopt_pixel: pixel_copy explain pixel map
bot_trackopt_cmp: cmp_copy cookie banner guide map
bot_trackopt_impact: impact_copy limited personalization map
bot_trackopt_channel_diff: channel_diff_copy separate channels map
bot_trackopt_gpc: gpc_copy GPC signal map
bot_trackopt_delay: delay_copy 24 to 72 h delay map
bot_trackopt_handoff: 72 h persistence → TRACKOPT853-HANDOFF-BOT
Modify CMP API consent → human handoff TO-5 only. Bot explain guide only.
How do I consume TRACKOPT-MAP #853?
The bot reads TRACKOPT-MAP #853: trackopt_program_id, cmp_copy, retarget_copy, pixel_copy, channel_diff_copy, impact_copy, delay_copy, gpc_copy, cmp_link_copy, handoff_849_copy, handoff_833_copy.
Sensitive tracking guardrails
TRACKOPT-MAP-GROUNDED-BOT: opt-out response from map only
DELAY-CITE-BOT: delay_copy cites map before closing retargeting
NO-ZERO-ADS-BOT: never promise zero advertisements after opt-out
CHANNEL-DIFF-FIRST-BOT: channel_diff if email_vs_pixel is confused
NO-CMP-EXECUTE-BOT: do not modify cookie consent via bot API
NO-LEGAL-ADVICE-BOT: no custom GDPR interpretation by the LLM
TRACKOPT853-HANDOFF-BOT: 72-hour persistence → #853 agents TO-5
TRACKOPTBOT-SUP policy in six rules
Six rules for responsible bot opt-out tracking.
TRACKOPT-MAP-GROUNDED-BOT: CMP delays impact from map only
DELAY-CITE-BOT: delay_copy mandatory on close retargeting
NO-ZERO-ADS-BOT: generic ads possible, no zero ads promised
CHANNEL-DIFF-FIRST-BOT: distinguish cookies emails push before guide
NO-CMP-EXECUTE-BOT: human CMP consent or self-service only
IMPACT-BEFORE-OPT-BOT: impact_copy if requesting to disable personalization
Flow TRACKOPTbot TOB-1 to TOB-8
Flow eight steps bot tracking embed footer CMP widget help post-visit.
TOB-1 Classify: bot_trackopt_* detect keyword track ads cookies pixel tracking
TOB-2 Intent check: retarget vs cmp vs impact vs channel_diff vs handoff
TOB-3 TRACKOPT-MAP: cmp retarget pixel impact delay channel_diff gpc
TOB-4 Explain: TPL-TRACKOPTbot-CMP or RETARGET depending on intent
TOB-5 Guardrail: MAP-GROUNDED DELAY-CITE NO-ZERO-ADS CHANNEL-DIFF NO-CMP-EXEC
TOB-6 Respond: TPL-TRACKOPTbot max 3 sentences grounded
TOB-7 Handoff or close: #853 payload #849 #834 reroute or close OK
TOB-8 Log: intent delay_cited zero_ads_blocked handoff Y/N
Example TPL-TRACKOPTbot-RETARGET
" [cmp_copy map.] [retarget_copy map.] Delay: [delay_copy map.] DELAY-CITE-BOT. "
TPL-TRACKOPTbot and touchpoints templates
Four short opt-out tracking embed templates.
TPL-TRACKOPTbot-CMP
[cmp_copy map.] [cmp_link_copy map.] TRACKOPT-MAP-GROUNDED-BOT.
TPL-TRACKOPTbot-RETARGET
[retarget_copy map.] [delay_copy map.] DELAY-CITE-BOT. NO-ZERO-ADS-BOT.
TPL-TRACKOPTbot-IMPACT
[impact_copy map.] Orders unchanged. IMPACT-BEFORE-OPT-BOT.
TPL-TRACKOPTbot-CHANNEL-DIFF
[channel_diff_copy map.] [handoff_833_copy or handoff_849_copy map.] CHANNEL-DIFF-FIRST-BOT.
Touchpoints
Cookie settings footer: bot_trackopt_cmp instant
Ads following me keyword: bot_trackopt_retarget trigger
Pixel tracking keyword: bot_trackopt_pixel proactive
Stop promo emails keyword: bot_trackopt_channel_diff reroute #834
Edge cases and reroutes
Five cases outside tier 1 standard bot tracking.
Account toggles only: PRIVPREFbot #850 reroute handoff_849
Meta Klaviyo Partners: PARTDATAbot #852 reroute
Transactional Emails: TXNPREFbot #834 reroute
Push marketing: PUSHNOTIFbot #836 reroute
Retargeting persists 72 h+: TRACKOPT853-HANDOFF ops verify pixel
Essential trackopt_bot KPIs
Five sensitive TRACKOPTbot steering metrics.
trackopt_bot_clarity_deflect: closed resolved without agent repeat 7d
trackopt_bot_delay_cite_rate: DELAY-CITE / bot_trackopt_retarget
trackopt_bot_zero_ads_violations: zero ad promise target audit 0
trackopt_bot_channel_diff_rate: % email_vs_pixel with CHANNEL-DIFF
trackopt_bot_handoff_rate: escalate #853 / total tracking bot
Target: trackopt_bot_zero_ads_violations 0 and trackopt_bot_delay_cite_rate greater than 95%.
TRACKOPTbot anti-patterns
Five common mistakes in bot opt-out tracking.
Promising zero ads: NO-ZERO-ADS delay_copy first
Executing cookie API rejection: NO-CMP-EXECUTE self-service CMP guide
Skipping retargeting delay: DELAY-CITE mandatory before close
Confusing email and pixel: CHANNEL-DIFF-FIRST before guide
Closing without impact if opt-out requested: IMPACT-BEFORE-OPT on personalization
TRACKOPTbot with Qstomy
Qstomy on Shopify: detect bot_trackopt intent footer CMP, TRACKOPT-MAP RAG grounded, DELAY-CITE guardrail, enriched handoff #853 tier 2 persistence gate.
Pipeline: #854 bot explain tier 1 → #853 agents execute TO-5 or ops if pixel firing.
Scenario: fashion brand, 12 tickets/month retargeting. Bot #854 answers CMP + DELAY, agents handle persistence after 72 h. trackopt_bot_clarity_deflect increases from 65% to 88% in 5 weeks.
Explore AI support and request a demo.
Checklist, FAQ and going further
TRACKOPTbot Checklist (8 steps)
Sync TRACKOPT-MAP #853: RAG bot tracking embed footer CMP
Policy TRACKOPTBOT-SUP: 6 rules DELAY-CITE NO-ZERO-ADS NO-CMP-EXEC
8 intents bot_trackopt_*: flow TOB-1 to TOB-8
4 templates TPL-TRACKOPTbot-*: CMP RETARGET IMPACT CHANNEL-DIFF
Block CMP API write: bot read-only no consent write
Red team 15 prompts: zero ads promise CMP execute skip delay email pixel mix
Footer cookies proactive: bot_trackopt_cmp trigger embed
KPI Dashboard: trackopt_bot_* section 9 zero_ads_violations delay_cite
FAQ
Difference #853?
#853 = CMP agents escalate ops TO-5. #854 = bot explain guide tier 1.
Bot refuses my cookies?
No. NO-CMP-EXECUTE-BOT. Guide cmp_copy self-service only.
Opt-out = no more ads?
bot_trackopt_retarget TPL-TRACKOPTbot-RETARGET + delay_copy. NO-ZERO-ADS-BOT.
Ads persist after 72 hours?
bot_trackopt_handoff TRACKOPT853-HANDOFF agents TO-5 ops pixel.
Go further
This week: deploy TRACKOPT-MAP RAG footer CMP embed, red team zero_ads_violations audit, sync bot_trackopt_retarget proactive scenario delay cite test.
Enzo
July 1, 2026
