Measure Traffic from AI Assistants

Two kinds of AI-related activity can reach your website: an agent requests a page, or a person follows an assistant's link. Use Acquisition for attributed visits and AI Visibility for identified agent requests.

Find attributed AI traffic

Open Acquisition and set the tenant, website source, dates, and timezone. Use AI Focus in Traffic Distribution to examine the AI-related traffic recognized by that report. Read source, medium, and channel together; a campaign label alone does not prove how someone discovered you.

Review Configuration before comparing conversion results. Use the same conversion events, attribution model, lookback, and traffic scope as your other channel analysis. Where the tenant supports Commerce, include revenue in the review.

Inspect the destination and journey

Check the relevant landing pages in Engagement → Pages, using the available attribution details for context. Inspect a session when you need to understand a specific visit. Use a funnel to measure a defined sequence such as product view → cart → purchase.

Then open AI Visibility for the same reporting period to see identified agents and the pages they requested. This provides a separate view of machine access; it is not a count of the people referred by those systems.

Interpret coverage carefully

Referrers and campaign context can be absent or lost during navigation. Hardal cannot infer every AI-assisted discovery from a direct visit. A recorded agent request also does not prove that the page appeared in an answer or generated a later sale.

Keep the two results separate in your marketing report: attributed website activity and agent-page coverage. Link the analysis to AI Visibility and Inspect AI Agent Traffic, rather than adding their totals together.

For the underlying request measurement, read How AI Bot Tracking Works. Use the weekly AI Visibility report to present agent access and referred website outcomes separately.