Primary vs. Secondary Conversion Actions for Contractor Ads

Define each event by what actually happened

List what the event means in business terms: page view, tap to call, connected call, form start, confirmed form submission, qualified request or booked estimate. Describe the source that confirms it. If the event fires on a CSS click or generic page load, do not label it as a completed lead.

For an embedded GoHighLevel form, verify the provider’s success state, thank-you transition or approved event integration. Test validation failure and successful submission through a controlled flow. Keep the CRM record and event definitions aligned so one submission does not count twice.

Understand primary and secondary settings

Google Ads distinguishes actions used for bidding and reporting from actions kept for observation, subject to campaign goals and configuration. Google’s current conversion-goal guidance explains primary and secondary action settings. Always check how the actual campaign uses account-default or custom goals before changing a status.

A secondary event may still appear in an ‘all conversions’ view or be used under a custom goal, depending on account setup. Read the current interface, not just the label. A status change can influence bidding if the campaign optimizes toward that goal, so document the intended effect and get the account owner’s approval.

Choose a primary signal that is both real and usable

For many local contractors, a validated web inquiry or qualifying call can be a reasonable early primary event if appointment volume is limited. If reliable booked-estimate data is available and properly imported, the business may later decide that stage is more useful. The decision depends on volume, data quality, lag and the campaign’s purpose.

Do not make a weak event primary just because it fires often. More button clicks can train a campaign toward people who tap without submitting. Likewise, an event that fires too rarely or inconsistently may not provide a useful signal. Check the entire path and explain the tradeoff to the owner.

Keep diagnostics without counting them as leads

Keep useful micro-events—CTA taps, form starts, FAQ opens—as secondary observations or analytics events where appropriate. They can reveal mobile friction or user interest while keeping the paid conversion count tied to completed intent. Use different report columns and labels so the team does not add micro-events to actual inquiries.

A click-to-call event is a tap, not necessarily a call connection. A calendar view is not a confirmed appointment. A thank-you route can be reloaded. Choose deduplication and count rules that match the source action, and compare reports with CRM records when possible.

Review goals by campaign

Campaigns may use account-default goals or campaign-specific goals. A roofing awareness campaign and a plumbing emergency campaign may need different observation or bidding choices. Confirm which goal each campaign uses before editing an account-wide conversion action that could affect several services.

Keep a conversion inventory with event name, source, trigger, primary/secondary status, campaign use, duplicate behavior, consent and last test date. Assign an owner to approve a change. This makes it easier to understand later why the system began optimizing toward a different action.

Test before changing optimization

Use Tag Assistant or the platform’s supported diagnostics to check that the event fires only on the intended state. Then compare the event with the form provider and CRM. If a tag is unreliable, repair it before making it the primary event. If the test requires a real production lead, do not proceed without a documented internal testing path.

After an approved change, monitor the same metrics and conversion windows. Do not expect a campaign’s historical reports to be retroactively identical after changing goal definitions. Record the date, previous status, new status, campaign scope and reason.

Example conversion map

• Page view: analytics context only.
• Phone link tap: secondary diagnostic, unless the business explicitly chooses another validated call signal.
• Form start: secondary friction diagnostic.
• Confirmed form success: primary lead event if deduplicated and verified.
• Qualified request or appointment: separate CRM stage; import only if configured and approved.
• Booked job or revenue: operational result; do not infer from the form event.

Do not change a goal to improve a report

A higher conversion total is not evidence that more people contacted the business. If the report is low, investigate whether the form, tag, consent, attribution or CRM is working. Keep the definition stable enough to compare periods and disclose any break in measurement.

Google Ads optimization can use the conversion actions selected for a campaign, so the choice affects both reporting and automation. Make it with the business owner after the event has been tested, not to make a chart look better.