Which Google Ads Conversion Action Should Count as Primary on Shopify?

TL;DR

For a Shopify store running server-side conversion uploads, the choice takes one line: one Purchase action carries bidding, everything else observes. The work is in confirming that Google agrees with you. Primary and secondary designations live on the goal, not on the action in isolation, and any action inside a custom goal is "used for reporting and bidding regardless" of that designation [2]. Add the counting setting, which defaults to Every conversion for imported conversions [4], and there are two dials most Shopify accounts have never deliberately set.

Key Takeaways

• Primary actions "are reported in the 'Conversions' column in your reports and used for bidding as long as the standard goal they are part of is used for bidding"; secondary actions "are for observation only" and report in All conversions [1].
• Change it under the Conversions summary: find the goal, select Edit goal, choose Primary or Secondary (observe only), save [1].
• Actions inside a custom goal are "used for reporting and bidding regardless of whether they're set as 'primary' or 'secondary' actions" [1]. That is the trap that makes "set it to secondary" fail silently.
• Google groups new conversion actions into goals automatically by category, for example Purchases or Contacts [3], and new campaigns select all account-default goals for optimization by default [3].
• Counting: Every conversion counts every conversion after an ad interaction, One conversion counts one per ad click [4]. Imported conversions default to Every conversion [4].
• Counting changes apply only to future conversion reporting [4], so a before-and-after comparison across the change is broken by construction.
• Google's repeat rate metric is "effectively the number of conversions you would have recorded using the 'every conversion' setting divided by the number you would record using the 'one conversion' setting" [4].

Which action should be primary on a Shopify store?

The one that carries your order value from the server, which on a WeltPixel Conversion Tracking store is the one offline-import action the app uploads to, a Purchase-category action when the app created it.

That is the whole answer, and it is short for a structural reason: the app only ever writes to one conversion action. There is no add-to-cart upload, no begin-checkout upload, no second purchase path. So there is nothing to choose between. Set that action primary, leave everything else observing unless you deliberately made it primary, and spend your time on verification instead.

The rest of this article is the verification, because three separate mechanisms can quietly overrule the setting you just made.

What primary and secondary actually change

Two columns and one bidding decision. Google's wording is precise enough to quote.

Primary actions "are reported in the 'Conversions' column in your reports and used for bidding as long as the standard goal they are part of is used for bidding". Secondary actions "are for observation only. They are used for reporting in the 'All conversions' column in your reports, but not for bidding, even if the goal they are included in is used for bidding" [1].

The path to change it: open the Conversions summary, find the goal containing the action, select Edit goal, then choose Primary or Secondary (observe only) and save [1]. Google adds its own warning on the same page, that "misconfiguring these settings can prevent Smart Bidding from optimizing effectively" [1].

Note how narrow the documented default is. The page states one, and only for conversions imported from Analytics: those "are secondary by default when created from Google Analytics and can only be updated to primary in Google Ads" [1]. For an action created in Google Ads, or by an app, it states no default at all. Google documents that actions are grouped into goals automatically by conversion category, "for example, 'Purchases', 'Contacts', or 'Submit lead forms'" [3], and stops there. So read the designation off your own Conversions summary rather than assuming a default, especially for an action created by an app or by a linked channel.

The custom goal that ignores your setting

This is the one that wastes a week.

Google's documentation states that "conversion actions included in a custom goal are used for reporting and bidding regardless of whether they're set as 'primary' or 'secondary' actions" [1][2]. Read it twice if you have ever set an action to secondary and watched it keep influencing spend. The designation is a property of standard goals. Put the same action in a custom goal that a campaign optimizes toward and the observe-only intent evaporates, with no warning and no visible change on the action itself.

Google's own position on custom goals is that they "are for advanced use and aren't recommended in most cases" [3]. For a Shopify store with one purchase action, they buy nothing and hide a lot.

Account-default goals deserve one sentence of the same skepticism. Google describes them as the goals "you'd like all campaigns in your account to bid and optimize toward automatically", and when you create a new campaign "all account-default goals in your account are selected for optimization by default" [3]. So an action promoted to an account-default goal reaches campaigns you never touched.

Count every conversion or one?

Every conversion, for a store selling physical goods, and Google agrees by default.

Google defines the two settings plainly: Every conversion means "Google Ads counts every conversion (per tracked conversion action) that happens after an ad interaction", and One conversion means "Google Ads counts only one conversion per ad click" [4]. Their recommendation is Every for sales, because "every sale likely adds value for your business", and One for leads, where "usually only one, unique lead per ad click likely adds value" [4].

The defaults matter more than the recommendation, because most accounts never change them. Website actions, in-app actions, Analytics transactions, mobile website clicks and imported conversions all default to Every conversion [4]. Server-side uploads are imported conversions, so a Shopify store's purchase action is already on the setting it should be on.

If you are considering a switch anyway, Google hands you the estimator. The repeat rate column shows "the average number of conversions made by customers who convert at least one time", which Google describes as "effectively the number of conversions you would have recorded using the 'every conversion' setting divided by the number you would record using the 'one conversion' setting" [4]. Run the arithmetic on an illustrative store: 2,600 reported purchase conversions from 2,000 converting customers gives a repeat rate of 1.30, so switching to One conversion would report roughly 2,000, a drop of 600 conversions, or about 23%. Your target CPA and ROAS numbers would need resetting on the same day, because they were calibrated against the higher count.

Then the constraint that breaks the analysis: "Any changes to conversion count settings will only apply to future conversion reporting" [4]. Your before-and-after chart will show a step, and none of the history will be restated to match. Decide from the repeat rate before the change, not from the chart after it.

How do you tell which action Smart Bidding is reading?

