Find qualified WordPress form leads by campaign

A campaign can deliver plenty of WordPress form submissions and still waste the sales team’s time. Raw form counts reward volume. They do not tell you whether the enquiries fit the service, include enough detail, or deserve a fast reply.

The better question is simple: which campaigns send leads your team can actually work? You can answer it without turning Sentient Forms into an attribution platform. Keep your analytics setup as the source of campaign data, store the campaign fields you need with the form submission, and review lead quality alongside those fields.

Start with campaign data your form already stores

Google Analytics uses campaign parameters such as utm_source, utm_medium, and utm_campaign to identify referring campaigns. Its official URL-builder guidance also stresses consistent naming. That consistency matters when the same values reach a form submission.

Sentient Forms does not add campaign tracking fields to your forms. The useful setup is one your site already controls:

• Your campaign links use a stable naming scheme.
• Your form or analytics integration stores the source fields you need with the submission.
• The AI review receives only the source fields and inquiry details required for the decision.
• Your team can trace a review result back to the original WordPress submission.

Do not send a full analytics payload merely because it exists. The same rule applies here as in a good form-data minimization checklist: include the smallest set of fields that can support the review.

Define a qualified lead before asking AI to review one

“Qualified” cannot be a vague synonym for “looks promising.” Write down the business rules first. For a service company, those rules might cover service fit, location, project timing, required information, and whether the request has a clear next step.

A practical review rubric can stay short:

1. Fit: Does the request match a service the business actually provides?
2. Readiness: Is there enough detail to choose the next action?
3. Timing: Is the stated timeline workable, urgent, or unclear?
4. Evidence: Which submitted fields support the result?
5. Handoff: Should staff reply, ask a question, route the enquiry, or close it as a poor fit?

This is where the Lead Scoring action can help. It can produce a review result and rationale from the fields you select. Staff still own the definition, the exceptions, and the final decision.

Compare campaigns by work created, not forms received

Start with a small review window. Twenty recent submissions across a few campaigns can expose data problems and rubric gaps before you build a larger report. For each campaign, record:

• how many submissions arrived;
• how many were ready for a staff next step;
• the most common missing detail or poor-fit reason;
• how often staff disagreed with the AI review; and
• the campaign decision: keep testing, adjust the offer, fix the form, or pause spend.

A campaign that sends fewer forms can be the better campaign if more of those forms become clear, workable conversations.

This does not replace analytics or a CRM. It adds an operational quality signal to the form queue. If you already track review time and handoff quality, connect the result to the scorecard in How to measure ROI from AI review on WordPress forms.

Use a review surface your team can verify

Keep the campaign fields, lead-quality result, rationale, and staff correction together. The exact review surface depends on the supported Form Source. Gravity Forms has the fullest native path. Contact Form 7, WPForms, and Elementor Pro Forms use after-submission workflows through the Sentient Forms Submission Ledger in the current release.

That distinction matters. Do not promise identical native notes, statuses, links, or blocking behavior across builders. Check the current WordPress.org listing before documenting the client workflow.

Avoid three attribution traps

1. Inconsistent campaign names: spring-sale, SpringSale, and spring_sale become separate buckets. Fix naming before judging performance.
2. AI as the source of truth: Treat the review as decision support. Sample disagreements and correct the rubric.
3. Automatic rejection: A thin or unusual submission may still be worth pursuing. Route uncertain cases to a person instead of silently closing them.

The goal is not a prettier dashboard. It is a better spending decision: which campaigns produce workable inquiries, which need a better form, and which are creating follow-up nobody should be doing.

Test the workflow on one campaign

Pick one campaign with enough recent submissions to review. Confirm its source fields, write a five-point quality rubric, and compare AI review with staff judgment before changing spend. Explore the Sentient Forms action library to choose the smallest review step that fits the queue.

Frequently asked questions