E-commerce
July 1, 2026
"Your Instagram ad is lying about the price." The bot replies to the customer but the objection never reaches the ads team. Same campaign, 8 lost signals in 3 days.
An e-commerce ad feedback AI chatbot captures campaign objections, structures UTM proof typology to ADSFEED-MAP #933, and feeds the marketing dashboard, without promising fixes or replacing agents #931.
This guide #934 covers intents bot_adsfeed_*, flow ADSFEEDBOT AFB-1 to AFB-8, and guardrails UTM-CAPTURE-BOT. Complement to the ADSFEED playbook (#933). Usecase: send campaign objections to the analytics widget.
Summary
Why botify advertising feedback?
Ad objections arrive in the chat before the formal ticket. Without structured capture, marketing only sees the aggregated customer service volume. FEEDBACK-STRUCTURED-BOT feeds ADSFEED #933 in near real-time.
What the ads feedback bot captures
Promise objection: disputed delivery code price
Campaign UTM: campaign_id source platform
Adsfeed typology: promise price shipping oos
Light proof: landing URL ad quote
Cluster signal: marketing dashboard export
DTC retail example
DTC fashion, active feedback bot. adsfeed_bot_capture_rate +58% structured signals, adsfeed_cluster_detect_time -40% in 6 weeks.
ADSFEEDBOT #934 vs ADSFEED #933, ADLCBOT #932, EXPIAD #930 and beta feedback
Seven feedback bot contents, seven distinct roles.
Quick Matrix
#934 ADSFEEDBOT: bot to capture and structure campaign objections for the marketing dashboard
ADSFEED #933: ticket loop process → AF-1 ads correction
ADLCBOT #932: evidence collection for Tier 1 client mismatch
EXPIAD #930: expired offer, explain distinct feedback analytics
ADLC #931: agents resolving individual mismatches
Beta feedback: beta product feedback distinct from the ad campaign
Post-support: post-ticket CSAT distinct from ad objection
#932 = help the client with mismatch. #934 = feed marketing with structured signals.
Which bot_adsfeed_* intents should be configured?
Eight ad feedback intents mapped ADSFEED-MAP #933.
Eight bot_adsfeed intents
bot_adsfeed_objection_detect: detect ad quote disputed promise
bot_adsfeed_utm_capture: collect UTM landing URL campaign
bot_adsfeed_typology_tag: classify adsfeed_* promise price shipping
bot_adsfeed_proof_light: ad quote minimum landing link
bot_adsfeed_signal_log: record signal dashboard export
bot_adsfeed_cluster_check: UTM threshold marketing alert
bot_adsfeed_handoff_support: customer ticket if resolution needed #931
bot_adsfeed_feed_loop: consume LOG #933 ads_registry
Each signal logs utm_campaign adsfeed_typology export_marketing.
How do I consume ADSFEED-MAP #933?
The bot reads ADSFEED-MAP #933 + bot fields: adsfeed_typologies, utm_fields_required, cluster_threshold, signal_log_template, export_webhook_url, close_loop_copy_pending, handoff_support_url, campaign_platform_map, ads_registry_active.
Ad bot feedback guardrails
FEEDBACK-STRUCTURED-BOT: adsfeed_* formatted signal mandatory
UTM-CAPTURE-BOT: campaign_id if ad objection detected
NO-MARKETING-PROMISE-BOT: do not promise ad fix
SIGNAL-LOG-BOT: export dashboard for each objection
CLUSTER-CHECK-BOT: UTM threshold alert #933
CLIENT-FIRST-BOT: handoff #931 #932 if client blocked from purchasing
NO-DUPLICATE-TICKET-BOT: signal only if tier 1 resolution OK
ADSFEED-FEED-LOOP-BOT: LOG #933 enriches widget typologies
The ADSFEEDBOT-SUP policy in six rules
Six rules for responsible advertising feedback on the widget side.
FEEDBACK-STRUCTURED-BOT: typology_tag before export
UTM-CAPTURE-BOT: utm_capture if ad is cited
SIGNAL-LOG-BOT: signal_log for every objection detected
NO-MARKETING-PROMISE-BOT: no "we correct the ad"
CLIENT-FIRST-BOT: client resolution prioritized over log
ADSFEED-FEED-LOOP-BOT: LOG #933 widget review within 48 hours
Flow ADSFEEDBOT AFB-1 to AFB-8
Flow eight steps: objection detect utm capture tag log cluster handoff export.
AFB-1 Ingest: message pub price delivery promise
AFB-2 Objection detect: contested campaign quote
AFB-3 UTM capture: landing URL campaign_platform
AFB-4 Typology tag: adsfeed_* classifier
AFB-5 Signal log: marketing dashboard export
AFB-6 Cluster check: alert threshold #933 Slack
AFB-7 Client route: handoff #932 #931 if purchase is blocked
AFB-8 Log: capture_rate cluster_check export_ok
Example TPL-ADSFEED-SIGNAL
"Thank you for this report. It has been forwarded to our team. In the meantime: {{aide_client}}."
TPL-ADSFEED templates and touchpoints
Four short feedback embed templates.
TPL-ADSFEED-SIGNAL
[signal_log_copy map.] Report registered. NO-MARKETING-PROMISE.
TPL-ADSFEED-UTM
[utm_capture_prompt map.] Where are you coming from? UTM-CAPTURE.
TPL-ADSFEED-CLUSTER
[cluster_alert_internal map.] Marketing alert. CLUSTER-CHECK.
TPL-ADSFEED-CLOSE
[close_loop_copy_pending map.] Ad under review. FEED-LOOP.
Touchpoints
"Misleading Ad": objection_detect + signal_log
Client blocked from purchase: handoff_support #932
Ad correction done: close_loop copy #933
LOG ADSFEED #933: feed_loop typologies
Edge cases: vague objection, multi-campaign, close loop pending
Five cases outside the standard flow.
Objection without UTM: utm_capture prompt manual platform
Multiple campaigns cited: log separated by campaign_id
Client wants refund: handoff_support #931 not a signal alone
Fix ads pending: CLOSE copy pending no date promise
Duplicate session signal: one log per UTM session
Essential adsfeed_bot KPIs
Five ADSFEEDBOT steering metrics and correlation #933.
adsfeed_bot_capture_rate: structured objections exported to marketing
adsfeed_bot_utm_complete_rate: % of signals with completed UTM
adsfeed_bot_typology_accuracy: % of tags aligned with marketing review
adsfeed_bot_cluster_trigger_rate: % of triggered UTM thresholds
adsfeed_bot_false_promise: target 0 ad correction promises
Target: false_promise at zero and utm_complete above 65%.
ADSFEEDBOT anti-patterns
Five common mistakes in ad bot feedback.
Promising ad correction: NO-MARKETING-PROMISE
Unlogged objection: Systematic SIGNAL-LOG
Ignoring blocked customer: CLIENT-FIRST handoff #932
Generic tag alone: Precise typology_tag adsfeed_*
Duplicating #932: #934 separate marketing analytics customer resolution
ADSFEEDBOT with Qstomy
Qstomy on Shopify: ADSFEED-MAP sync #933, marketing webhook export, Slack cluster alert, SIGNAL UTM templates, adsfeed_bot dashboard.
Scenario: DTC mode, 6-week bot feedback. adsfeed_bot_capture_rate +58%, adsfeed_fix_rate #933 +22 pts via faster detection.
Explore AI support and request a demo.
Checklist, FAQ and going further
ADSFEEDBOT Checklist (8 steps)
Sync ADSFEED-MAP #933: threshold typologies webhook export
Policy ADSFEEDBOT-SUP: 6 rules STRUCTURED UTM-CAPTURE
8 intents bot_adsfeed_*: flow AFB-1 to AFB-8
4 templates TPL-ADSFEED-*: SIGNAL UTM CLUSTER CLOSE
export_webhook: marketing dashboard Gorgias sync
cluster_threshold: aligned #933 5 tickets 24 h
Red team feedback: false promise client-first test
Dashboard KPI: adsfeed_bot_* section 9 + delta adsfeed_
FAQ
Difference #933?
#933 = team process digest fix ads. #934 = automated signal capture bot.
Difference #932?
#932 = client mismatch proof. #934 = marketing analytics export.
Difference #930?
#930 = explain client expiration. #934 = structured objection log.
Does the bot replace tickets?
No if the client is blocked. CLIENT-FIRST handoff #931 #932.
Going further
This week: sync ADSFEED-MAP #933, export webhook, cluster threshold, measure adsfeed_bot_capture_rate.
Enzo
July 1, 2026
