Back to blog

Google Ads Accounts for Multiple Websites: Ownership, Access and Conversions

Plan Google Ads around advertisers, budgets and business outcomes rather than domain counts. Review manager access, shared conversions, destination consistency and migration checks.

A company with a brand site, regional site and campaign page does not necessarily need three ad accounts. An agency serving three independent clients should not copy the same structure merely because the site count matches. Establish the advertiser, budget responsibility and business result to record first.

Structure should make responsibilities, access and data understandable, not solve reviews or restrictions through extra accounts. Advertising must still meet current policies and applicable business requirements.

Map websites to business relationships

List domains, advertisers, brands, billing leads, main landing pages and target events. One domain may serve several products; one product may span domains for inquiries or purchases. URLs alone cannot determine separation.

Describe outcomes as specific events, such as completed appointments or valid inquiries, not merely “more conversions.” Form completion, sales-qualified lead and final sale are different stages. Specify which drive reporting and optimization.

SituationConfirm firstStructural concern
Regional sites of one entityMatching markets and goalsRegional responsibility and event definitions
Product lines of one brandSame business outcome?Suitability for shared learning
Independent client sitesAuthorization, payment and data boundariesSeparate client accounts and access
Campaign landing pagesSame advertising business?Links, budget and end-of-campaign maintenance
Cross-domain inquiry or checkoutWhere the event occursTracking and actual user journey

This identifies questions, not a fixed account-count formula. Business, advertising and data leads should agree before technicians build around domains alone.

Manager accounts centralize management, not businesses

Google’s manager-account guidance describes managing several Google Ads accounts from one entry point. It creates management relationships and permission-based work, not an upgrade into an all-purpose account.

For independent clients, clarify each account, authorization and responsible person before manager linking. Central visibility does not let clients see each other or require an agency to hold personal login credentials.

Grant only the necessary scope and have members verify visible accounts. At project end, inspect both membership and manager links; removing a name from an internal sheet does not end access.

Conversion definitions are easier to overlook than account counts

Products sharing a booking flow may not have equal value. Sharing default goals between free downloads and enterprise sales leads can inflate apparent growth without answering business questions.

Google’s cross-account conversion guidance explains manager-created shared conversions and checking the goals campaigns actually optimize during a switch. Share according to outcomes and data use, not simply fewer tags.

Document each event’s trigger, page, duplicate risk and verifier. Align website, analytics and ad-system names so identical labels do not mean different actions.

Plan cross-account changes

Record existing conversion sources and active goals before defining scope, order and acceptance criteria. Do not delete every tag to “clean old data”: missing conversions then become hard to distinguish from business changes.

Follow current official transition steps. Check duplication, optimization goals and correct source references per account. Mark the switch in historical and new records rather than merging them into an apparently continuous trend.

If nobody can explain why a goal is primary, verify it before letting automated advertising continue relying on it. The value is understandable data, not a tidier hierarchy.

Check displayed and final destinations across domains

Google’s destination-mismatch policy requires accurate representation of destinations and covers mismatches among display URLs, final URLs and tracking templates. Multi-site businesses must catch templates using old brands or redirecting to other domains.

Check each ad promise, landing page, mobile experience and page after tracking. Opening only an unparameterized home page does not validate the journey. Do not show reviewers different content from real users.

Regional redirects, language switches and third-party tracking can alter paths. Preserve actual user conditions in tests, fix configurations and follow the real account status and review process.

Align naming and team workspaces

Account, campaign and website records should identify entity, market and task. Assign budget approval and landing-page changes so advertising does not retain outdated links after client updates.

For authorized client sessions on a computer, explore environment groups and member permissions on the PurpleMark website. Naming environments by client and business and assigning responsible people helps confirm the current object before entering the ad interface.

Platform authorization remains on the platform. Check environments, manager links and tools separately. One access assignment is not another business authorization, and new accounts must not bypass existing policy restrictions.

Validate after restructuring

Check client relationships, payment responsibility and member visibility first, then destinations, event triggers and goal references. Coordinate tests with technical leads and label test records so they do not contaminate business conclusions.

Compare data with consistent definitions and time windows, recording transition changes. Short fluctuations do not prove better performance. Investigate measurement first when events duplicate, sources disappear or optimization goals are wrong.

Derive structure from business boundaries

Define advertiser, budget and outcomes, then account hierarchy, then tags, permissions and workflows. Repeat for new websites rather than mechanically adding one account per domain.

A scalable structure explains why every account exists, why each member has access and what each conversion represents.