The ad account is only one asset on the list
In Meta's structure, the ad account, Page, pixel (now often called a dataset), Instagram account, domain and payment method are separate assets, each with its own owner and permission level. Admin access to the ad account does not give you the Page or the pixel. Many handovers fail because the ad account moved while the ad identity and conversion data stayed with the previous owner. The right question is not whether you received the account, but who owns each asset now and what level of access you actually hold.
The Page determines who the ads appear to come from
The name, profile image and engagement surface of an ad come from the Page, and the connected Instagram account is usually tied to it or to the same business assets. A Page can belong to a business portfolio or be held through a personal profile. If it still sits in the previous owner's portfolio and you only have a granted role, removing that access leaves your ads without a usable identity, and the Page's history is outside your control. Check three things: who owns the Page, whether you hold full control or a limited role, and whether there are at least two trusted admins to avoid a single point of failure.
The pixel determines who keeps the data and audiences
The pixel or dataset records site and app events, and conversion optimization, retargeting and lookalike audiences all depend on it. If the previous owner still owns it, you may reference it from your ad account, but the data flow stops when they stop sharing, and audiences built from it can no longer update. Creating a new pixel is possible, yet event history and audiences do not migrate, so learning starts over. Also verify any Conversions API token setup, domain verification ownership, and which pixel ID is actually embedded in the site code.
Check asset by asset and set stop conditions
For each asset in business settings, answer four questions: which portfolio or person owns it, whether you hold admin or limited access, whether it is linked correctly to the ad account, and whether the account carries any restriction or disabled status. A simple rule works: if a critical asset such as the Page, pixel or payment method cannot be fully held by your own business assets, fix that before paying or taking over, not after. If the other side can only offer personal login details instead of asset-level authorization, stop. Shared logins add security risk and often trigger unusual-login checks.
Compliance boundary: hand over through asset permissions, not shared credentials
Meta has its own terms on transferring or selling accounts and business assets, and they change, so rely on the platform's current policy pages. Legitimate handovers, such as agency to client or an internal entity change, usually go through partner sharing or permission assignment within business assets. Do not treat bypassing verification, hiding associations or using someone else's identity documents as a handover method. If detected, the whole business portfolio can be affected. Before you order or accept, make sure the ownership chain is clear and the authorization route is compliant; that matters more than the account's spend history.