You get enquiries through a contact or quote form, and you want to know how many came in last month. You also want to know which campaigns and channels sent the people who filled it in. A pageview count can’t answer that. It tells you people visited, and the form tells you somebody wanted to talk. You need the two joined.

Vireo Analytics, our free cookieless analytics plugin for WordPress, joins them without Google Analytics 4 or Google Tag Manager. If your site uses one of the common form plugins, Vireo counts each enquiry that went through, straight from the form plugin, with no tag setup. Vireo Pro then shows the source, medium and campaign behind each one. Vireo never keeps what the visitor typed.

How the usual GA4 route works

Google Analytics 4 has two common routes. The first is enhanced measurement, which includes form interactions. It sends a form_start event the first time a user interacts with a form in a session. It sends a form_submit event when the user submits one. Google’s page doesn’t say whether form_submit counts only successful submissions. The event parameters also need custom dimensions before you can use them in reports.

The second route is the thank-you page. Google’s help on creating key events covers this case. You enter the confirmation page’s URL, and the event fires when someone submits their details and lands there. You then mark it as a key event, which Google defines as “an event that measures an action that’s particularly important to the success of your business.” If your form shows a message on the same page instead, there’s no page to match.

Google Tag Manager offers a Form submission trigger. Its “Check Validation” option makes the trigger “fire only if the form is successfully sent”. Unticked, it fires on every attempt. Either way, you’re setting up and maintaining a trigger and a tag in a second tool.

Which form plugins Vireo counts on its own

Vireo records a form_success event when a supported form plugin accepts a submission. It listens to each plugin’s own server-side hook, which runs only once the submission has been accepted. All of this is in the free plugin, which supports:

  • Contact Form 7, after the form’s mail is sent
  • WPForms, when processing is complete
  • Gravity Forms, after submission
  • Fluent Forms, when the submission is saved
  • Elementor Pro forms, when a new record is created
  • Ninja Forms, after submission, once every field and action has passed
  • Formidable Forms, after an entry is created
  • Forminator, after an entry is saved and the response reports success
  • Breakdance, through an action you tick on the form

The first eight work with no setting at all. Vireo adds a listener for each plugin that’s active on your site and ignores the rest.

Breakdance works differently, so Vireo adds a “Vireo Analytics” action to the form’s “Actions after submission” list. Tick it on each Breakdance form you want counted. Breakdance runs ticked actions once the submission has passed its checks.

Only submissions that went through

A visitor who bounces off a required field never reaches those hooks, so that attempt isn’t counted. For Ninja Forms, Formidable and Forminator, drafts, spam, failed submissions and builder previews are skipped as well.

Bots and excluded traffic are left out too. Before recording anything, Vireo applies the same check its tracker applies to pageviews. A bot, an excluded IP address or an excluded role submitting the form doesn’t count. Logged-in administrators are excluded by default, and you can change who’s excluded in the excluding traffic settings.

If you send a test enquiry while logged in as an administrator, Vireo won’t count it. Test logged out, from an address you haven’t excluded.

Vireo also has an optional form_submit auto-event, under Settings, Tracking, Auto-events, “Form submissions”. It’s off by default. It fires on every browser submit, which happens before validation, so a form that bounced on a required field counts the same as one that sent. form_submit skips forms from the supported plugins, so a failed attempt isn’t counted beside the one that went through. Hand-built forms and forms from other plugins use form_submit.

Where the numbers show up

This part is free. Open Vireo Analytics, then Overview, then the Campaigns tab. The “Top events” card lists each event with its Count and Unique visitors for the date range. Click form_success to open its own screen: Total count, Unique visitors, Distinct values, a chart of Daily counts, and Top values.

The event’s value is the form’s id and title, for example “#3 Contact us”. For form_success, the Top values list is your forms, so you can see which form brought in how many enquiries. The titles are your own labels, and Vireo records nothing the visitor typed. The events documentation has more detail.

The event records the form’s id and title. To tell pages apart, give the form on each page its own title, or use separate forms.

Turn enquiries into a goal

Goals are a Vireo Pro feature. In Pro, go to Vireo Analytics, Goals, then “Add goal”. Give it a Name, such as “Enquiry”. Set Type to “Event” and Pattern to form_success. Add a Value if you want one, keep Active ticked, and click “Create goal”.

“Preview against historical data” runs the pattern over the last 30 days, so you can see what the goal would have counted before you save it. The goals list shows “This week” and “All time” completions. On the Overview’s Campaigns tab, the Goals card shows each goal’s Completions, Rate and Value. Rate is the share of visitors who completed the goal.

A goal on form_success needs free Vireo Analytics 0.22.1 or later. Before that version, only events sent from the browser completed goals. Version 0.22.1 made a goal on form_success, or on any other event recorded by a form plugin or by code on the server, count its completions. The goals and funnels documentation walks through the screens.

Which campaigns bring leads

Vireo Pro 1.10.0 adds a “Leads by source” card to the Campaigns tab. It needs free Vireo Analytics 0.22.1 or later. The card counts accepted form submissions by the Source, Medium and Campaign the visitor arrived from. A Forms column shows which forms they used, and you also get the change on the previous period of the same length.

It stores counts only. The table keeps the date, form, source, medium, campaign and two counts. It holds no visitor hash, no IP address and no field contents.

The two counts work differently. Leads counts submissions. People counts each visitor once a day per source, medium and campaign, so someone who sends the same form twice in a day counts as one person.

The Conversion rate divides those people by the visitors counted from the same tagged link. That means a rate exists only for links with UTM tags. Visitors from search, social and plain referrers show no rate rather than a guess. If you haven’t tagged your campaign links yet, the UTM links guide shows how.

Vireo works out the source the same way Pro credits sales, from the visit’s UTM tags or else its referring site. A lead and a sale from the same campaign land under the same labels.

The card credits each form to the source that first brought the visitor, within a 48-hour window, using the same daily secret that tells visitors apart.

Pro 1.10.0 also adds a get-leads-by-source ability, so Ask Vireo and connected AI assistants (MCP clients) can answer which campaigns bring leads.

For developers

The free plugin fires a vireo_form_success action after each accepted submission is counted. It’s new in 0.22.1. The action receives three arguments: the event value (form id and title), the form plugin’s id for the form, and the form’s title. It runs after the same bot and exclusion check, so it doesn’t fire for bots or excluded traffic.

add_action( 'vireo_form_success', function ( $value, $form_id, $title ) {
    // For example, write the form's name to your debug log.
    error_log( 'Enquiry counted: ' . $value );
}, 10, 3 );

To switch form_success tracking off, return false from the vireo_track_form_success filter.

For any other form, call vireo_track_event( 'name', 'value' ) from your own server-side code to record an event. The hooks reference lists Vireo’s other hooks.

Setting it up

If one of the plugins above runs your form, the free plugin is already counting. On Breakdance, tick the Vireo Analytics action first. Send a test enquiry while logged out, then check Top events on the Campaigns tab. To see where enquiries come from, add UTM tags to your campaign links and open Leads by source in Pro. If you’re moving off GA4 altogether, removing Google Analytics from WordPress covers that side.