AI sent them. Count what they bought.
Viz credits every purchase, booking, lead and sign-up on your site to the assistant that sent the visitor: ChatGPT, Perplexity, Gemini and ten more, with conversion rate and value per assistant. Captured inside WordPress from the plugins you already run, no tag manager, no Google connection. Agent leads and purchases land in the same table; see Agent tools.
Cited is not the metric.
AI visibility dashboards stop at the mention. The money happens later, in your checkout, your booking calendar and your contact form, and Viz is already there. So the proof runs all the way: crawled, cited, visited, converted.
From an assistant's link to a line in your ledger.
An assistant sends a visitor
Someone asks ChatGPT or Perplexity a question, gets your site in the answer, and clicks. Viz recognizes the assistant that sent them at the server, as it already does for referral visits.
Viz remembers who sent them
With cookie consent, the visitor gets one signed first-party cookie naming the assistant and the landing page, for 30 days. No personal data, and nobody else gets one.
They buy, book, enquire or sign up
Your existing plugins fire their usual hooks. Viz records a conversion with the kind, the value and the landing page, and nothing that identifies the person.
The assistant gets the credit
The AI Conversions tab shows visits, conversions, rate and value per assistant, by kind, by landing page, and trended against all conversions on the site.
Four kinds of conversion, thirteen assistants, one table.
Attribution is only as good as its denominator. Viz counts every conversion on the site, not just the AI ones, so AI share means something.
Purchases
WooCommerce and Easy Digital Downloads orders, with order value and currency. A WooCommerce order that contains a bookable product is counted as a booking.
Bookings
WooCommerce Bookings and MotoPress Hotel Booking reservations, recorded the moment the booking is confirmed on your server.
Leads
Submissions from Contact Form 7, Gravity Forms, WPForms, Fluent Forms, Ninja Forms and Formidable, plus anything an AI agent submits through the contact_business tool or /ai-contact/.
Sign-ups
WordPress user registrations and LearnDash or LifterLMS course enrolments.
Your own events
Anything else that counts as a conversion on your site: one line of PHP, do_action( 'vizwp_conversion', … ), and it shows up next to the rest.
Credited to the assistant
Every conversion is credited to the assistant that sent the visitor, so the dashboard reads per assistant: visits, conversions, rate, value.
One next step, shown only to the visitors AI sends. To half of them.
An AI-referred visitor lands deep, already half-decided. Landing Paths adds a short server-rendered note to the page - “Arrived from ChatGPT? Here's the next step” - with one button to the best action page on your site: booking, shop, quote or contact. Half of those visitors see it, half see the page as-is, and the dashboard reports the lift. A controlled experiment, with no JavaScript and no tag manager.
A - with Landing Path block
5.8%
156 landings · 9 conversions
B - page as-is
3.2%
156 landings · 5 conversions
Lift
+81%
A vs B conversion rate
Illustrative numbers. The block never renders on cart, checkout or account pages, and never for logged-in editors.
When an agent comes to act, it finds tools.
Every page registers WebMCP tools an agent in the visitor's browser can call, and /ai-contact/ takes requests from agents that never open one. Both end up here: a contact request becomes a lead, and a purchase that follows a tool call is credited to the agent.
Book, buy, check prices, browse: what agents came for, next to what humans do.
Viz sorts what AI agents came to do on your site and shows it beside the same numbers for humans, with a trend, a table of recent high-intent visits and a breakdown per agent. Segments let you define what counts as a high-intent request for your business and flag it for the daily digest. The first time an agent tries to act on your site, Viz tells you.
High intent
Agents that came to act or check availability: booking pages, checkout, quote forms, date searches. Shown next to the same count for humans, so you can see how agent demand compares.
Price intent
Agents that came for your pricing, rates, plans or fees. The first question an assistant answers before it recommends you.
Browsing
Agents reading your catalog, listings, products or services. The long tail that becomes a recommendation later.
Prefer email? An opt-in daily digest lists yesterday's agent leads, AI-attributed conversions and agents that tried to act, only on days when something happened.
Five questions an agent asks. A grade for each.
Before an assistant can recommend you, book you or quote you, it has to get an answer from your site. Viz reads your content types, your commerce and booking plugins and your structured data, then fetches a few pages the way an AI crawler would, and grades each question ready, partial or none, with where that answer actually lives. The five verbs are also what the WebMCP tools answer.
Describe
what you offer
List
browse your entities
Price
how much it costs
Availability
what is in stock or bookable
Act
book, buy, enquire
If your availability lives in Calendly or your prices in Shopify, an agent reading your site cannot get them. The map says so, and the grade caps at partial until it can.
Attribution without a data problem.
One cookie, and only for some visitors
A single first-party cookie, set only for visitors who arrive from an AI assistant, for 30 days. It carries the assistant name, the landing page, a timestamp, an internal visit id and an A/B arm. No personal data, and it is signed so it cannot be forged. Nobody else gets a cookie.
Consent comes from your banner, not ours
Viz never shows a consent banner. It honours the WordPress Consent API and CookieYes: no analytics consent, no cookie, no attribution, no landing block.
Conversions carry no personal data
A conversion is a kind, a source, a reference id, a value and a URL. Names, emails and messages never enter the conversions table, and never sync to Viz Cloud.
Leads never leave your site
Agent-submitted leads are stored only in your WordPress, emailed to you, covered by the WordPress personal-data export and erase tools, and kept for as long as you choose.
AI Conversions FAQ.
Do I need Google Analytics for this?
No. Conversions are captured on your server from the plugins you already run, and attributed to the assistant that sent the visitor without any Google connection, tag manager or pixel. Linking GA4 remains optional and adds session depth (how long AI-referred visitors stayed, what they engaged with) on top.
My AI-attributed number looks small. Is it wrong?
It is a floor, not a ceiling. Some assistant apps open links without a referrer, so a share of AI-sent visitors books as direct and cannot be credited. Read the rate rather than the count: if AI-referred visitors convert above your site average, the channel is working and the true volume is higher than the chart shows.
Is AI Conversions a paid feature?
No. Attribution, Landing Paths, segments, agent requests, the capability map, /ai-contact/ and the WebMCP agent tools are included on every plan, including Free. Paid plans keep more history: 7 days on Free, 90 on Lite, 365 on Pro.
Does it add JavaScript or slow the site?
No third-party JavaScript, and no tag manager. Viz prints two small first-party inline scripts with no external requests: one that only runs for visitors arriving from an AI assistant, and one that registers WebMCP tools in browsers that support the standard. Conversions are recorded by the same server hooks your commerce and form plugins already fire.
Which plugins are supported?
WooCommerce, Easy Digital Downloads, WooCommerce Bookings, MotoPress Hotel Booking, Contact Form 7, Gravity Forms, WPForms, Fluent Forms, Ninja Forms, Formidable Forms, LearnDash, LifterLMS and WordPress user registration. Anything else can report a conversion with do_action( 'vizwp_conversion', … ). If your bookings or prices live in an embedded service such as Calendly or Shopify, the capability map tells you so, and why an agent cannot read them from your site.
Are AI agents really submitting forms today?
Rarely, so far. What is already common is agents fetching pricing, booking and contact pages on someone's behalf and leaving with nothing they can act on. The tools exist so that when one comes to act, your site is the one that lets it: a WebMCP tool call in the visitor's browser and a submission at /ai-contact/ are logged the same way, and you learn about either the same day rather than the year after.
What does the Landing Path block show, and can I change it?
A short "Arrived from ChatGPT?" note with one next step: the button defaults to the best action page Viz found on your site (booking, shop, quote, contact) and you can override the headline, label and link. It only renders for AI-referred visitors, never on cart, checkout or account pages, and never for logged-in editors.