For B2B SaaS, Google Ads account architecture should make three decisions clear: which demand receives budget, which message each buyer sees, and which commercial outcome guides optimisation. Use campaigns where you need distinct controls and ad groups where a group of searches can share a coherent message and landing page.
This guide focuses on deciding what belongs at account, campaign and ad-group level. For the next step, see the guide to structuring SaaS search campaigns.
Understand the three levels before splitting the account
Google describes its advertising hierarchy as accounts, campaigns and ad groups. Campaigns contain budgets and targeting settings; ad groups organise related ads and keywords. See Google’s account organisation guidance.
For a SaaS team, that hierarchy should reflect actual operating decisions. A different keyword does not automatically justify a new campaign. A different budget owner, market requirement or conversion objective may.
A decision checklist for each proposed split
- Do we need an independent budget or campaign setting? Consider a separate campaign when a market, product or intent category needs a decision that cannot be made appropriately within the existing campaign.
- Does the buyer need a different message or page? Consider a distinct ad group when the search theme requires a different promise but shares the campaign’s budget and settings.
- Are billing, ownership or administrative requirements different? Review whether a separate account is warranted. Do not create extra accounts merely to make reporting look tidy.
- Can we explain how this split changes a decision? If the answer is only “more granular reporting”, consider labels or reports before adding structural complexity.
- Can the planned budget and available conversion signal support the design? A structure with many small segments can become difficult to evaluate. There is no universal campaign count that suits every SaaS company.
Separate existing demand from acquisition decisions
Brand searches, category searches, competitor comparisons and early problem research represent different buying situations. Review them separately before concluding that the account is acquiring new customers efficiently.
A useful starting design may separate brand and high-intent non-brand activity so budgets and commercial results are explicit. Competitor or exploratory campaigns should have a clear test purpose, relevant pages and an agreed evaluation window. These are planning choices, not mandatory campaign types for every advertiser.
Do not mistake a low blended cost per lead for evidence that every category is working. Compare qualified opportunities and customer outcomes where tracking supports the comparison. Keep attribution limitations and the sales cycle visible.
Build ad groups around one answer a buyer needs
Suppose a SaaS product supports both expense management and invoice approval. An expense-software search and an invoice-approval search may need different ads and pages, even when they share a market and campaign budget.
Keep searches together when the same honest promise and landing page answer them. Split the theme when the use case, buyer expectation or required evidence changes. Avoid building a separate ad group for every wording variation without a corresponding message difference.
Use the landing-page message matching guide to check whether the page continues the search conversation. Changing account structure cannot compensate for a page that describes the wrong use case.
Choose conversion goals before judging the architecture
Document what each campaign is intended to achieve: a qualified demo, an activated trial or another measurable commercial event. Then inspect the actual conversion actions and goals selected for that campaign.
Primary conversion actions can inform bidding when the campaign uses their associated goal. Secondary actions are generally observation-only, but a secondary action included in a custom goal can be used for bidding. Check the configuration rather than relying on the action label alone. See Google’s primary and secondary conversion guidance.
A deeper CRM stage may be commercially useful but arrive slowly or infrequently. Assess signal quality, reporting delay and available volume before changing bidding inputs. Do not replace an established goal with a poorly tested event simply because its name sounds closer to revenue.
Worked example: one product with two markets
The following is a hypothetical planning example, not a client result. A sales-led SaaS company sells one product in the UK and US. Its teams have different sales coverage and separate market budgets.
- Consider market-level campaigns because budget allocation and targeting require independent decisions.
- Within each market, keep brand performance distinguishable from non-brand acquisition.
- Organise non-brand ad groups around the product’s verified use cases, with an appropriate landing page for each theme.
- Document the conversion goal and CRM qualification definition used in each market.
- If a segment has too little activity to evaluate reliably, revisit the design and test scope rather than inventing certainty from a small sample.
The useful output is a map with five fields for every campaign: buyer intent, market, budget responsibility, landing-page destination and conversion goal. Any campaign that cannot be described clearly in that map needs investigation.
Restructure without losing the ability to learn
Before editing a live account, export the existing configuration and record the current performance baseline. List what will change, why it should help, what could confound the comparison and how you would reverse the change.
Implement in manageable stages where practical. Avoid changing account structure, conversion definitions, landing pages and bidding targets simultaneously unless the situation requires it; otherwise it becomes difficult to identify what caused the result. Allow for the conversion delay and sales cycle when evaluating performance.
After implementation, check actual search terms, spend distribution, landing-page destinations and conversion reporting. Review qualified outcomes alongside platform metrics. Keep a dated change log and distinguish observations from explanations that still need testing.
When to get help
If the account’s structure obscures where budget goes or which campaigns produce suitable prospects, Google Ads Growth covers ongoing management. If the underlying constraint is unclear, an optional Search Diagnostic can establish priorities. See the current scope and pricing before choosing an engagement.
Book a 30-minute fit call to discuss the account, lead-quality problem and available evidence.
Frequently asked questions
How many campaigns should a SaaS account have?
Enough to support necessary budget and targeting decisions. Start with your markets, buyer intents, commercial objectives and signal availability. A fixed campaign count is not a useful target.
Should every country have its own campaign?
Only when separate controls are useful. Differences in budget responsibility, language, sales coverage, customer economics or targeting may justify separation. Similar markets with limited volume may need a simpler design.
Does a cleaner structure guarantee better lead quality?
No. Lead quality also depends on the offer, queries, messaging, landing pages, conversion signals and sales follow-up. Architecture makes those decisions easier to control and evaluate; it does not guarantee their outcome.