Google Ads Conversion Actions: Primary vs Secondary

Dashboard showing a gold primary conversion path and blue supporting conversion signals.

Your campaigns can produce cheap form fills while sales conversations stay sparse. These actions decide which visitor behaviors count as success and which signals automated bidding can pursue.

A form start, brochure download, phone call, and sales-qualified lead don’t carry the same business value. If the setup treats them as equal, it will optimize for activity rather than genuine buying intent.

The right primary and secondary setup gives your bidding strategy a clearer destination.

Key Takeaways

  • Primary conversions appear in the Conversions column and can guide smart bidding when they belong to the campaign’s active goal. Use them for verified lead outcomes that reflect the sales result you want more of.
  • Secondary conversions appear in All conversions and support observation, troubleshooting, and funnel analysis. They can influence bidding only when included in a custom goal.
  • Raw form submissions, CTA clicks, form starts, downloads, and short calls are often better treated as supporting signals until their quality is proven. Promote qualified CRM stages, booked consultations, or meaningful calls when the data is dependable.
  • Configure Google Tag Manager to fire conversion tags only after a confirmed success event, and use Conversion Linker, consent mode, enhanced conversions, and stable lead identifiers carefully.
  • Connect Google Ads with CRM outcomes through offline conversion imports, while using GA4 for journey analysis and validation rather than automatically making it the bidding source.

How Google Ads conversion actions steer lead-gen bidding

A conversion action measures one defined behavior, such as a submitted enquiry form, booked consultation, website call, or imported qualified lead. Each action has a distinct conversion action type and belongs to one or more conversion goals. For website data, a Google tag connects the event with conversion reporting. The conversion category is an action-setting choice, not proof of lead quality.

Website, phone, imported, app, and impression-based events need different quality checks under that conversion action type. App conversions and view-through conversions shouldn’t automatically be treated as qualified leads.

Primary conversions appear in the Conversions column and can guide smart bidding when they belong to the campaign’s active goal. Secondary conversions appear in All conversions and support observation. Google’s primary and secondary conversion action guidance confirms one practical exception: a secondary action can influence bidding when it sits inside custom goals.

A marketer reviews campaign charts on a laptop beside a notebook and coffee.

Account-default goals apply primary actions across campaigns unless you set campaign-specific goals or use custom goals. Therefore, changing a conversion action can affect far more than one campaign. The Google Ads API can expose action status and goal configuration for teams auditing accounts programmatically.

SettingWhere it appearsBest use for lead generation
PrimaryConversions and All conversionsA verified lead outcome that you want smart bidding to increase
SecondaryAll conversionsSupporting signals, early funnel actions, and quality checks
Custom goalDepends on the selected actionsA campaign where custom goals define a distinct optimization target

Treat every primary action as an instruction to the algorithm. A poorly chosen action can increase lead volume while lowering lead quality, especially when campaign-specific optimization relies on custom goals.

Choose primary signals based on sales quality

Start with your sales team’s definition of a worthwhile enquiry. Conversion tracking records an event, but it doesn’t prove a real sales outcome.

Raw lead submissions are useful, but imperfect

A confirmed form submission is often the first measurable lead event, but its conversion action type doesn’t make it valuable by itself. It can include spam, duplicate requests, existing customers, job applicants, or people outside your service area.

Keep form starts, CTA clicks, pricing-page visits, and downloadable resources as secondary conversions. They help diagnose landing-page behavior without pushing the bidding system toward shallow engagement.

At launch, a raw lead submission may need to remain the bidding goal because qualified lead feedback is too slow or sparse. In that situation, check recent CRM records often. Add spam controls and review whether tags fire only after a successful server-confirmed submission.

Promote qualified leads when your CRM data is dependable

A sales-qualified lead should meet criteria your business can defend, such as a relevant service need, workable budget, serviceable location, and valid contact details. A booked consultation may be a stronger bidding goal for some businesses. Others should wait for sales acceptance.

Once the CRM returns that status consistently, use offline conversions to import it. Make that qualified stage the core bidding signal for the relevant campaign, with a conversion action type that matches it. Avoid putting a raw form fill and its later qualified version in the same bidding goal unless you have deliberately set values and understand the duplicate optimization signal.

Where opportunity values differ, import a reasonable dynamic conversion value at the qualified opportunity or closed-sale stage. The Google Ads API can upload or manage these qualified CRM outcomes. Also retain a stable lead ID, or use transaction IDs, to prevent repeated submissions from inflating results. Your cost per qualified lead tracking should reflect these CRM outcomes, not only the cheapest enquiries.

