Who Owns the Meta Pixel, Catalog, and Custom Audiences When an Agency Runs Your Ad Account

Which assets are separate from the ad account

Meta does not treat the ad account as a container that automatically carries your data assets with it. Pixels (now surfaced as datasets), catalogs, custom audiences, offline event sets, and custom conversions are separate assets inside a business portfolio, each with its own owning business and its own access relationships.

Meta's Business Asset Management documentation says business asset groups can contain 'ad accounts, Pages, Facebook pixels, offline event sets, apps, catalogs, custom conversions and Instagram accounts,' and that each asset 'can be owned by a business or shared to provide access to an agency.' Meta's Business Help Center lists catalogs, datasets and pixels, offline event sets, and custom conversions as data sources in a business portfolio.

The practical consequence: an agency can run your ad account while the pixel feeding it belongs to a different business entirely. Meta's Ads Pixel API exposes an owner_business field — the ID of the business that owns the pixel, or null if no business has claimed it yet. When you audit custody, check every asset individually. Being able to see the ad account tells you nothing about who owns the data sources attached to it.

Who owns a pixel created by an agency

Meta's Ads Pixel reference separates two facts: the creator (the user who created the pixel) and the owner_business, defined as the ID of the business that owns the pixel, or null if the pixel has not been claimed by any business yet. Ownership sits with the business, not with the person who clicked create.

So if your agency created the pixel inside its own Business Manager — or inside an ad account its business owns — the agency's business is the owner, and your business typically receives shared, task-based access rather than ownership.

The most concentrated version of this is Meta's 2-tier Business Manager model for onboarding clients at scale. Meta states that by default the client does not have access to the child Business Manager while the partner has complete access, and that the partner can create the ad account and associate assets such as the pixel, custom audiences, and product catalog with it. In that model the partner also pays Meta directly and maintains the billing relationship with you — convenient, but ownership, data, and billing all sit on the provider side unless your contract says otherwise. If you want to own the pixel, it should be created in, or claimed by, your own business portfolio and then shared out to the agency.

Sharing versus transferring an asset

Meta's documented model for pixels is sharing, not transfer. The owning business shares the pixel to an agency business with permitted tasks: ANALYZE (view, analyze, and advertise), UPLOAD (send website conversion data to the dataset), ADVERTISE (connect ad accounts and use the dataset for advertising), and EDIT (manage the dataset — Meta notes EDIT access is currently restricted and requires allowlisting through a Meta representative). If the two businesses have no existing relationship, Meta creates a sharing agreement with the pixel attached, and the pixel is shared once the recipient approves. Meta also notes there is a limit on how many businesses a single pixel can be shared with. Throughout, the owning business keeps the asset and can delete the sharing connection.

Ad accounts behave differently. A business can claim an ad account it administers, which Meta describes as a one-time procedure — once claimed, the account can only be managed in that Business Manager. Meta's API also records whether your business acts as OWNER or AGENCY on each account, and it steers most marketing companies toward requesting access to client-owned accounts rather than claiming them.

Custom audiences follow a third pattern: a sharing relationship between Business Managers that runs in one direction only. None of these flows amounts to a clean handover of the keys, so plan transitions around re-creating assets in your own portfolio rather than expecting a transfer button.

Catalogs, custom audiences, and what cannot be moved

Catalogs have their own role model, separate from ad account permissions. A Catalog Admin (the MANAGE and ADVERTISE tasks) has full read and write control: creating, updating, and deleting items, managing feeds, attaching the catalog to pixels and apps, creating product sets, and changing catalog settings. A Catalog Advertiser (ADVERTISE only) can create product sets and run Advantage+ catalog ads with the catalog but cannot edit its products, feeds, or catalog settings. If the agency owns the catalog, the feed, feed rules, and catalog-to-pixel links live in their portfolio — you may be able to advertise from it without being able to edit, export, or re-point it.

Custom audiences are likewise anchored to the business that created them. Meta describes a custom audience as one advertisers build from their own data sources or Meta engagement data. Sharing one requires a partnership relationship between the two Business Managers, Business Manager admin permission to initiate it, and an affirmation of compliance with Meta's Custom Audience terms — and the share runs in one direction only, so the recipient cannot pass it onward.

What cannot be moved at all is the event history inside a pixel or dataset. Meta's documentation provides sharing connections, not an export of historical pixel events, so a new pixel created in your portfolio starts collecting from zero. Meta does not document a self-serve process or timeline for migrating dataset history between businesses — treat that history as non-portable.

What you lose if access ends before a transfer

If the relationship ends while assets still sit in the agency's portfolio, access can disappear quickly. The pixel-owning business can delete the pixel-sharing connection using an admin access token, which ends your ability to analyze, upload to, or advertise with that dataset. Because custom audience sharing is one-directional, audiences the agency owns simply stop being available to your ad accounts when the relationship is removed.

Restrictions compound the risk, and they apply at distinct levels. Meta's Advertising Standards state that if a Business Account — the business portfolio — or its assets, meaning an ad account, Page, or user account, is restricted, that account or asset can't be used to advertise across Meta's technologies. A restricted agency portfolio can therefore freeze assets you depend on even when your own business is in good standing, and a restricted person at the agency can block actions that require an admin.

There is also a data-hygiene gap. Practitioners writing for AdExchanger warn that when a contract ends, pixels are 'supposed to stop collecting data,' but that is not always the case — zombie pixels can keep sending your visitors' data to a dataset you no longer control. Meta does not document a grace period or a process for restoring shared assets after access is revoked, so treat anything outside your portfolio as losable.

Asset custody checks before signing

Before you sign with an agency or infrastructure provider, run a custody check on every asset class:

• Pixel/dataset: have it created in, or claimed by, your business portfolio, then shared to the agency with ADVERTISE or ANALYZE tasks. Verify the owner_business, not just visibility in Events Manager.
• Catalog: your business should own it; grant the agency the minimum role it needs. Catalog Advertiser is enough if it only runs Advantage+ catalog ads.
• Custom audiences: build them in your Business Manager from your own data sources. If the agency needs access, use Meta's documented sharing relationship and record the relationship_type.
• Ad account: know whether your business is OWNER or AGENCY on the account — Meta's API exposes this as access_type. Be cautious about letting an agency claim an account you administer, because claiming is a one-time procedure that locks management to one Business Manager.
• Structure: treat 2-tier child Business Manager onboarding with care — Meta notes the client has no access by default. If a provider uses it, get written commitments on asset ownership, billing transparency, and exit.
• People and credentials: Meta's best practices say storing customer passwords is not an approved model. Access should run through Business Manager grants that you can revoke.
• Offboarding clause: require the agency to keep sharing connections alive until your replacement pixel and catalog are live, and to remove its code from your site afterward. Practitioners recommend keeping a complete inventory of the pixels on your site and knowing where each one sends data.