Before you start
You need a site already collecting data in Fathom, access to the Fathom API on your account, and permission to manage integrations for your ChatFeatured project. This integration reads your existing analytics. It does not install Fathom’s tracking script.Connect Fathom
1
Create an API key
In Fathom, open Settings → API and click Create new. Name the key and choose its permissions. Read only (all sites) or a site-specific key is enough. Copy the key when it is shown, because Fathom will not display it again.See Fathom’s API key guide for details.
2
Open the integration
Select your project in ChatFeatured, then go to Integrations → Website analytics → Fathom Analytics.You can also choose Connect your analytics from Website Analytics or the Website Traffic widget.
3
Enter your key and pick a site
Paste your API key and click Find my sites to choose from the sites the key can see.Site-specific keys cannot list sites. Enter the Site ID by hand instead. It is the short code in your Fathom tracking snippet and site settings, such as
ABCDEFGH.Click Connect Fathom Analytics. ChatFeatured checks that the key can read the site before saving anything.4
View your reports
Click View website analytics. Fathom becomes the selected provider for this project in your browser.
What you can see
- Visitors, pageviews, and daily trends.
- AI referral traffic by platform, including ChatGPT, Perplexity, Claude, Gemini, and Copilot.
- Landing pages, traffic sources, bounce rate, and average visit duration.
- Conversions from the events you track in Fathom.
How Fathom’s numbers map
Fathom does not measure sessions. Sessions and Users both show Fathom’s visits, which is the number Fathom’s own dashboard labels visitors. Expect them to match each other, and to differ from GA4 or Plausible for the same dates. Conversions counts completions of your Fathom events, read from the first 10 events on the site. ChatFeatured’s conversion rate divides conversions by visits. Revenue is not read from Fathom yet and displays as —. AI referrals are recognized from the campaign source (utm_source) first and the referring site second. A visit with neither cannot be attributed to an AI platform.