Sign-ups from AI, counted from your own traffic
Sign-ups from AI counts the visits AI assistants send to your site and the sign-ups that come after them, read from your Cloudflare logs rather than a browser tag. You set which pages count as sign-up pages and which referrer field to note. It is for SaaS and lead-gen teams who need one plain number: how many new accounts AI search produced.
From Cloudflare Logpush. Sign-up pages: /signup, /start.
Sign-ups from AI, in short
The facts, ready to quote.
- Counts
- AI assistant visits and the sign-ups that follow them
- Data source
- Your Cloudflare logs (Logpush), so ad blockers and consent banners do not hide visits
- Your settings
- Which paths are sign-up pages and which referrer field to note, kept per organization
- Also available
- Through the Proofsource API for your own reporting
Sign-ups from AI. Counts AI assistant visits and the sign-ups after them from your Cloudflare logs, in the app and through the Proofsource API for your own reporting.
Sign-up pages and referrer settings. Set your own sign-up paths and the referrer field to note, per workspace.
AI sign-up attribution, explained
AI sign-up attribution links new accounts or leads to the AI assistant that sent the visitor. If someone asks ChatGPT for the best AI meeting notes tool, clicks your link in the answer and creates an account, that sign-up is credited to AI search instead of disappearing into direct traffic.
Browser analytics often undercounts this path. Consent banners, ad blockers and privacy settings stop tags from firing, and many sign-up flows move across domains or apps. Edge logs record every request regardless, so they give a steadier count of visits and of the sign-up pages reached after them.
Proofsource reads your Cloudflare logs, recognizes visits referred by AI assistants and counts the sign-ups that follow, using the sign-up paths you set for your workspace. You also choose a referrer field to note, such as a utm_source value, so campaign tags line up with your own reporting.
How it works
Counts the visits AI assistants send and the sign-ups that follow, from your Cloudflare logs, using the sign-up pages you choose.
Connect Cloudflare logs
Proofsource reads AI-referred visits from your Cloudflare Logpush data.
Name your sign-up pages
List the paths that mean a new account or lead, such as /signup or /start.
Choose a referrer field
Pick the field to note alongside each visit, such as utm_source, so tags match your reports.
Read the count
See AI visits and the sign-ups after them on the Sign-ups from AI screen, or pull them through the API.
See it in the product
Screens from the Proofsource app, drawn with sample data for an example brand.
Who it is for
Know if AI search grows the business
See new accounts that came after ChatGPT or Perplexity visits, not only mentions.
Add AI to the channel report
Put AI-referred sign-ups next to paid, organic and referral in the monthly review.
Count leads, not just traffic
Mark your form or booking pages as sign-up paths and count leads AI sent.
Why it matters
Fewer missed visits
Edge logs record AI-referred visits even when a browser tag is blocked.
Your definition of a sign-up
You choose the paths that count, so the number matches how your business works.
A number leadership understands
Sign-ups from AI is the plainest proof that AI visibility pays.
Google AI OverviewsGoogle AI Mode
Sign-ups from AI: Proofsource and other tools
Conversion data from AI search is described in different ways across the category; this is what each public page says.
| Capability | Proofsource | Profound | Peec AI | Semrush | Ahrefs |
|---|---|---|---|---|---|
| Conversions after AI visits | YesSign-ups after AI assistant visits, from edge logs | RelatedGA4 node pulls sessions, users, conversions, revenue into agentsSource | RelatedGoogle Analytics 4 connection for traffic, engagement, conversions, revenueSource | RelatedPreset widget for AI referral traffic and conversions from Google AnalyticsSource | RelatedWeb Analytics (free) shows pages receiving visitors from AI searchSource |
| Counted from logs, not a tag | YesReads Cloudflare Logpush data | RelatedLog-based tracking for AI bots, not a JS trackerSource | Not listed | Not listed | Not listed |
| Custom sign-up paths | YesYou choose which paths count as sign-ups | Not listed | Not listed | Not listed | Not listed |
| AI referral traffic | YesCounts the visits AI assistants send | YesMeasures human visits from AI search and its effect on overall trafficSource | Not listed | YesMy Reports preset widget for AI referral traffic and conversions from Google AnalyticsSource | Not listed |
| Cloudflare connection | YesReads your Cloudflare logs | RelatedServer logs, not JS tracker; forwarding from AWS, Akamai, Cloudflare, Fastly, GCP, Netlify, VercelSource | RelatedBot visit insights via CDN and log providers; Cloudflare, CloudFront, AkamaiSource | Not listed | Not listed |
| API for the data | YesRead or send sign-ups through the Sign-ups from AI endpoints | YesPull Profound data into own apps, reports and pipelines; SDKsSource | YesPro and above; actions, content, shopping, brand perception endpointsSource | RelatedA Semrush API for its dataSource | YesAhrefs API v3 with Brand Radar reports; metered in API units per rowSource |
Where each of them shines
GA4 data, including conversions and revenue, pulled straight into automated marketing agents. Compare in full
A clean GA4 connection covering traffic, engagement, conversions and revenue. Compare in full
AI referral traffic and conversions in My Reports, next to every other channel in a full SEO suite. Compare in full
A large prompt index plus free AI referral and crawler analytics. Compare in full
Questions about Sign-ups from AI
How do I know how many sign-ups came from ChatGPT?
Connect your Cloudflare logs and tell Proofsource which pages are your sign-up pages. It counts visits referred by ChatGPT and other assistants and the sign-ups that follow them.
Why use logs instead of Google Analytics?
Consent banners, ad blockers and privacy settings can stop browser tags from recording a visit. Edge logs see every request, so AI-referred visits are less likely to go missing.
Which assistants are counted?
Visits whose referrer is an AI assistant, such as ChatGPT, Perplexity and Claude. Assistants that pass no referrer cannot be told apart from direct traffic by any tool.
What counts as a sign-up?
A visit that reaches one of the sign-up paths you set for your workspace, for example /signup or /start. You can change these at any time.
What is the referrer field setting?
It tells Proofsource which field to note with each visit, such as utm_source, so its counts line up with the campaign tags you already use.
Do I need Cloudflare?
Sign-ups from AI reads Cloudflare Logpush data. For conversion counts from analytics instead, connect Google Analytics 4 and use AI Referrals and the AI Funnel.
How is this different from GA4-based conversion tracking in Peec AI or Semrush?
Those read conversions from Google Analytics, which works well when tags fire. Proofsource can also count from your edge logs with sign-up paths you define, which helps when consent or blockers hide part of your traffic.
Which AI engines does Proofsource track?
Proofsource tracks up to 10 AI engines, depending on your plan: ChatGPT, Perplexity, Claude, Google AI Overviews, Google AI Mode, Gemini, Microsoft Copilot, Grok, DeepSeek and Meta AI. The free scan and free trial run four of them: ChatGPT, Perplexity, Claude and Google AI Overviews.
Keep exploring
Try it on your own brand.
Proofsource is live: scan your brand and see Sign-ups from AI at work with your own answers, competitors and sources.
Google AI OverviewsGoogle AI Mode