After an agency change, the company should retain continuity across Google Ads, Meta assets, GA4, measurement, and historical data. No single “owner” label decides that outcome. Administrative roles, manager relationships, platform-level asset ownership, payment profiles, contracts, and infrastructure control must be checked separately. A payment profile identifies the entity responsible for billing; it does not by itself prove ownership of all account data or intellectual property. The safest design is client-created assets, at least two client-side administrators, and revocable agency access.

Operator guidance from an agency that manages these accounts — not legal advice, and platform mechanics change, so verify the current setup for your accounts.
TL;DR
- The governing principle: you own the accounts and data; the agency is a revocable manager. Put it in the contract, and structure the accounts to match.
- Access, billing, and ownership are separate layers. The payment profile says who pays; administrative roles and platform structure determine who controls the asset.
- Google Ads: your account on your billing, the agency's manager account (MCC) linked. If it's on the agency's billing, the history can stay with them.
- Meta: your Business Manager owns the ad account, Page, pixel and datasets; the agency is a partner. Meta accounts generally don't move between Business Managers, so start in yours.
- GA4: losing the property means losing history permanently — a new property starts from zero.
- The tagging layer (pixel, Conversions API, server-side GTM) is often the real prize — a compounding asset you must own.
- Check ownership now, not at the exit, and require an offboarding SLA in the contract.
The governing principle: owner vs manager
Every platform below follows the same rule, so start here: the client owns the accounts and data; the agency is a manager with revocable access. A manager can create campaigns, spend budget and optimise — everything needed to run the account — without owning it. Ownership is a separate question: whose account is it, on whose billing, inside whose structure?
The confusion that costs companies their data is treating access and ownership as the same thing. They are not. An agency with admin access looks, day to day, exactly like an owner — it does all the same things. The difference only appears at the exit: revoke a manager's access and the account stays with you; but if the account itself belongs to the agency, revoking access leaves you with nothing, because there was nothing of yours to revoke access to. The whole game is making sure every account is yours, with the agency merely linked.

Access, control, and billing are three separate questions
A payment profile stores the entity legally responsible for payments, tax information, and payment methods. It is an important financial-control layer, but it is not a universal deed to the account, its data, creative, or configuration. Google separately models the Ads client account, linked manager account, optional owner-manager role, and payment profile.
An audit should answer separately: who has administrative access, whether the company can unlink the manager, which manager is marked as owner, who is responsible for billing, and what the contract says about data and handover. The company needs its own administrators independent of the agency. A payment profile can be changed through a billing transfer (“Change who pays”) when the required permissions are available, so it should not be described as an immutable ownership marker.
Google Ads
Google Ads separates the account from the manager account (MCC) that oversees it. The right structure: your Google Ads account, on your billing profile, with the agency's MCC linked for management access. The agency runs everything through that link; the account and its history belong to you.
The risky structure is an account created by the agency manager with no client-side administrator and billing controlled only by the agency. Google states that even an owner manager does not take data ownership away from the client account, and a client administrator can unlink the manager. The practical failure occurs when the company lacks its own administrator or cannot control billing. Review the “Owner” field under Managers and complete a billing transfer before offboarding when the client will become the payer.
Why the history matters: Google's Smart Bidding learns from your conversion data over time. A new account is a cold start — the bidding algorithms begin from scratch, and it takes weeks or months to recover the performance a mature account had. Losing the account is not just losing records; it is resetting the machine learning that made the account efficient. Your conversion actions and their history — including enhanced conversions and Customer Match audiences — live with the account.
Meta (Facebook and Instagram)
Meta's structure makes ownership especially important, because assets generally do not move between Business Managers. The right structure: your Business Manager (Business Portfolio) owns the ad account, the Page, the pixel/dataset and the audiences, and the agency is added as a partner with access. Starting in the agency's Business Manager and hoping to move it later is the trap — Meta ad accounts typically cannot be transferred between Business Managers, so an account created in the agency's portfolio may not be moveable to yours at all.
The assets that matter on Meta:
- Ad account — in your Business Manager, agency as partner.
- Page and Instagram — owned by your Business Manager.
- Pixel / dataset (and the Conversions API) — yours; this is where conversion history and much of the audience value lives.
- Custom and Lookalike audiences — these live tied to the dataset; lose the dataset and you lose them.
Because the audiences and conversion history are bound to the pixel/dataset, and the dataset lives in a Business Manager, "who owns the Business Manager" quietly decides who keeps the most valuable Meta assets. Start in yours. The Conversions API setup should point at your dataset, not the agency's.
GA4 and the analytics stack
GA4 can move a property, including reporting data, streams, settings, and most linked integrations, between accounts when the required Administrator and Editor roles exist and none of Google's documented restrictions applies. Historical data cannot be copied into a newly created property. If the company loses access and cannot perform the move, the replacement property starts from zero.
The right structure: your GA4 account and property, with the agency added as a user. GA4's "Move property" can shift a property between accounts you control, but it does not conjure back data from a property you have lost. The same applies to the wider stack — Search Console, Merchant Center, Google Tag Manager — all should be your accounts with agency access. The reason to implement GA4 properly under your own account is precisely this: the history is irreplaceable.

