How to Import Qualified Branch Leads Into Google Ads Without Rewarding Low-Quality Enquiries

A form submission is not the same as a valuable lead

For a chain with many locations, an ad can generate dozens of enquiries that cannot be served: wrong city, unsupported service, duplicate form, unreachable contact or a request outside the branch's coverage. If the campaign optimises only for the initial submission, it can learn to seek more of the wrong behaviour.

Google Ads supports importing offline outcomes and recommends considering enhanced conversions for leads for many new implementations. The official offline conversion import FAQ describes qualified or converted lead goals and separate conversion actions for different funnel stages. Follow the current setup guidance for your account rather than copying a legacy upload recipe.

Define the branch lead lifecycle first

Use a small, mutually understandable status model:

• Received: a unique enquiry has been captured.
• Contactable: contact details pass basic validation and a response attempt is recorded.
• Qualified: the request matches service, geography and business criteria.
• Booked or quoted: the branch has accepted a next step.
• Won: the sale or service is completed.
• Disqualified: the reason is captured, such as duplicate, spam, outside territory or unavailable service.

Do not upload every stage as the same conversion action. Separate actions preserve diagnostic value. Decide with the paid media team which stage, if any, should inform bidding; do not let an unreviewed CRM status become a bidding signal by default.

Map CRM records to ad interactions

Capture the necessary click or user-provided matching information using a documented, privacy-reviewed implementation. Store the assigned branch ID separately from the campaign name: campaigns can change, while the branch that actually handles the enquiry is an operational fact. Preserve event time, conversion name, deduplication key and value where relevant.

Before the first import, test a small batch with known outcomes. Confirm that timestamps follow the required format and time zone, the conversion action exists in the target account, and a lead is not uploaded twice under different status labels. Google documents common upload errors and deduplication behaviour in its current FAQ.

Example of a misleading report

A clinic chain sees 300 enquiries, but 90 are outside its service area and 70 cannot be contacted. Reporting 300 “conversions” makes one branch appear successful even if it produces few booked appointments. The operational fix is not to delete the top-of-funnel event; it is to report each stage and agree on the stage that represents genuine business value.

Weekly quality review

Compare leads received, qualified rate, booked rate, completed rate, disqualification reasons and import errors by branch cohort. Investigate differences in service availability and response processes before assuming that media performance alone explains them.

Privacy and limitations

Limit access to customer data, follow applicable privacy and consent requirements, and send only the fields supported by the chosen Google setup. Importing offline conversions improves measurement signals; it does not prove that every sale was caused by an ad.