To check traffic from Perplexity, start with visits from people who clicked through to your site. In Hardal Acquisition or GA4, filter the session source for perplexity.ai. Hardal can also report anonymous sessions when a visitor declines identity cookies, if your collection setup permits them. Then check your server or CDN logs for PerplexityBot and Perplexity-User. Those requests measure access to your pages, not human visits. To measure visibility in Perplexity answers, test a consistent set of relevant questions and record whether your pages are cited.
| What you want to know | Where to look | What it measures |
|---|---|---|
| How many visits came from Perplexity? | Hardal Acquisition or GA4, filtered by session source | Attributable sessions and their conversions |
| Which pages did Perplexity access? | Server or CDN logs; Hardal AI Visibility | Bot requests by agent, page, and time |
| Does Perplexity show or cite my content? | Repeated checks of relevant questions in Perplexity | Observed answer visibility |
Keep these numbers separate. A crawl does not prove a citation, and a citation does not prove someone clicked.
How to find Perplexity traffic in Hardal or GA4
In Hardal
- Open Reports → Acquisition in the Hardal Dashboard. Set the reporting period and open Configuration.
- Choose All Traffic to include both consented and anonymous sessions. Select the conversion events you want to measure.
- In Traffic Distribution, filter the source for
perplexity.ai. Compare sessions, conversions, and conversion rate. Switch to Unconsented Traffic to see the anonymous portion using the same date range. - Open Engagement → Sessions to inspect the landing pages and session context behind those visits.
Hardal can collect anonymous session and source data when a visitor declines identity consent. It removes identity fields and clears the identity cookie, while session-level measurement can continue. This makes the All Traffic view useful when a consented-only view misses part of your Perplexity audience. Collection still depends on your implementation, consent policy, and applicable requirements. See Hardal's Acquisition and consent signals guides.
In GA4
- Open Reports → Acquisition → Traffic acquisition in GA4.
- Set the primary dimension to Session source / medium, then search for
perplexity.ai. If your property has an AI Assistant channel, use it for a broader view, but filter by source to isolate Perplexity. - Compare sessions, engaged sessions, and key events over the same date range. Add Landing page as a secondary dimension to see which pages received visits.
Both tools need a usable source signal to attribute a visit to Perplexity. If a click arrives without a referrer or tracking parameters, it may appear as Direct. Neither Hardal nor GA4 can reliably recover those missing Perplexity visits by relabeling every Direct session. See Google's traffic-source documentation for how GA4 source attribution works.
Google Search Console answers a different question. Its clicks and impressions tell you how this page performs in Google Search, not how much traffic Perplexity sends to your site.
How to check PerplexityBot and Perplexity-User
Perplexity publishes two user agents with different jobs:
PerplexityBotcollects pages so Perplexity can surface and link them in search results. It is not a human visitor or a model-training crawler.Perplexity-Usermay fetch a page in response to a person's action inside Perplexity. A fetch is still not a click-through session or proof that your page appeared in the final answer.
In your server, CDN, or WAF logs, filter the User-Agent field for each name separately. For each request, record the requested URL, timestamp, HTTP status, and IP address. Count successful page requests by URL and check whether important pages return 200, redirects, 403, or 404. A user agent can be spoofed, so compare IPs with Perplexity's published ranges before treating a request as genuine.
Browser analytics will usually miss these requests because bots do not need to run your page's JavaScript. If you use Hardal AI Visibility, send original request metadata from your server or CDN. Its agent report can then group recognized Perplexity requests by page and agent. The setup guide shows the required fields and verification step.
How to measure visibility in Perplexity answers
Bot activity is an access signal. To see whether Perplexity actually uses your content, make a small list of questions your buyers ask, including product, comparison, and problem-solving queries. Run the same questions on a regular schedule and record the date, question, cited URL, and whether your brand appears in the answer. Keep the question set and checking method consistent so changes over time mean something.
Use three separate lines in your report: cited answers, referral sessions, and bot requests. Referral sessions show people who reached your site with an identifiable source. Answer checks show observed visibility. Bot requests show which pages Perplexity accessed. None of these alone gives you a complete count of every Perplexity search that mentioned your site.
Check access before diagnosing low visibility
If PerplexityBot never reaches a page, check your robots.txt, WAF rules, and response status. Perplexity recommends allowing PerplexityBot if you want your site to appear in its results:
User-agent: PerplexityBot
Allow: /
Its crawler documentation says Perplexity-User generally ignores robots.txt rules because it acts on a user's request. Allowing the indexer is only one prerequisite: it does not guarantee a crawl, citation, or visit. You can also use isvisible.ai to check whether Perplexity's agents can access your site.
Start with the number you need: Hardal or GA4 for attributable human visits, request logs or Hardal AI Visibility for bot access, and repeatable answer checks for citations. Use Hardal's All Traffic scope when eligible anonymous sessions matter. That gives you a useful Perplexity report without calling every bot request “traffic.”