The tagging layer is the real prize
The most overlooked and most valuable asset is the tagging and measurement layer: the Meta pixel and Conversions API, GA4 events, and especially server-side Google Tag Manager. This is where conversion history accumulates and where audiences are built, and it is a compounding asset — every month of clean data makes bidding smarter and audiences richer.
The ownership question here is subtle: who hosts and pays for the server-side infrastructure? If the agency hosts your server-side GTM on its own cloud account, leaving can mean losing the tagging setup that took months to build and validate. The tagging layer should be hosted on your infrastructure (or clearly transferable), with the agency configuring it. The thesis to hold onto: the pixel and conversion history are a compounding asset you must own — it is the hardest thing to rebuild and the most expensive to lose.

Creative, copy and landing pages
Beyond accounts and data, there is the creative you paid for — ads, copy, landing pages, design. You should own it, including the raw source files, with intellectual property assigning to you on payment. Losing access to the working files (not just the published asset) means you cannot edit or reuse what you paid for. This should be explicit in the contract, because in many jurisdictions IP does not transfer automatically without a written assignment.
The honest exception
There is a legitimate case for an agency-owned account: some agencies run certain accounts (often for very small or short-term clients) inside their own structure for operational simplicity, and disclose it. This is not automatically wrong — but it is a decision to make with eyes open, and to de-risk. If an account is agency-owned, the contract should at minimum guarantee an export of data and audiences on exit, a defined hand-back process, and clarity that the client can recreate equivalents. The problem is never disclosure; it is the undisclosed agency-owned account discovered at the exit.
Glossary
- Owner vs manager — the account belongs to the owner; a manager has revocable access to run it.
- Billing profile — whose payment method and entity the platform bills; the practical marker of ownership.
- MCC (manager account) — the Google Ads manager account an agency links to a client's account.
- Business Manager / Business Portfolio — Meta's container that owns ad accounts, Pages, pixels and datasets.
- Dataset / pixel — Meta's measurement object holding conversion history and audiences.
- Cold start — a new account's loss of the machine-learning history that made the old one efficient.
- Server-side GTM — server-hosted tag management; who hosts it decides who keeps the tagging setup.
Offboarding checklist
Before you leave, confirm each of these is on your account with the agency merely accessing it:
- Google Ads — account on your billing profile; MCC linked, not owner.
- Google Analytics (GA4) — your account and property; agency is a user.
- Meta Business Manager — owns the ad account, Page, pixel/dataset and audiences.
- Conversions API / pixel — pointing at your dataset.
- Server-side GTM — hosted on your infrastructure or clearly transferable.
- Search Console, Merchant Center, Tag Manager — your accounts.
- Creative source files — delivered to you, with IP assigned.
- Access hand-back SLA — agreed timeline (e.g. 48 hours to a few days), independent of final invoices.
Why this matters beyond the exit
Ownership is not only an exit issue — it affects the value of the business. In an acquisition, buyers run marketing due diligence and check exactly this: does the company own its accounts, data and tagging, or is its growth engine borrowed from an agency? A company whose conversion history, audiences and analytics sit on an agency's billing is a fragility a buyer discounts. Owning your accounts is both operational hygiene and a protection of enterprise value.
Red-flag clauses vs what to require
| Red flag | What to require instead |
|---|---|
| "The agency owns and manages the ad accounts" | Client owns accounts; agency has revocable access |
| Accounts on the agency's billing profile | Accounts on your billing profile |
| Meta ad account created in the agency's Business Manager | Account created in your Business Manager, agency as partner |
| Server-side GTM hosted on the agency's cloud | Hosted on your infrastructure or clearly transferable |
| No mention of data/audience export on exit | Defined export and hand-back on termination |
| Access returned "when practical" | Offboarding SLA (e.g. 48h), independent of final invoices |
How Space Ads approaches account ownership
We run these accounts as a manager, and our position is that the client owns everything — accounts, data, pixels, audiences and tagging — with our access as a revocable link. The failure we see most in accounts we inherit is the previous setup: a Google Ads account on the old agency's billing, a Meta ad account trapped in the old agency's Business Manager, and server-side tagging on infrastructure the client never controlled. The client did not lose access because someone was malicious; they lost it because ownership was never structured correctly in the first place.
Our approach is to set up (or migrate to) client-owned accounts from day one — your billing, your Business Manager, your GA4, your tagging infrastructure — with our access linked on top. That way there is nothing to hold hostage and nothing to lose at the exit, and the compounding assets keep compounding regardless of who manages them. That is the ownership layer beneath performance marketing, and it is spelled out in the marketing agency contract checklist. When ownership needs senior oversight across the whole stack, a fractional CMO engagement holds the same line.
FAQ
Who owns my Google Ads account when I leave an agency?
You should — if the account is on your billing profile with the agency's manager account (MCC) linked for access. If the account was created inside the agency's MCC on the agency's billing, the account and its conversion history can stay with them when you leave. Access is not ownership; the billing profile decides, so check it before the exit.
Does my agency own my Meta ad account?
It should not. Your Business Manager should own the ad account, Page, pixel/dataset and audiences, with the agency added as a partner. Meta ad accounts generally cannot be transferred between Business Managers, so if the account was created in the agency's Business Manager, you may not be able to move it to yours — which is why starting in yours matters.
Will I lose my GA4 history if I change agencies?
Only if you lose the property. GA4 history does not transfer and cannot be rebuilt — a new property starts collecting from zero. If your GA4 property is under your own account with the agency as a user, you keep everything. If the agency created it under an account you do not control, the historical data can be lost permanently.
Who owns the Meta pixel and Conversions API?
You should, via your Business Manager's dataset. The pixel/dataset holds conversion history and the custom and lookalike audiences built on it, and those live wherever the dataset lives. If the dataset is in the agency's Business Manager, the audiences and history go with it, so the Conversions API should point at your dataset from the start.
Who owns server-side Google Tag Manager?
Whoever hosts and pays for the server infrastructure effectively controls it. If the agency hosts your server-side GTM on its own cloud account, leaving can mean losing the tagging setup. Server-side GTM should be hosted on your infrastructure or be clearly transferable, with the agency configuring it rather than owning the hosting.
How do I check who owns my ad accounts?
Check the billing profile and account structure on each platform: in Google Ads, whose payment method the account is billed to and whether it sits under the agency's manager account; in Meta, which Business Manager owns the ad account and dataset; in GA4, which account the property belongs to. If the accounts are on the agency's billing or inside the agency's containers, ownership is not yours yet.
What should the contract say about account ownership?
That the client owns all ad accounts, analytics properties, pixels/datasets, audiences and tagging infrastructure, and that the agency has revocable access as a manager. It should also require an offboarding SLA — a defined timeline for handing back access and delivering data and creative source files — independent of settling final invoices.
Key takeaways
- You own the accounts and data; the agency is a revocable manager — put it in the contract and structure accounts to match.
- Access is not ownership; the billing profile and where the account lives decide.
- Google Ads on your billing (MCC linked); Meta in your Business Manager; GA4 under your account.
- The tagging layer — pixel, Conversions API, server-side GTM — is the compounding asset to own.
- Check ownership now, require an offboarding SLA, and treat it as enterprise value, not just exit hygiene.
Sources and further reading
- Google Ads Help — About manager accounts (MCC)
- Google Ads Help — Owner managers and client-account rights
- Google Ads Help — Change the payment profile and billing ownership
- Meta Business Help — Business Manager, ad accounts and partner access
- Google Analytics Help — Move a GA4 property with its reporting data
Continue learning
- What should be in a marketing agency contract? A founder's checklist
- Server-side tagging and the Conversions API — feeding clean signals back
- Customer Match in Google Ads — what it is and how to use it
- Marketing due diligence: what PE and strategic buyers check
- GA4: why implement it and what are the benefits
- Performance marketing, run on client-owned accounts
Continue reading

Marketing Dashboard: What Growth Teams Should Track Across Ads, SEO and Sales
A marketing dashboard should connect ad spend, SEO, GA4, CRM and sales outcomes into one decision view. This guide explains what growth teams should track and how to avoid dashboard noise.

What Should Be in a Marketing Agency Contract? A Founder's Checklist
A marketing agency contract should make three things unambiguous: who owns the accounts and data, how money and ad spend are separated, and how you exit with everything you built. This clause-by-clause checklist covers what a fair contract says — from an agency that signs and honours them.

Marketing Reporting in 2026: Cross-Channel Client Reports Across Google, Meta and TikTok
Better reporting is less about prettier charts and more about trustable decisions. This guide shows what to reconcile across Google, Meta, TikTok and GA4, how to answer client questions without weekly exports, and where plain-language reporting is replacing static dashboards.




















