Write down what counts before installing tags

Agree on a lead definition with the person who handles calls. For one contractor, a valid lead may be a new customer in the service area asking for a covered repair. For another, it may be a commercial estimate request that meets minimum project criteria. Exclude spam, job applications, vendors and duplicate forms when possible.

Choose separate events for meaningful stages. For example, record a genuine form confirmation as a lead, and keep a walkthrough button click as a navigation event. This prevents an ad platform from learning that a person who merely opened the form is equivalent to someone who submitted it.

  • Lead: validated new inquiry submitted through the intended path.
  • Qualified inquiry: fits service, area and job type after human review.
  • Booked or sold: confirmed by the company’s scheduling or business records.

Make the conversion signal match the completed action

A page-load conversion works only if the page is reached after a successful submission and cannot be opened as a normal page. If the form stays on the same page, redirect behavior may not exist. A third-party embedded form can also submit inside a cross-origin iframe, where the host website cannot inspect the submit button or success state directly.

Use the form provider’s supported success event, verified post-submit redirect or server-confirmed event when available. Avoid a click trigger on the submit button as the final lead signal: client-side validation can reject the form after the click, and a double click can create duplicate events. Test the complete journey in Tag Assistant and the analytics debug view.

  • For a real confirmation page, ensure only a successful response can reach it.
  • If using a provider callback, confirm it fires after the provider confirms success.
  • Keep click and form-start events separate from generate_lead.

Preserve campaign information responsibly

Campaign parameters and click identifiers can help match a website visit to a campaign, but they should be handled under the site’s consent choices and privacy practices. Preserve the original source values through the inquiry when the implementation allows it and consent is in place. Do not overwrite a known source with direct traffic on a later page.

Test source capture with a real tagged test URL that does not create a production lead. Verify the landing page, form handoff and analytics session. If an embedded form runs on another domain, confirm whether attribution is passed into its fields or shared through an approved integration rather than assuming the parent page can read it.

  • Use consistent campaign naming and lowercase values.
  • Document which identifiers are stored and for how long.
  • Do not place names, email addresses or phone numbers in URL parameters.

Connect website activity to the office outcome

A basic lead sheet or CRM pipeline can show whether a form was reached, whether the team responded, and whether the inquiry matched the services. Use a small number of stages that staff will keep current. If ad platform conversions are imported from downstream CRM stages, deduplicate them against browser events and document the imported event’s definition.

A cost-per-lead figure without lead quality can reward campaigns that generate cheap but irrelevant requests. Review the search term or audience, service fit, service area, contactability and next step alongside cost. No attribution setup can fully recover a conversation that was never recorded.

  • Review lead quality with the person answering the phone.
  • Mark disqualified reasons consistently.
  • Compare campaign cost to qualified inquiries and booked work over an appropriate cycle.

Use a measurement checklist before increasing budget

Run a controlled test for each conversion path: one call, one successful form and one invalid form attempt. Confirm which tags fire and which do not. Check that consent denial stops analytics events if the site promises that behavior. Then verify campaign source persistence and reporting delays before using the numbers for a budget decision.

Google Ads and Analytics define conversion and attribution concepts in their own documentation; reports may vary by selected model and configuration. The business should document the specific event names, definitions, tags, consent behavior and owner so future changes do not silently change what ‘a lead’ means.

  • No conversion on a button click alone.
  • One lead event after verified success.
  • No duplicates between thank-you and provider callback.
  • A documented test record and tag version before campaign launch.

Sources and further reading

A RELEVANT NEXT STEP

See how Parallax Growth connects managed Google or Meta advertising to the Foundation inquiry system. Growth is $1,098/month total; advertising media spend is separate.

Book a Walkthrough