Set up lead conversion actions in Google Tag Manager

A well-chosen goal still fails when Google Tag Manager lets the Google tag fire on a button click instead of a completed lead event. Conversion tracking should follow a confirmed success state, so build the path around that outcome.

Laptop and phone showing connected website, ad, and CRM workflow panels.

Install tags around the confirmed lead event

  1. In Google Ads, go to Goals, open Conversions, select Summary, and create a website conversion action.

Choose the appropriate conversion action type for the completed form event. It should record website conversions only after the form succeeds. 2. In Google Tag Manager, place the Google tag across the site. Install Conversion Linker across the landing-page domain, then set Conversion Linker to fire before the conversion tag.

Keep the Google tag in the same container as the conversion setup. 3. Create a Google Ads conversion tracking tag in Google Tag Manager. Configure the Google tag to fire only when the form submission succeeds.

An event snippet should follow successful server validation or a confirmed data layer event. A unique thank-you page can also work if no other action reaches it. 4. Use Preview mode in Google Tag Manager to test one real submission. Confirm Conversion Linker fires once, then check conversion tracking.

Verify the Google tag, conversion ID, label, trigger, consent mode behavior, and count setting before publishing. For advanced QA, use the Google Ads API to compare IDs, labels, and action status.

Also check Conversion Linker domain coverage. Remove duplicate containers that could fire a second Conversion Linker.

For most lead forms, choose a count of “One” unless repeat submissions after the same ad interaction carry separate commercial value.

Add enhanced conversions for leads with consent

Enhanced conversions for leads connect consented first-party details, such as an email address or phone number, with later CRM outcomes. This user-provided data may be hashed for matching, which can improve attribution when cookies or click identifiers are incomplete.

Accept the Customer Data Terms, choose the lead data source, and configure the data in Google Tag Manager. Set the Google tag to respect consent mode, then test the Google tag before publishing.

Check that Conversion Linker remains compatible with this enhanced lead-matching setup. Consent requirements should be part of the implementation, not an afterthought.

Google’s enhanced conversions for leads checklist covers the required implementation checks.

This setup doesn’t replace careful data handling. Collect only information you have permission to use, document consent, and secure the path between the form, CRM, and upload process.

If match rates or diagnostics look wrong, inspect the Google tag and Conversion Linker first. Review the Conversion Linker settings in Google Tag Manager, and check consent mode in diagnostics before changing bid targets. Use this enhanced conversions diagnostic guide when the setup still reports errors.

Connect Google Ads to the CRM outcome

Lead generation attribution doesn’t end when someone submits a form. The downstream CRM record shows whether the lead became a real opportunity.

Form capture handles data collection, the CRM preserves the outcome, and Google Ads uses the selected signal for bidding. Keep those jobs separate when reviewing performance.

Preserve identifiers at the moment of capture

Good conversion tracking starts at form capture. Store the original click identifier, landing page, timestamp, campaign data, consent status, and lead ID with the CRM contact. For Google Ads, retain GCLID when available, plus WBRAID or GBRAID where applicable.

Record whether consent mode affected the tag and later attribution. Keep the Google tag tied to the same lead record, so identifier persistence survives CRM processing. Conversion Linker can help retain click identifiers across the landing page and form flow.

Use hidden fields in lead forms and verify that your CRM integration doesn’t overwrite them during deduplication. Include transaction IDs when your setup supports them. Check the container in Google Tag Manager, then test a fresh submission in Google Tag Manager before launch.

This guide to capturing GCLID and WBRAID can help teams keep the identifiers needed for lead attribution.

Google Ads can match offline conversions from CRM stages back to ad interactions through its offline conversion import process. Use offline conversions when the CRM stage, rather than the form submission, is the outcome you want to measure.

For enhanced conversions, upload outcomes within 63 days of the associated last ad click. Treat that limit as the conversion window for the import. Teams can also use the Google Ads API to validate upload status programmatically.

If duplicate records appear, inspect Conversion Linker and the Google tag before changing CRM rules.

Give native Google Ads and GA4 different jobs

Native Google Ads conversions give you direct control over bidding goals and conversion goals. They’re usually the clearest choice for the immediate submitted-form or website-call event.

Google Analytics is better suited to broader journey analysis. It can show how content, organic visits, and assisted paths contribute before the enquiry. Review those paths in the GA4 property, and interpret assisted paths and view-through conversions through the chosen attribution model.

