E-commerce
July 1, 2026
"I clicked on the link sticker in your story, the -20% offer is not being applied." "How can I prove I saw the story to get the code?" "Does the story link not count towards your flash promo?" Three tickets where an Instagram story tracked link mixes up attribution, UTMs, and offer eligibility.
The e-commerce Instagram story tracked links support covers proof of click, UTM parameters, attribution window, story code, and sticker link destination. Separate from broken social links (#945), follower offers (#951), and expired story bot (#956).
This guide #955 deploys policy STORYLINK-SUP, flow SL-1 to SL-8, and matrix STORYLINK-MAP. Customer service pair of the future expired story link bot (#956).
Summary
Why do Instagram story links generate attribution tickets?
Instagram stories last 24 hours and often feature a link sticker with dedicated UTMs (utm_source=instagram, utm_medium=story, utm_campaign=flash_juin). The customer clicks, arrives at the store, but the story code does not work or they do not know how to prove their eligibility after the story expires. Without STORYLINK-MAP, the agent grants a gesture without tracking the campaign or denies the offer without checking the attribution_window.
Five typical frictions with tracked story links
Story offer not applied: sticker code rejected at checkout
Proof of eligibility: customer asks how to prove story click
UTMs missing from URL: link without expected tracking parameters
Story expired: offer no longer visible, customer still wants the promo
Wrong destination: sticker leads to incorrect product or collection
DTC fashion example
DTC fashion, 2 tracked stories/week, 9 storylink_ tickets/month. After STORYLINK-MAP: storylink_resolution_rate 83%, ad hoc story gestures -44% in 5 weeks.
STORYLINK #955 vs BROKLINK #945, FOLLEX #951, UTMATTR #935, EXPIAD #929 and bot #956
Seven social story attribution contents, seven distinct angles.
Quick Matrix
#955 STORYLINK: Instagram story tracked link, UTM attribution, offer eligibility
BROKLINK #945: broken social link 404 recovery distinct tracking live
FOLLEX #951: distinct account subscribers offer story tracked link
UTMATTR #935: partner dispute commission distinct end customer story
EXPIAD #929: expired Meta ad offer distinct organic story
ADLC #931: landing promise mismatch distinct UTM attribution
Bot #956: bot retrieve expired story offer tier 1
#944 = dead URL. #955 = live or expired tracked link with attribution eligibility question.
Promise #955
STORYLINK-SUP policy, STORYLINK-GATE tree, 8 macros, tracked stories registry, storylink_resolution_rate KPI.
Which storylink_* typologies should be classified?
Action-oriented classifier: attribution ≠ UTM ≠ eligibility ≠ expiration ≠ destination.
Eight STORYLINK-MAP typologies
storylink_offer_not_applied: story offer code rejected at checkout
storylink_eligibility_proof: customer requests proof of story click
storylink_utm_missing: URL without expected UTMs in registry
storylink_attribution_ask: does story click count for flash promo?
storylink_expired_story: 24-hour story expired but offer still requested
storylink_wrong_destination: sticker leads to wrong product collection
storylink_swipe_fail: link sticker not responding technically
storylink_ops_flag: marketing signal UTM destination story offer
Tags: storylink, ig_story, utm_story, story_attribution. STORYLINK-MAP-GROUNDED: UTM offer from registry only.
Policy STORYLINK-SUP: agent rules and registry of tracked stories
The STORYLINK-SUP policy establishes attribution verification without confirming clicks without proof, nor honoring stories outside the registry.
Six STORYLINK-SUP rules
STORY-REGISTRY-FIRST: verify campaign story registry before responding
UTM-GROUNDED: cite utm_source medium campaign map only
ELIGIBILITY-PROOF: eligible_proof_fields map screenshot timestamp order window
NO-ATTRIBUTION-GUESS: do not confirm click without UTM order or registry proof
OFFER-GROUNDED: story_offer discount code registry only
Handoff #956: brief expired story bot recovery widget
Minimum tracked story registry
storylink_id: campaign story identifier
story_campaign_ref: marketing campaign name
utm_params: source medium campaign content
destination_url: published sticker link URL
story_offer: discount code promised in the story
attribution_window_hours: delay from story click to eligible purchase
eligible_proof_fields: story screenshot timestamp order_ref UTM
equivalent_offer_expired: substitute offer if story has expired
Flow SL-1 to SL-8: ticket processing for tracked story link
Eight steps: intake lookup verify classify proof respond ops log closure.
Flow SL-1 to SL-8
SL-1 Intake: storylink_* intent + UTM URL capture story order_ref
SL-2 Story lookup: STORYLINK-MAP story_campaign_ref match
SL-3 UTM verify: utm_params destination_url live check
SL-4 Classify: offer proof attribution expired destination swipe
SL-5 Proof collect: eligible_proof_fields if eligibility_ask
SL-6 Respond: macro STORYLINK grounded map offer
SL-7 Ops flag: utm missing wrong destination → marketing social
SL-8 Log: KPI storylink + brief correction register
SLA: storylink_offer_not_applied Shopify status code in one interaction if map exists.
Eight STORYLINK-* macros ready to paste
Story attribution macros without ad hoc gesture out of register.
STORYLINK-* Library
STORYLINK-OFFER-01 : "Story offer {{story_campaign_ref}} : code {{story_offer}}. Conditions : {{conditions map}}. Valid {{attribution_window_hours}} h after click."
STORYLINK-PROOF-01 : "Proof of eligibility : {{eligible_proof_fields map}}. Window : {{attribution_window_hours}} h."
STORYLINK-UTM-01 : "Tracked link : {{utm_params map}}. Destination : {{destination_url}}."
STORYLINK-ATTR-01 : "Order {{order_ref}} : UTM {{utm_match}} within window {{attribution_window_hours}} h : {{statut}}."
STORYLINK-EXPIRED-01 : "Story expired 24 h. Current offer : {{equivalent_offer_expired map}}."
STORYLINK-DEST-01 : "Correct destination : {{destination_url map}}. Link flagged to team."
STORYLINK-SWIPE-01 : "Try bio link {{bio_url}} or direct access {{destination_url}}."
STORYLINK-DONE : "Ticket summary {{id}}. Resolution : {{résolution}}."
STORYLINK-GATE tree and social analytics marketing coordination
Decision tree before confirming attribution or honoring out-of-window offer.
STORYLINK-GATE
Story or campaign cited? → story lookup SL-2
Invalid story code? → OFFER-01 + Shopify verify
Eligibility proof requested? → PROOF-01 eligible_proof_fields
Order_ref provided? → ATTR-01 UTM match attribution_window
Expired story but offer requested? → EXPIRED-01 equivalent_offer
Missing UTMs in URL? → UTM-01 ops flag marketing
Wrong destination? → DEST-01 ops flag social
Dead URL 404? → reroute BROKLINK #945
Story go-live ritual D-0
Marketing publishes STORYLINK-MAP: utm_params tested on mobile, story_offer active on Shopify, attribution_window documented. Bot #956 syncs expiry.
KPI, QA and handoff to bot #956
Measuring STORYLINK detects missing UTMs and poorly synchronized story offers.
Five STORYLINK KPIs
storylink_resolution_rate: tickets resolved without ad hoc action
storylink_utm_match_rate: % confirmed story UTM orders
storylink_proof_complete_rate: % eligibility tickets with collected proof
storylink_ops_flag_rate: UTM destination story offer reports
storylink_attribution_guess_violation: click confirmations without proof target 0
Handoff #956
Export STORYLINK-MAP to bot: storylink_expired_story storylink_offer_not_applied priority. Guardrail OFFER-GROUNDED brief #956: bot cites equivalent_offer_expired map only.
Edge cases: highlight, creator collab, ads boost story, GA4 analytics
Four cases outside the standard flow.
Archived story in highlight
Link still clickable: OFFER-01 if story_offer active map. Otherwise EXPIRED-01.
Creator collab tagged story
Distinct creator UTM: check collab row storylink_id. Alignment INFLMIS #949 if promise ≠ sheet.
Paid boosted story
Double tracking paid + organic: prioritize EXPIAD #929 if ads, STORYLINK if brand organic story.
GA4 vs Shopify discrepancy
Analytics attribution: ops handoff, not customer promise on tool discrepancy. Alignment UTMATTR #935 if partner.
Agent training: 20 minutes STORYLINK
Module: STORY-REGISTRY, distinguish BROKLINK #945 FOLLEX #951 EXPIAD #929 bot #956.
Exercises
Ticket A: invalid story code → OFFER-01 Shopify status
Ticket B: proof of eligibility → PROOF-01 attribution_window
Ticket C: expired story → EXPIRED-01 equivalent_offer
Ticket D: 404 link → reroute BROKLINK #945
How Qstomy structures STORYLINK in your stack
Qstomy on Shopify: route storylink_*, UTM stories register sync, OFFER PROOF ATTR macros and handoff #956 expired recovery.
Three building blocks
Routing: intent ig_story_utm vs broken_link vs followers_offer
Story link registry: utm_params story_offer attribution_window proof
Bot #956: tier 1 expired story offer recovery widget
Scenario: DTC mode 2 stories/week. Registry D-0 go-live. storylink_resolution_rate 83%, attribution_guess_violation 0.
Explore AI support, analytics and request a demo.
FAQ and STORYLINK deployment checklist
FAQ
Confirm story click without proof?
No. NO-ATTRIBUTION-GUESS. ATTR-01 UTM order or PROOF-01.
Difference BROKLINK #945?
#945 = 404 dead link recovery. #955 = tracking attribution eligibility live or expired link.
Difference #956?
#955 = agents proof ops UTM. #956 = bot tier 1 expired story recovery widget.
Difference FOLLEX #951?
#951 = offer for follow subscribers. #955 = UTM-tracked story sticker link.
Honor story offer without window?
No without marketing bridge. EXPIRED-01 equivalent_offer map.
STORYLINK Deployment Checklist (8 steps)
STORYLINK-SUP + STORYLINK-MAP: campaign story register template
Tested utm_params: mobile sticker link prior to publication
Shopify story_offer: active code documentation_window documented
storylink_* Tags: storylink_id utm_campaign correlation
eligible_proof_fields: published client-facing
Reroute BROKLINK #945 EXPIAD #929: STORYLINK-GATE tree
Sync bot #956: OFFER-GROUNDED equivalent_offer
20 min training: section 10 exercises
Interlinking
Enzo
July 1, 2026
