Google Ads Conversion Goals: Set Primary, Secondary and Account-Level Goals Correctly
Google Ads can only optimise in the direction a business authorises through its goal architecture. This is precisely where costly misunderstandings arise in small and medium-sized businesses: a click on a phone number is treated as equivalent to a qualified order, an event imported from GA4 runs in parallel with the Google Ads tag, or one campaign has been using different goals from the rest of the account for months. The interface continues to show conversions. Whether those conversions carry the same commercial meaning remains unresolved.
This guide provides a conversion goal register to resolve that problem. It connects every conversion action to a business outcome, data source, optimisation role, scope, quality evidence and documented approval. The internal register statuses STOP, OBSERVE, CAMPAIGN TEST and ACCOUNT STANDARD are deliberately not Google Ads settings. They represent the business review process: an action may technically be configured as Primary in Google Ads and still receive STOP in the register if it is counted twice or does not represent a defensible commercial value.
A conversion goal is not a single switch
Read the action role, goal and scope together
Google's official overview of conversion goals describes a multi-level architecture. At the lowest level is the conversion action: for example, a purchase recorded by the Google tag, an imported GA4 event or a qualified lead from the CRM. Actions are grouped by category into standard goals such as Purchase, Contact or Submit lead form. For most conversion actions, the action-level setting determines whether they are Primary or Secondary; that choice is restricted for certain action types. At goal and campaign level, the account determines which standard goals are included and whether a campaign adopts the account-wide default or uses its own selection.
These levels answer different questions. The category describes the type of activity being measured. Primary or Secondary generally describes the action's optimisation role. The account standard defines the goal scope intended for new campaigns and campaigns that use account-default goals. A campaign-specific selection replaces that scope locally. A custom goal, meanwhile, is a manually assembled exception. Anyone who reads these levels as one undifferentiated list of “conversions” can select a correct individual option and still build the wrong overall architecture.
| Level | Object | Guiding question | Typical setting | Effect | Evidence in the register |
|---|---|---|---|---|---|
| Business | Real outcome | Which action creates commercial value? | Order, qualified lead or purchase | Defines the business benchmark | Evidence from CRM, shop or finance system |
| Data | Conversion action | Which source records and sends the event? | Google tag, GA4 or offline import | Creates the measurable data point | Test case and unique ID |
| Meaning | Goal category | Which category is assigned to the action? | Purchase, Qualified lead or Contact | Organises actions for goals and reports | A category that matches the business meaning |
| Optimisation | Action role | Should the action normally guide bids? | Primary or Secondary | Affects reporting columns and bidding eligibility | Approval plus exception check |
| Account | Standard goal | Which goals apply by default? | Use as an account goal | Used by campaigns that adopt account-default goals | List of affected campaigns |
| Campaign | Goal selection | Does the campaign adopt the standard? | Account-default or campaign-specific | Determines the goal scope actually used | Campaign view and change log |
The table must be reviewed in both directions. A technically clean data point with no business meaning is not a good goal. A valuable order without reliable transmission is not yet a usable signal. Nor does a Primary action automatically guide every campaign: it must belong to a goal that the campaign in question uses. Outside that selection, it is not an explicit optimisation goal and does not appear there in “Conversions”; Google nevertheless notes that such Primary data may support predictions. Approval is justified only when all six levels work together.
The business outcome comes before the interface
A submitted form is not yet a qualified order
Before changing any settings, the business defines the outcome in its own language. For a trades business, that might be a confirmed on-site appointment within the service area. For a B2B provider, a lead may become qualified only after its role, need and budget have been checked. In an online shop, a purchase is not automatically profitable if returns, discounts or different margins are ignored. The conversion action is a measurable proxy for that outcome, not proof that it occurred as defined.
Even a suitable category does not replace a business definition. Google's overview of updated conversion categories distinguishes, among others, Purchase, Add to cart, Begin checkout, Qualified lead, Converted lead, Submit lead form, Book appointment, Request quote, Contact, Page view and Other. The category improves grouping and readability, but it neither assigns a higher value to an action by itself nor turns a form submission into a qualified lead.
The register therefore records a short business definition for every action: the triggering event, eligible cases, excluded cases and the system that confirms it. “Qualified lead” could mean, for example, a contactable person, a suitable location, a genuine need and a service the company accepts. Sales, marketing and the agency must understand that definition in the same way. If it is missing, the action receives STOP. If it exists but the backend reconciliation is not yet reliable, its status is OBSERVE. A bidding role can be considered only when technical and business samples point to the same outcome.
Primary and Secondary describe an action's optimisation role
Keep bidding signals and observation metrics separate
According to the official explanation of Primary and Secondary conversion actions, a regular Primary action appears in the “Conversions” column and can be used for bidding when the campaign actually uses the associated goal. A Secondary action is generally intended for observation, appears in “All conversions” and is not used as a bidding signal in normal standard goals. That statement contains two important conditions: Primary alone is not sufficient, and Secondary does not mean “unimportant” or “not measured”.
An example illustrates the distinction. A retailer measures purchase, begin checkout and product view. Purchase can be Primary because it is closest to the business outcome. Checkout and view can remain Secondary so that changes in the customer journey stay visible without feeding Smart Bidding three different funnel stages as though they were equivalent outcomes. For a service provider, a submitted form can initially remain Secondary while a subsequently confirmed qualified lead becomes Primary. If no reliable offline feedback exists yet, the form may be used temporarily as a test signal; that transitional solution still needs a date, an owner and a condition for replacing it.
The terms should therefore not be treated as badges of rank. Secondary can be an important diagnostic metric. Primary can be a poor signal if it is easy to manipulate, duplicated or too broad in business terms. The custom-goal exception in section 7 also applies: an action marked Secondary may still be used for bidding when it belongs to an applied custom goal. Every approval must therefore check not just the action status, but also the goal type and the campaign's specific goal selection.
The conversion goal register makes decisions auditable
Six fields connect business value, data quality and scope
The register is not a copy of the Conversions summary. It supplements the technical configuration with information Google Ads cannot know: commercial meaning, data maturity, business ownership and the reason for approval. In Goals → Conversions → Summary, the current instructions for managing conversion goals explain how to manage settings including Account Default and Action Optimization as Primary or Secondary, and how to create custom goals. A status change can affect every campaign that uses the associated goal. That is precisely why each settings change needs a register entry before it is made.
| Conversion action | Business outcome | Source and quality evidence | Google role and scope | Register status | Next approval condition |
|---|---|---|---|---|---|
| Purchase — Google tag | Paid order | Test purchase, transaction ID and shop reconciliation | Purchase · Primary · standard goal · no custom goal · intended for Account Default | ACCOUNT STANDARD | Monthly review of value, cancellations and duplicates |
| Purchase — GA4 | The same paid order | Parallel measurement identifies the same order population | Purchase · Secondary · standard goal · no custom goal · no direct use for bidding | OBSERVE | Explain discrepancies; do not also set it to Primary |
| Form submitted | Unverified enquiry | Tag test passed; CRM quality varies | Submit lead form · Secondary · standard goal · no custom goal · observation | OBSERVE | Establish reliable qualification rate and spam filtering |
| Qualified lead | Opportunity verified by sales | CRM status, upload ID and sample review | Qualified lead · Primary · standard goal · no custom goal · pilot campaign only | CAMPAIGN TEST | Confirm volume, delay and value over the test window |
| Phone number clicked | Intent without a confirmed call | Browser event with no evidence of an actual call | Contact · Secondary · standard goal · no custom goal · not selected as a goal | STOP | Link it to an actual call and minimum duration first |
| Old thank-you page | No unique outcome | Repeated loading and duplicate counting are possible | Submit lead form · Primary · member of a legacy custom goal · multiple campaigns | STOP | Record custom-goal membership and affected campaigns, then replace it |
The status path is STOP → OBSERVE → CAMPAIGN TEST → ACCOUNT STANDARD, but not every action has to reach the final status. A useful micro signal can remain under OBSERVE permanently. A valuable but infrequent offline action may initially be approved only for a CAMPAIGN TEST. In this internal register, ACCOUNT STANDARD means that the action is approved as a Primary action in a standard goal that may serve as Account Default. The actual account-default setting remains attached to the goal; it does not automatically force the action into every existing campaign.
The register also includes a change record: date, previous state, new state, affected campaigns, approvers, expected effect and rollback rule. A screenshot documents the interface, but not the decision. The register entry explains why the business allows an action to guide optimisation and what evidence would reverse that decision.
Account-wide conversion goals provide the campaign standard
Account-wide means inherited, not universal
Account-default conversion goals provide the intended standard for campaigns that adopt this account setting. The official description of account-wide conversion goals separates two levels: Use as an account goal is set on the goal, while Primary or Secondary is set on the individual action. Changing the account standard affects campaigns that use account-default goals; a campaign with its own goals does not necessarily inherit the change.
The account standard is therefore a governance decision. It should contain the small number of business outcomes that genuinely apply to most of the account. If Purchase, Add to cart, Begin checkout and Page view all enter the account-wide optimisation scope at the same time, the system may pursue several stages of the same journey even though only the purchase has direct commercial meaning. The same applies to leads: a contact click, form, appointment and qualified opportunity must not be treated as interchangeable without a value and quality rationale.
Before a change, the team identifies every campaign that adopts the account standard and every exception. New campaigns may adopt the standard automatically; existing campaign-specific configurations remain separate cases. According to the documentation, account-default goals do not apply to App campaigns: the required conversion actions are always selected at campaign level in that case. The register therefore records more than “account-wide: yes”. It also states which campaign groups inherit the standard, which ones are exempt and who reviews those exceptions regularly.
Campaign-specific goals need a justified exception
An exception is architecture, not a quick repair switch
Campaign-specific goals allow a campaign to replace the account-wide set with selected standard goals and, where required, a custom goal. In its documentation on campaign-specific conversion goals, Google generally recommends a shared account-default set so that similar campaigns can learn within a consistent goal framework. An exception can still be correct when the campaign genuinely pursues a different business outcome, rather than merely because its current results are disappointing.
A plausible case would be a B2B campaign that should optimise for qualified opportunities while a separate self-service area is oriented towards direct purchases. A less plausible response would be to add an easier micro goal briefly when conversion rate falls so that more “conversions” appear again. This changes the objective function in the middle of the assessment; the more attractive number then answers a different question. Different commercial values are not automatically a reason to separate goals either. Where the same outcome type has different values, a sound value-based bidding approach may be more appropriate.
The custom goal is the critical exception to the simple Secondary rule
A Secondary action can still guide bids inside a custom goal
A custom goal can manually combine specific conversion actions from different standard goals. Under the current goal architecture, a campaign can use no more than one such custom goal. It is not a neutral reporting folder: when a custom goal is applied to a campaign, every bidding-eligible action it contains is used for reporting and bidding. This explicitly includes actions whose Action Optimization setting is Secondary. Store Sales Direct conversion actions are an exception and cannot be used for bidding even inside a custom goal.
That exception is operationally dangerous because a superficial check may look reassuring. The action detail says “Secondary (observe only)”, yet the same action belongs to a custom goal in use and still influences the campaign. The register therefore needs a dedicated “Member of custom goal” field and a corresponding check at campaign level. An exported list of Primary actions alone is not enough.
Custom goals are justified only when a narrowly defined campaign needs a combination that suitable standard goals cannot represent cleanly. They should not be used to bypass unclear categories, bundle several micro signals or compensate artificially for limited data with easy-to-complete actions. Every included action is assessed individually before approval. If the combination contains an action with STOP, the custom goal also receives STOP. If it permanently combines different types of outcome, the assigned values and bidding objective must be able to express their commercial differences.
Micro and macro conversions have different jobs
More signals do not automatically mean better signals
Macro conversions are close to the business outcome: a purchase, booked job, qualified opportunity or paid subscription. Micro conversions describe intermediate activities such as a product view, scroll depth, PDF download, add to cart or click on a contact option. Both can be useful diagnostically. The problem begins when measurability is mistaken for suitability for optimisation.
Smart Bidding does not infer the value the team privately assigns to an action; it learns from the goals and values supplied to it. If a frequent page interaction is made Primary, it can numerically dominate the less frequent but more important result. The system may then find more of the easier action efficiently while orders remain unchanged. The SME gains activity, but not necessarily revenue or qualified demand. Micro actions therefore normally remain Secondary and support funnel diagnosis. Any time-limited use as Primary requires a clear rationale, a meaningful value difference and a defined replacement condition.
Multiple data sources must not multiply the same business transaction
Reconcile the Google tag, GA4 import and offline feedback at action level
A typical account records the same purchase through the Google Ads tag and a GA4 import, perhaps with an offline upload added as well. Multiple Primary actions for the same order can tell Smart Bidding that several successes occurred. A transaction ID can help within a suitable action; it does not guarantee deduplication across separate actions or sources.
A conversion action created through the Google Analytics interface is set to Secondary by default. To use it for regular bidding through a standard goal, change its action optimisation setting to Primary in Google Ads; if it belongs to an applied custom goal, however, it is used for bidding even while marked Secondary. History from before the import is not backfilled. Differences between Ads and Analytics are not automatically errors because the reporting date, counting method, attribution and windows can differ, among other factors.
Ownership of conversions must also be unambiguous. With cross-account conversion tracking, a client account uses either its own conversion actions or those provided by the manager account, not both sets at once. Only the responsible manager account can edit the cross-account actions. When switching from account-specific to manager-account cross-account conversion tracking, campaigns targeting a specific conversion action switch to the manager account’s default conversion goals; the same caveat applies when moving back to serving-account tracking. Earlier statistics are not lost as a result, but goal selection and history should be documented before and after every switch.
The register names one leading data source for each real outcome and assigns any additional source a role as control, backup or quality signal. Test cases show which actions fire with which value, currency and ID. Unresolved double counting leads to STOP, not to an average derived from contradictory systems. The technical installation remains a separate area of work.
Value, counting method and conversion window determine the signal's meaning
The right action with the wrong economics remains the wrong goal
A business-appropriate action can become unusable through incorrect values. A shop with widely varying basket sizes should not send the same fixed value for every purchase. A lead value must not be presented as exact revenue when it is only an expectation; as a modelled value, it must be derived transparently from close rate, revenue or contribution margin.
The counting method also follows the business case. For purchases, every unique order matters. With lead forms, however, repeated submissions by the same person in a short period do not necessarily represent several new opportunities. Conversion windows must fit the real decision cycle: a window that is too short understates long sales cycles, while a very long window may include later contacts that require more cautious interpretation. View-through conversions and engaged-view conversions should be read separately when they occur in the relevant setup.
The register stores the value source, update cadence, currency, counting method, window and data delay. For leads, it also records the feedback rate: what proportion of records later receives a CRM status? A good reported CPA is not robust if many records are never returned as either qualified or rejected. Appropriate parameters are required before CAMPAIGN TEST or ACCOUNT STANDARD can be justified; implementation remains outside this article's scope.
Reporting must show configuration and outcome separately
Distinguish Conversions, conversion value and All conversions
The “Conversions” column reports conversions from Primary actions in the standard and custom goals a campaign is optimising towards. The exception is a Secondary action in an applied custom goal: it is also used for bidding and reported in “Conversions”. “Conversion value” shows the assigned value of those conversions, not automatically revenue or profit. The campaign column “Conversion goals” helps identify which goals are selected. The documentation on Results reporting also describes “Results” at campaign level. The “Results” column reports conversions across Primary actions in all standard goals in the account. Conversions from goals the campaign is optimising towards appear normally; conversions from other standard goals appear greyed out. Secondary actions do not appear there. Custom goals are not displayed as their own grouping, although a Primary action they contain can appear through its standard goal. The Results column is not supported for App campaigns. “Results” and “Conversions” are therefore not the same figure in every setup.
The “All conversions” column is broader. It reports conversions from Primary and Secondary actions in standard and custom goals whether or not the campaign is actively optimising towards them. Depending on the setup, it can also include view-through conversions and certain call or store-visit data. It is a diagnostic view, not a direct representation of the Smart Bidding goal list. An increase in “All conversions” may result from more observed micro actions without any improvement in the primary business outcome.
Reports are therefore segmented by conversion action and source. The team places four views side by side: the campaign goals actually used, Conversions by action, All conversions by action and backend outcomes for the same period. Where available, value is also broken down by action. Categories support semantic organisation but do not replace a commercial cross-check. Differences between figures should first trigger an investigation. They must neither be added together automatically nor replaced by whichever interface appears most plausible.
Goal changes require a test contract
One hypothesis, one change and one rollback rule
Changing an action, an action status or the goal scope changes both optimisation and the interpretation of reports. The official instructions for updating conversion goals recommend checking affected campaigns under “Review campaigns” and saving them as a CSV before making the change. When an action is removed, it is archived and can be restored; its historical data is not simply deleted. Nevertheless, the new goal logic can materially change ongoing bid optimisation.
| Hypothesis | Baseline | Only planned change | Primary metric | Guardrail metric | Rollback rule |
|---|---|---|---|---|---|
| Qualified leads provide better guidance than forms | Forms, CRM quality and cost before the switch | Use Qualified lead as Primary in one pilot campaign | Cost per qualified opportunity | Lead volume, delay and close rate | Return to the old goal selection if feedback fails |
| The duplicate GA4 action is diagnostic only | Purchases from the tag and GA4 for each order | Keep GA4 purchase Secondary and use tag purchase as the leading source | Backend-confirmed purchases and value | Measurement gap in the primary source | Test an alternative source only after a verified outage |
| The account standard suits core campaigns | Goal selection and values for every core campaign | Apply the defined standard to a test group | Shared business outcome | Volatility, budget and outcome quality | Restore documented exceptions to their prior state |
| A micro goal is distorting bids | Micro-to-macro ratio and previous quality | Remove the micro action from the bidding scope | Macro conversions or value | Reach and qualified intermediate actions | Stop the change if the measurement chain was misclassified |
| A custom goal contains the wrong Secondary action | Actions, roles and campaign membership | Clean up or replace the custom goal | Intended outcome type | Volume for each included action | Restore the previous setup only with documented emergency approval |
The contract names exactly one hypothesis and one deliberately controlled change. Technical emergencies can, of course, be corrected immediately, but they are still logged. Changing the goal, budget, bidding strategy, attribution and landing page at the same time prevents a clean interpretation. Google describes a standard 7–14-day Smart Bidding learning phase, but this is not a promise that business performance will stabilise after exactly seven or fourteen days. The observation period depends on conversion delay, volume and business objective; the rollback rule is agreed before the test begins.
Seven approval gates lead to the account standard
Seven gates organise review, testing and rollout
The path prevents a technically visible event from immediately becoming an account-wide bidding signal. Every stage has a verifiable output and a responsible owner. If a team skips a gate, the previous register status remains in force.
- Business gate: The team names the real outcome, its commercial value and excluded cases. Without a shared definition, the status is STOP.
- Source gate: The tag, GA4, CRM or shop data is assigned to a unique transaction; IDs, value and currency are tested with controlled cases. Duplicate counting results in STOP.
- Quality gate: A sample confirms that the measured event genuinely matches the business definition. If the data is mature enough only for diagnosis, the status is OBSERVE.
- Role gate: Primary or Secondary is justified at action level; membership of standard goals and custom goals is checked separately. An unreviewed custom-goal exception results in STOP.
- Scope gate: The team lists campaigns using the account standard, campaigns with campaign-specific goals, the manager account responsible for conversion tracking and all exceptions. Only then does the precisely defined pilot group receive the change.
- Test gate: The contract from section 12 runs for a window appropriate to the data delay. Primary and guardrail metrics are compared with the backend and baseline; until then, the status remains CAMPAIGN TEST.
- Standard gate: Only an action that is technically stable, commercially correct and assigned to a clear owner becomes ACCOUNT STANDARD in the register, meaning that it is approved for a Primary role in an account-wide approved standard goal. The owner, review cadence and rollback rule remain in place after rollout.
The path does not necessarily run linearly to the end. A product view can remain under OBSERVE permanently after the quality gate. An infrequent offline conversion may require several test cycles. If later backend reconciliation identifies deterioration, an existing account standard returns to CAMPAIGN TEST or STOP. Governance does not mean certifying a setting once; it means proving repeatedly that the setting still deserves its role.
STOP rules protect bidding from false signals
When approval must be withheld or rolled back
An immediate STOP applies when double counting is unresolved, the business definition is missing or keeps changing, the currency is wrong, arbitrary fixed values are used, transactions are not unique or no responsible owner is named for a data source. The same applies when a Secondary action is hidden inside an applied custom goal without anyone noticing, a campaign uses goals other than those documented in the test contract, or an account-wide switch is planned without a list of affected campaigns.
A rollback is triggered if the primary source fails in production, offline data is no longer fed back in full, spam or unqualified leads increase sharply, values diverge from the backend or the tested outcome quality falls below the agreed guardrail. A decline in the raw number of conversions, by contrast, is not automatically an error: removing a worthless micro goal can reduce the count while improving the business logic of optimisation. The business evidence defined in advance is what matters.
Enhanced Conversions do not alter this governance. Starting in June 2026, Google began rolling out a single on/off setting that combines Enhanced Conversions for web and leads; the precise interface must still be checked in each account. According to the current documentation on Enhanced Conversions settings, supplied user data can be processed through tags, Data Manager and APIs. This is a data and matching layer. It does not automatically create a new goal, make an action Primary or replace either the account standard or the campaign selection. The technical implementation belongs in the next specialist guide, not in a supposed repair of the goal register.
STOP does not necessarily mean “turn off the campaign”. It may mean removing the action from the bidding scope, repairing the data source, removing a custom goal from the campaign, pausing the pilot or returning to the documented previous state. The status protects the objective function while the cause and ownership are clarified.
A 90-day plan moves from inventory to a defensible standard
Four phases from inventory to account standard
A 90-day period is a working framework, not a guarantee of sufficient data. An e-commerce account with daily purchase volume may answer individual questions more quickly; a B2B company with a long sales cycle needs longer to assess quality and revenue. The order is decisive: inventory first, clean-up second, then a limited test and only at the end a broader standard.
| Phase | Objective | Core work | Required evidence | Decision |
|---|---|---|---|---|
| Days 0 to 14 | Establish the goal inventory | Record actions, categories, roles, sources, custom goals, account standard and campaign exceptions | Complete register plus export of affected campaigns | STOP or OBSERVE for each action |
| Days 15 to 30 | Clean up the measurement foundation | Check test cases, IDs, values, currency, counting method, windows and backend reconciliation | No unresolved double counting; business sample passed | Approve test or repair |
| Days 31 to 60 | Test a limited goal change | Implement one hypothesis in a clearly named campaign group and log the change | Mature primary and guardrail metrics against baseline | CAMPAIGN TEST: continue, stop or expand |
| Days 61 to 90 | Embed governance | Approve a suitable action as standard and document exceptions and review cadence | Owner, monitoring and rollback rule confirmed | ACCOUNT STANDARD or further testing |
Technical foundations such as tagging, GA4 and Consent Mode are covered in the guide to setting up Google Ads conversion tracking with GA4 and Consent Mode. To assess the commercial effect of the approved signal, the next decision is how the business should choose the right Google Ads bidding strategy for clicks, CPA or ROAS. If customer status itself becomes part of the objective function, a separate review is needed to determine how to measure new customer acquisition in Performance Max correctly. These in-depth guides do not replace the register; they mark adjacent decisions that need their own methodology.
Frequently asked questions about Google Ads conversion goals
Eight answers that prevent goal chaos in an account
The following answers refer to the current Google Ads goal architecture. They do not replace either a technical tracking audit or business approval within the company.
Does Smart Bidding automatically use every Primary conversion?
No. With regular standard goals, the action must be Primary and the campaign must actually use the associated goal. A Primary action outside the campaign's goal selection is not an explicit optimisation goal for that campaign and does not appear there in “Conversions”; Google may nevertheless use such data to improve predictions. The action role and campaign goals must therefore always be reviewed together.
Are Secondary conversions not counted at all?
They are counted. They generally appear in “All conversions” and can be important for diagnosis, funnel analysis or quality control. They are normally not used for bidding in standard goals. The decisive exception is an applied custom goal: a Secondary action inside it can still guide bids.
What does “account-wide” mean for conversion goals?
It means that a standard goal is designated as Account Default for campaigns that adopt that setting. It is not an immutable requirement for every campaign. Campaign-specific goals can replace the standard locally. Account-default goals do not apply to App campaigns; their conversion actions are selected at campaign level.
Should Add to cart, Begin checkout and Purchase all be Primary?
Generally, no—not merely because all three can be measured. If Purchase is the actual outcome, the earlier stages can support diagnosis as Secondary actions. An intermediate action used for bidding needs a justified relationship with business value, appropriate values and a replacement or review rule.
Can a GA4 import remain Primary alongside the Google Ads tag?
Multiple actions can technically exist, but the same transaction may then be counted twice in business terms. The team selects one leading data source and compares identical test orders by action, ID, value and time. The second source often remains Secondary until a clearly different purpose is demonstrated.
When is a custom goal useful?
When a single campaign needs a justified, manually assembled combination of specific actions that standard goals cannot represent appropriately. It is not a catch-all folder. Every bidding-eligible action it contains affects bidding in the campaign where it is applied, including Secondary actions; Store Sales Direct conversion actions are the exception and remain ineligible for bidding. Each membership must therefore be approved separately.
Does removing a conversion action delete its history?
A removed action is archived and can be restored; its previous statistics are not simply erased. Removing it can still change reports and optimisation. The affected campaigns should be saved first, with the baseline and route back documented.
How long should a team wait after changing a goal?
There is no universal number that guarantees stability for every account. The window depends on conversion delay, volume, bidding strategy and the business cycle. Genuine measurement errors are corrected immediately; performance is assessed only once the agreed level of data maturity has been reached.
Next step: approve conversion goals as a control plan
Turn a conversion list into an approved control plan
A defensible architecture does not begin by switching an action from Secondary to Primary. It begins with a real outcome, a unique source and a business cross-check. Category, action role, goal type and scope are then reviewed. The seven-stage path makes it clear why an action is observed, tested in one campaign or approved as an account standard.
The conversion goal register creates a shared language for management, marketing, sales, analytics and the agency. It also records which actions deliberately remain Secondary, which campaigns do not inherit the standard and which rollback rule applies if something goes wrong. A change does not become risk-free as a result, but it does become traceable and reversible.