Use Google Analytics for journey context, not direct bidding control. If you import an event from the GA4 property into Google Ads, it becomes a Google Ads conversion action. Configure its conversion action type intentionally, and document the GA4 property as the data source.

Set campaign goals around that one source. Campaigns using custom goals can intentionally use a different action set, but document why.

Don’t count the same successful form through a native Google tag and an imported Google Analytics event as separate bidding signals. Choose one source for bidding and use the other for validation.

Use conversion tracking reports to check source deduplication between the native tag and imported event. Compare the GA4 property with Google Analytics reports to validate duplicates between sources. Validate the Google tag against the GA4 property event before changing bids.

Audit calls and reports before changing bids

Phone leads need their own conversion tracking design because not every call reflects buying intent. Modeled or incomplete call data may reflect consent mode settings, so audit it before adjusting bids.

Separate website calls from calls placed from ads

Treat phone call conversions from ads separately from calls generated by your website. Website call tracking uses Google Tag Manager to deploy a Google tag for number replacement. Configure the Google tag to fire after a minimum call duration, then test the Google tag during QA.

Set the duration from your own call data. Review recordings or CRM dispositions to confirm that the conversion action type reflects meaningful calls, not short, low-value ones.

Google’s website call tracking instructions explain the technical requirements. Keep short calls as non-bidding signals until the duration threshold reliably reflects a meaningful conversation. If your CRM records sales calls, importing qualified calls as offline conversions later gives you greater control.

Compare Conversions with All conversions

In campaign reporting, segment performance by conversion action to see which events drive the total. Identify the data source first: native Google Ads, imported analytics, or CRM data. Teams needing action-level segmentation can use the Google Ads API.

Compare the Conversions column with All conversions before raising budgets or changing target CPA. Check whether custom goals or campaign-specific settings alter the reported total.

View-through conversions represent users who saw an ad and converted later without clicking. Segment view-through conversions by network or campaign. Don’t treat view-through conversions as direct qualified leads by default. Compare view-through conversions separately before changing target CPA.

Separate app conversions from website calls when reviewing lead-gen totals. Keep app conversions in a separate scope so app events don’t inflate lead-gen reporting.

A rising conversion count is a warning sign when the CRM’s qualified lead rate falls.

SEO, performance marketing, social media marketing, and website development teams should use the same lead definitions, even when their attribution models differ. Google Analytics may show assisted interactions in broader digital marketing reports. AEO and GEO content may influence an enquiry, but the CRM remains the bidding source of truth for qualified pipeline.

Frequently Asked Questions

What is the difference between primary and secondary conversion actions?

Primary conversions appear in the Conversions column and can guide smart bidding when they belong to the campaign’s active goal. Secondary conversions appear in All conversions and are generally used for observation, analysis, and quality checks.

Should form submissions be primary conversions?

A completed form can be a primary conversion when it is the best available indicator of lead intent. However, spam, duplicates, existing customers, and poor-fit enquiries can reduce its value, so qualified CRM stages may be a stronger bidding signal once reliable data is available.

How should qualified leads be imported into Google Ads?

Import the qualified CRM stage as an offline conversion and use it as the core bidding signal for the relevant campaign. Preserve a stable lead ID or transaction ID, and upload dynamic values when opportunity quality differs.

When should a Google Ads conversion tag fire in Google Tag Manager?

The tag should fire only after the form or other lead event reaches a confirmed success state, such as server validation, a confirmed data layer event, or a unique thank-you page. Test the Google tag, Conversion Linker, trigger, consent behavior, and conversion settings before publishing.

Should GA4 and native Google Ads conversions both guide bidding?

Choose one source for bidding so the same successful action is not counted as two optimization signals. GA4 is useful for broader journey analysis and validation, while native Google Ads conversions often provide clearer control over bidding goals.

Build bidding around the lead you want more of

Google Ads conversion actions guide smart bidding. Primary conversions should resemble the sales outcome your team wants to create more often, not merely the easiest website interaction to record.

Use secondary actions to inspect intent, troubleshoot tracking, and compare funnel quality. Google Analytics can validate the journey, but it shouldn’t automatically become the bidding source. If the account includes app conversions, review custom goals for each campaign before judging performance.

Before trusting a low cost per lead, audit Google Tag Manager and confirm your Google tag fires correctly. Then connect Google Ads data to disciplined CRM qualification.

If your conversion columns and CRM outcomes tell different stories, Get In Touch With Us for a practical review of tracking, lead quality, and campaign goals.

Recommended Posts