What it means
Source attribution is the audit trail that makes AI support trustworthy — it's the difference between 'the AI said so' and 'the AI derived this from your written policy.'
Source attribution is closely related to answer citation but broader in scope. While answer citation is the customer-facing presentation of sources, source attribution is the underlying technical and operational practice of recording provenance throughout the AI response pipeline. A fully attributed AI response pipeline tracks: which documents were retrieved from the knowledge base, what retrieval confidence scores applied, which document segments were injected into the LLM context, and how the final response maps to those segments. This full attribution chain is primarily valuable internally — for support managers debugging response quality, for product teams improving retrieval accuracy, and for merchants who want to audit which knowledge base documents are driving the most customer-facing responses. In regulated verticals or high-stakes support contexts, source attribution also provides an important accountability record: if a customer acts on an AI response and a dispute follows, the attribution record shows exactly what information the AI had access to and used.
Why it matters
For Shopify merchants, source attribution matters most when something goes wrong. A customer received incorrect shipping information and is demanding compensation — was the AI citing an outdated shipping page, or did it fabricate information? Source attribution answers that question definitively. It also reveals optimization opportunities: which knowledge base documents are retrieved most frequently (probably worth expanding), which are retrieved but never cited in final responses (may be poorly chunked or indexed), and which topics generate queries with no good retrieval match (knowledge gaps to fill).
How Bookbag helps
Full Retrieval Provenance Logging
Bookbag logs the complete retrieval chain for every AI response — which documents were retrieved, their relevance scores, and which segments influenced the final answer — accessible to merchants in the analytics dashboard.
Response Trace Debugger
For any conversation, merchants can open Bookbag's trace view and follow the exact reasoning chain: customer message → intent detected → documents retrieved → response generated, with source mapping at each step.
Knowledge Base Usage Analytics
Bookbag surfaces which knowledge base documents are cited most frequently, which are retrieved but not used, and which topic areas have no good source material — directly guiding knowledge base investment.
Frequently Asked Questions
See Bookbag in action
Join the ecommerce teams resolving more tickets, answering 24/7, and turning support into a revenue channel with Bookbag.