Perplexity Traffic Index.
Daily trends in identifiable Perplexity referral traffic.
Current state
Perplexity traffic index is at 30% of tracked peak, with -19.4% over 30 days.
Share of AI traffic
Perplexity accounts for 1.3% of all AI referral traffic across the panel.
7-day momentum
Short-term trend is -11.1% over the last 7 days versus the prior week.
Measure Perplexity referrals in your own GA4
Start with identifiable referrers, then keep a separate view of the traffic GA4 cannot attribute. This recipe mirrors the source matching used by the public panel while keeping uncertain aliases visible for review.
Reference: Google’s GA4 landing page report and PostHog web analytics.
Traffic acquisition report
- Open Reports, then Acquisition, then Traffic acquisition.
- Set the primary dimension to Session source / medium and compare the last 30 days with the previous period.
- Add a filter for Session source, choose Matches regex, and paste this expression.
- Add Landing page + query string as a secondary dimension. Review Sessions, Engaged sessions, Key events, and Total revenue.
^((www\.)?perplexity\.ai|perplexity)$Use a Matches regex filter on Session source. Keep the anchors so tagged campaigns do not match by accident.
Free-form exploration
Views align with this index's GA4 screen-page-view measure. Sessions and key events answer a different question: what happened after the click.
Measure AI landing pages and conversions in PostHog
Use the same source domains, but measure the entrance page and the conversion event in one funnel. This keeps referral volume separate from what visitors did after the click.
Referral and landing-page report
- Open Web analytics, set the last 30 days, and review Acquisition or Referrers for the AI source domains in the table below.
- Compare visitors, sessions, views, and conversion goals by referring domain. Keep broad aliases separate until you have checked the raw values.
- Open Product analytics and create a funnel. Make the first step
$pageview, filtered where$referring_domainmatches the AI source regex. - Use your real signup, lead, checkout, or purchase event as step two. Break down the entrance
$pageviewby$pathnameto compare landing pages.
PostHog fields to use
Filter the entrance event, not every funnel step. A conversion event may not carry the original referrer property.
Perplexity source values and limits
perplexity.ai, www.perplexity.ai, perplexity- Treat perplexity.ai as the high-confidence source. Keep the bare perplexity alias visible in your raw export for review.
- App-to-browser handoffs, redirects, and privacy settings can strip the referrer and move a real click into Direct.
- Referral traffic does not equal citation share. A source link can be shown without being clicked, and GA4 cannot recover the originating answer.
Compare your Perplexity source mix
Use GA4 Views for an apples-to-apples comparison with this public index. The index does not expose an industry baseline for AI views as a share of all website views.
Enter your last 30 days of views to create a baseline before connecting anything.
Keep blind spots and bots in separate reports
- In-app browsers, app-to-browser handoffs, redirects, privacy settings, and referrer policies can strip the source. Those visits can appear as Direct or have an empty referrer.
- Gemini referrals can show as gemini.google.com, but Google AI Overviews and some AI Mode clicks can remain google / organic. Standard web analytics cannot reliably isolate them from conventional Search clicks.
- Treat dark AI traffic as an unmeasured remainder, not a number to relabel. Report identifiable AI referrals as the observed minimum and keep Direct and unassigned movement as a separate watchlist.
- A source domain identifies the sender when the referrer survives. It does not reveal the prompt, answer, citation, or citation position that caused the click.
- AI crawlers are bots, not human referrals. Keep crawler activity in server or CDN logs, and exclude known bots and internal traffic from visit and conversion reporting.
Connect the same workflow to Trakkr
Trakkr’s Visitors view connects Google Analytics, categorizes identifiable AI referrers, and reports landing pages and conversions alongside visibility data.
See Trakkr’s traffic analyticsPerplexity Traffic index since tracking started
Normalized to peak = 100%. Last updated: July 23, 2026
About this data
This index aggregates anonymized GA4 screen page views from properties connected to Trakkr by their owners. Page views are included when the session source matches "perplexity.ai" or a current source alias, then normalized to the highest traffic day (= 100%). Updated daily at 00:00 UTC.
Perplexity page views are identified on sessions where GA4 sessionSource matches perplexity.ai or the current perplexity alias. The index measures referral page views, not Perplexity usage or citation share.
The 3,276 property count is the number of distinct GA4 properties with qualifying Perplexity source data in the current payload. It is not a denominator for every property connected to Trakkr.
The data is first-party and aggregated. Site owners connect their own Google Analytics, and no individual visitor is identified.
What is Perplexity referral traffic?
Perplexity referral traffic is the page views recorded after someone clicks a source link from a Perplexity answer. In Google Analytics 4, the clearest identifiable source is "perplexity.ai".
Perplexity makes source links visible in its answer experience, but a GA4 source row still does not identify the prompt, answer, or citation placement that caused a click. Landing-page and conversion reports answer those separate questions.
The Trakkr Perplexity Traffic Index tracks identifiable Perplexity referral page views daily across 3,276 GA4 properties with qualifying source data, so you can compare your direction with the wider panel.
How much traffic does Perplexity send to websites?
Perplexity referral volume varies by site and period. The live metrics above show its current share and movement across 3,276 GA4 properties with qualifying Perplexity source data.
Does Perplexity referral share equal its user share?
Perplexity makes source links prominent in its answer experience, which creates a clear path to an external site. The public index measures the resulting referral page views, but it does not contain overall Perplexity usage, so it cannot prove a click-through rate versus another platform.
How do you measure Perplexity referral traffic?
Perplexity traffic is measured from GA4 screen page views on sessions whose source matches perplexity.ai or its current alias. Trakkr aggregates anonymized property data and normalizes the series to the highest-traffic day (= 100%) without exposing absolute panel volume.
Is Perplexity referral traffic growing?
The direction changes over time. Use the current 7-day and 30-day values above instead of assuming a permanent growth rate, and compare a longer period when the daily series is volatile.
Does the Perplexity index include an industry breakdown?
Only when the current payload contains source-by-industry cells that clear its minimum property threshold. The page hides that section when no qualifying breakdown is available instead of estimating it.
How can I track Perplexity traffic to my own website?
Use the GA4 recipe and calculator on this page before signup. You can then connect your Google Analytics property to Trakkr to categorize identifiable AI referrers and compare your source mix with the public panel.
Benchmark your Perplexity traffic against the market
Connect Google Analytics to compare your Perplexity trend with category baselines and source-mix shifts.