Two business owners came to us with a problem they didn’t know they had. We’ll call them PBL (name redacted for confidentiality). They had a real brand, real revenue, and months of Meta ad spend behind them. What they didn’t have, it turned out, was ownership of the one asset all that spend had quietly been building: their pixel.

Every dollar they had poured into ads had trained a pixel that lived inside their old marketing company’s Business Manager. The audiences, the conversion data, the months of learning that make a pixel actually valuable, all of it sat behind a wall of ownership they couldn’t cross. They had paid for the engine. They just didn’t own it. When they came to us to grow, we found out the growth engine wasn’t theirs to drive.

So we did what we do. We fought to get it back. We chased down the portfolio, made the case, pushed for the transfer. In the end, we couldn’t pry it loose. The only honest path left was the hard one: start over. New portfolio, new pixel, from zero. For this client, that reset is going to cost thousands in sales while a brand-new pixel relearns everything the old one already knew. That is the real price of a trap most brands never see coming. Here is how to spot it before it costs you.

The trap: your assets live in someone else’s Business Manager

Every Meta ad asset, the pixel/dataset, the ad account, the Facebook page, the product catalog, the audiences, lives inside a Business Manager (now Meta Business Portfolio). Whoever owns that portfolio owns those assets. Not whoever pays for the ads. Not whoever the brand belongs to. The portfolio owner.

The problem shows up when a previous agency, a “marketing partner,” or a platform provider created those assets inside their portfolio and merely granted the brand access. Access is not ownership. That was exactly PBL’s situation: their old marketing company had built the pixel, the ad account, and the page inside its own portfolio, then handed the owners a set of keys instead of the deed. They could run ads. They couldn’t fully control or extract their own data, and they couldn’t complete the setup they actually needed.

Why this blocks Conversions API

Conversions API (CAPI) is how you send conversion events to Meta server-to-server, instead of relying only on the browser pixel that iOS updates and ad blockers quietly break. In a post-privacy-update world, CAPI is not a nice-to-have, it’s how you keep your event data accurate enough to optimize and attribute against.

But CAPI is bound to the dataset (the pixel’s data source), and configuring it requires genuine ownership-level control of that dataset, generating access tokens, connecting your server or store integration, deduplicating events against the browser pixel. If the dataset sits in a portfolio you don’t control, you can’t do any of that cleanly. That is the wall PBL hit. They were pouring budget into an account while stuck on degraded, pixel-only tracking they had no way to fix.

Access lets you run ads. Ownership lets you set up Conversions API, export your audiences, and take your data with you. They are not the same thing.

Run an asset-ownership audit, before you scale

We run this audit at the start of every paid engagement, and we’d urge any brand to run it today. Inside Meta Business Settings, check who owns, not just who can access, each of these:

• The dataset / pixel. Which Business Portfolio is it under? Can you generate a CAPI access token, or are the controls greyed out?
• The ad account. Is it owned by your portfolio, or shared into it by another business?
• The Facebook page and Instagram account. A page owned by an outside portfolio can be pulled at any time, taking your reviews, followers, and ad history with it.
• The product catalog and custom audiences. Audiences you built from your own customer list can be stranded in a portfolio you don’t own.

The tell is always the same: if there’s a business name you don’t recognize sitting in the “owner” column, or you have “partner” access instead of ownership, you have a problem to fix before you spend another dollar scaling. PBL had that exact tell. By the time anyone looked, the spend was already stacked on top of it.

The right Business Manager structure

The structure that keeps you safe is straightforward, and it’s the one we set up for every client from day one:

• The brand owns the Business Portfolio. Created under an email the brand controls, not the agency’s, not a vendor’s. This is the root of everything.
• The portfolio owns the core assets. Pixel/dataset, ad account, page, Instagram, and catalog all live inside the brand’s portfolio.
• Agencies and partners get assigned access, not ownership. We operate as a partner with the permissions we need, and if the relationship ever ends, the brand revokes our access and keeps every asset, every audience, and every event.

This is the difference between renting your marketing infrastructure and owning it. When the brand owns the portfolio, switching agencies is a permissions change, not a migration crisis.

Why you’ll never be the one fighting for your assets

PBL’s story has a villain, and it isn’t Meta. It’s a setup where the company that did the marketing quietly kept the marketing. We build the exact opposite way, on purpose. When you work with GrowthHouse Digital, the pixel is yours. The portfolio is yours. The audiences, the page, the catalog, and every dollar of pixel learning your budget pays for are yours, sitting inside a portfolio created under an email you control. We work inside it as an assigned partner, nothing more. If we ever part ways, you revoke our access and walk away with everything intact. There is nothing to fight over, because we never built a wall to trap you behind in the first place.

CAPI setup prerequisites

Once ownership is clean, the path to a durable tracking setup is clear. Before we stand up Conversions API for a client, we confirm:

• The dataset lives in the brand’s own portfolio, with token-generation access.
• The browser pixel is already firing correctly, so we can deduplicate browser and server events and avoid double-counting.
• A server-side connection exists, a store-native integration, a conversions gateway, or a server endpoint, to send events.
• Event names and parameters are mapped consistently across pixel and CAPI so attribution lines up.

None of that is possible on borrowed assets. That’s why we treat ownership as the very first step of the tracking and paid ads build, before creative, before budget, before a single campaign launches. Get it wrong and everything downstream is built on land you don’t own.

PBL found out too late, and it’s costing them real sales to fix. If you’re not certain who owns your pixel and page, that uncertainty is the answer, and it’s worth a look now, not after you’ve scaled spend on top of it. Talk to us and we’ll audit your Business Manager and make sure your data is, and stays, yours.