Open the Conversions summary and read three columns, because two sources can each create a purchase action on the same account.

Shopify's Google & YouTube channel installs browser tags and creates its own conversion actions, and a server-side app uploads to an offline-import action. Both are legitimate. Both can end up counted. The full coexistence procedure lives in running a tracking app alongside Shopify's Google & YouTube channel, and the one-line rule is one purchase source per destination.

Here is the read, in order:

1. Go to Goals → Conversions → Summary and list every action with the Purchases category.
2. Check the type column. An offline-import action shows as an import type; a channel-created action is tag-based. Type alone tells you which is which.
3. Check the status column for Primary or Secondary (observe only) on each [1].
4. Check which goal each action sits in, and whether that goal is a standard goal or a custom one. A custom goal ends the analysis, because the designation stops mattering there [2].
5. Open a campaign's optimization settings and confirm which goals it uses, including account-default goals it inherited on creation [3].
6. Read each purchase action's own row rather than the column totals. All conversions includes secondary actions by design [1], so the gap between the two columns tells you nothing on its own; the action's Primary or Secondary (observe only) designation does.

If the numbers still disagree with Shopify's order count after that, the cause is usually earlier in the chain than the goal configuration. Why Google Ads reports fewer conversions than Shopify and Google Ads conversions without a GCLID on Shopify cover the identifier and window side. And if you have just created the action, the 4 to 6 hour rule explains the zero you are staring at.

What the app decides, and what it leaves to you

The division is clean, and it is worth knowing before you go looking for a setting that does not exist in the app.

The merchant picks which conversion action the app uploads to, and the picker only offers actions that are enabled and of the offline-import type, so a browser-tag action cannot be selected by mistake. If you let the app create the action, it arrives as an offline-import action in the Purchase category, enabled, with a 90-day click-through lookback window and no default value substituted for the real order value. Each upload carries the conversion action, the conversion time, the value, the currency and the Shopify order ID, plus the click identifiers when the order has them, hashed customer identifiers when Enhanced Conversions is on. When an order carries both a gclid and a gbraid from the same ad click, both are sent, which is what Google's own guidance recommends.

What the app never touches: primary or secondary designation, the counting setting, goals of any kind. Those live in Google Ads and stay yours. The app also reads each action's own click-through lookback window and drops click IDs older than it before upload, which is the one place where the action's configuration changes what gets sent.

Two neighbours in the same settings screen are worth reading separately. Account-level Enhanced Conversions settings are covered in server-side Enhanced Conversions on Shopify, the leads variant of that toggle in Enhanced Conversions for Leads on Shopify, and the customer-acquisition goal, which only works against Purchase-category actions, in new versus returning customer tracking on Shopify. If duplicate purchase rows are your actual problem rather than the designation, event deduplication and event_id is the right starting point.

If you want one Purchase action fed from the order record with the Shopify order ID attached to every upload, WeltPixel Conversion Tracking [5] does exactly that and leaves the primary, secondary and counting decisions in your Google Ads account, where Google's own warning about misconfiguration applies [1].

FAQ

Should a Shopify store have more than one primary conversion action?

Usually no. One Purchase action carrying order value from the server is enough for bidding, and additional actions such as add-to-cart or begin-checkout belong in All conversions as secondary observation [1].

I set an action to secondary and it still affects bidding. Why?

Almost certainly a custom goal. Actions in a custom goal are used for reporting and bidding regardless of their primary or secondary designation [2]. Check which goal the action belongs to.

Is a new conversion action primary or secondary by default?

Google states a default only for conversions imported from Google Analytics, which are secondary by default and can only be updated to primary in Google Ads [1]. For an action created in Google Ads or by an app it documents no default, only that actions are grouped into goals automatically by category [3], so read the designation from your Conversions summary rather than assuming.

Will switching from Every conversion to One conversion fix double counting?

No. It changes how repeat purchases after one click are counted, and the change applies only to future conversion reporting [4]. Duplicate rows from two different conversion actions are a separate problem.

Does the tracking app set any of this inside Google Ads?

No. The app picks and writes to one offline-import conversion action and never sets primary, secondary, counting or goal configuration.

Sources

1. Google Ads Help, "About primary and secondary conversion actions" (primary reported in the Conversions column and used for bidding when its standard goal is used for bidding; secondary "for observation only" reported in All conversions; Edit goal path; custom goal actions used for reporting and bidding regardless of designation; conversions created from Google Analytics secondary by default; misconfiguration warning), support.google.com/google-ads/answer/11461796, accessed September 10, 2026
2. Google Ads Help, "About campaign-specific conversion goals" (conversion actions included in a custom goal used for reporting and bidding regardless of whether they are set as primary or secondary goals), support.google.com/google-ads/answer/9143218, accessed September 10, 2026
3. Google Ads Help, "About conversion goals" (actions grouped into goals automatically by conversion category, for example Purchases, Contacts, Submit lead forms; account-default goals selected for optimization by default on new campaigns; custom goals are for advanced use and not recommended in most cases), support.google.com/google-ads/answer/10995103, accessed September 10, 2026
4. Google Ads Help, "About conversion counting options" (Every conversion counts every conversion after an ad interaction; One conversion counts one per ad click; Every recommended for sales and One for leads; defaults to Every conversion for website actions, in-app actions, Analytics transactions, mobile website clicks and imported conversions; changes to conversion count settings apply only to future conversion reporting; repeat rate as the every-conversion count divided by the one-conversion count), support.google.com/google-ads/answer/3438531, accessed September 10, 2026
5. WeltPixel Conversion Tracking, Shopify App Store listing, apps.shopify.com/weltpixel-conversion-tracking, accessed September 10, 2026