Keep a dated record of the five events in the example, because each one answers a different question about progress. Google's generative AI performance report shows impressions by page and date for AI Overviews and AI Mode. HubSpot's AEO tool runs your tracked prompts daily, and its documentation advises reviewing several days or weeks before judging a trend, because responses change. Both tell you about visibility in the surfaces and prompts they cover. Neither tells you a lead qualified.
That part lives in the CRM. Lean Labs describes its AEO reporting as mentions, citations and prompt coverage set beside HubSpot contacts, campaign influence, deals and pipeline. Keeping the two together lets you read the dates side by side, and we cover the setup in how to track traffic from AI answer engines.
Read those dates with one limit in mind. The first citation you observe is the first one your tracking caught, in the prompts you chose to track. The page could have been shown earlier, or for a question you weren't tracking. So a lead that arrives before your first observed citation doesn't rule AEO out, and a lead that arrives after it doesn't prove the page produced it.
What you're building is a consistent record: the same five events and the same definition of qualified, dated for every lead. One lead gives you a single interval. A record kept the same way across many leads is what lets you describe your own timing.