A guide “helps” if the customer can finish the job without guessing. You judge that from activity on the Product Experience you operate: scans, which guides opened, questions asked, warranty registrations submitted to you. You do not judge it from an invented conversion rate or from a marketplace buyer list MyQRGuide never receives.
The category essay is the data blind spot after the sale. Explore Product Intelligence: Product Intelligence After the Sale. How to open reports: AI Smart Reports. Plan names and which reports you get stay on Pricing — Product Intelligence is listed on Silver and above.
Questions the data can answer
| Ask | If yes | If no / unclear |
|---|---|---|
| Did people scan? | The code is findable. Next: did they open first-use? | Check placement and scan testing before rewriting the guide. |
| Did they open the first-use guide? | The page is reachable. Next: same symptom in tickets or questions? | The scan may land on the wrong Mini Site, or the first step is buried. |
| Do the same questions repeat? | Put the answer in HTML using the troubleshooting template. | You may not have enough signal yet. Do not invent a percentage. |
What this is not
- A ranking or AI-citation score
- Proof that every scan became a sale or a registration
- Marketplace reporting. If the customer never scans, you may have no post-purchase signal at all.
Illustration
This is a labelled example, not a customer case study and not a dashboard screenshot.
Noise. “Engagement is up 40%.” No definition, no date range, no link to a missing step. Nobody changes the guide.
Useful. Scans happen. The first-use guide is opened. The same “pump hums, no water” question still arrives. You add that section to the live Smart Guide and keep the QR URL. Then you watch whether that question appears less often — still not a guaranteed rate.
Repeated setup gaps are covered in when setup problems become support tickets. Warranty submissions stay private even when you count that a registration happened.