What an agency ad account is
An agency ad account is a standard Meta ad account that sits inside an agency's Business Manager (business portfolio) instead of yours. Meta's own Business Management APIs describe the model directly: a business can own assets or access them as an agency, and Meta defines an agency as a business entity that manages or accesses assets owned by another business [exa-efd394bc62d6f373]. The relationship is explicit in Meta's systems — the Ad Accounts API records whether your business is acting as an OWNER or an AGENCY of a given ad account [exa-cbba3e71ded57973].
In the provider market, 'agency ad account' usually means the agency or infrastructure provider owns the ad account inside its Business Manager and grants you advertiser- or admin-level task access so you can run campaigns day to day [exa-ddc15e9c547f4020]. Billing typically runs through the agency's payment method or line of credit. Meta documents this pattern at scale in its 2-tier Business Manager solution, where a parent Business Manager can share its line of credit with child Business Managers and assign spend limits to them [exa-8061133f8fc0ba1a].
Two things follow from the structure:
- You operate the account, but you do not own it. Your access is a set of assigned tasks (ANALYZE; ADVERTISE; MANAGE), not ownership [exa-efd394bc62d6f373]. - The arrangement is visible to Meta. Agency access is a documented, API-level relationship — not a workaround.
What an aged Facebook account is
An 'aged' Facebook account is a secondhand asset: a personal profile, Business Manager, or ad account that someone else created, accumulated history on, and now sells or hands over to you. Marketplace estimates put one-time costs around $150–$900 for basic purchased accounts and $300–$1,200 or more for aged assets with stronger history, though practitioners stress these are rough working estimates, not benchmarks [exa-3c38eb1f73390399].
The sales pitch is that age implies trust: prior payment activity, a longer existence window, and less abrupt creation history. Practitioner analysis cautions that age is a context signal, not a performance guarantee — it does not prove your offer, landing page, or creative is compliant, and it does not prove the account's history is clean [exa-3c38eb1f73390399].
Critically, Meta has no official 'buy an account' pathway. Meta's documented flows cover claiming an ad account you already administer into a Business Manager you admin — a one-time procedure — and requesting agency access to assets owned by other businesses [exa-cbba3e71ded57973]. Practitioner reviews of Meta's Commercial Terms note they prohibit selling, transferring, or sublicensing ad accounts without authorization [exa-ddc15e9c547f4020]. And despite seller language about 'trust scores,' Meta has never published such a metric [exa-ddc15e9c547f4020].
Compliance and platform-policy risk
The compliance gap between the two options is structural.
Agency ad accounts run on a model Meta documents: business-to-business access requests, permitted tasks, and agency relationships are first-class API concepts [exa-acdb36d3956646f7]. That does not make them immune — Meta's Advertising Standards still apply to every ad, and no account type bypasses policy review [exa-ddc15e9c547f4020].
Aged accounts usually depend on credential transfer: the seller hands over login details for a profile or Business Manager you did not create. Meta's own best-practices documentation is blunt about this pattern. Storing or using customer passwords 'is not an approved model,' and Meta warns that if a fake or shared Facebook user is created and multiple people log in with it, 'Facebook might identify that user as a spam user and suspend it' [exa-2013d5c682a9083c]. That is direct restriction evidence against the aged-account operating model.
Restriction risk also differs by asset level, and it is worth separating four things sellers often blur:
- Person-level restrictions: the profile behind the account can be suspended — the exact failure mode Meta flags for shared or fake users [exa-2013d5c682a9083c]. - Ad-account-level restrictions: delivery stops on that account; Meta documents enforcement and spending-limit pauses at this level [exa-be9352bba54ef2e6]. - Page-level restrictions: Pages are separate assets with their own access and task model [exa-efd394bc62d6f373]. - Business-portfolio-level restrictions: the most severe for rented infrastructure — practitioner guidance warns that if the agency's whole Business Manager gets restricted, every account inside it goes with it [exa-ddc15e9c547f4020].
Neither option removes enforcement risk. The question is whether the structure adds avoidable risk — credential sharing, unknown history, no recourse — on top of the policy risk every advertiser carries.
Ownership, access, and portability
Ownership is where the two options diverge most sharply.
With an agency ad account, the agency is the OWNER and your business holds AGENCY access with defined permitted tasks. Meta's API enforces the hierarchy: you cannot grant access to assets you only have AGENCY access to — only the owner can [exa-acdb36d3956646f7]. Granting agency access can also trigger a security review by another business admin before it completes [exa-acdb36d3956646f7]. If the ad account sits in a business portfolio, permissions are managed from Meta Business Suite settings rather than Ads Manager [exa-7abd099fb7e67789].
Portability is limited by design, and this cuts both ways:
- Claiming an ad account into a Business Manager is a one-time procedure; once claimed, it can only be managed in that Business Manager [exa-cbba3e71ded57973]. - An OWNER cannot remove a CONFIRMED ad account from their business [exa-cbba3e71ded57973]. - Meta states that once an ad account is created in your business portfolio, it cannot be transferred to another business's portfolio [exa-23695ca236044f65].
So with an agency account, assume the account itself stays with the provider. What you can protect is everything around it: your pixel, audiences, Page, and creative. Practitioner guidance is consistent — keep your pixel and Conversions API dataset in your own Business Manager, since your pixel and CAPI dataset belong to your BM, not the agency's, and get exit terms such as a wind-down window and balance handling in writing before you fund the account [exa-ddc15e9c547f4020].
With an aged account, 'ownership' is nominal. You hold credentials, but the original owner may retain recovery paths (email, phone, ID), and there is no Meta-supported transfer to formalize the handover. Offboarding is equally murky: if the seller disappears or reclaims the profile, you have no documented recourse.
Ready to upgrade your ad account infrastructure?
AdsInfra provides certified agency accounts for Meta, TikTok, and Google. Setup in 2-5 business days.
Talk to a SpecialistSpend limits and support
What Meta officially documents about spend limits is narrower than marketplace marketing suggests:
- An ad account spending limit is a flexible lifetime cap you set yourself; when spend reaches it, ads pause and the account stops spending [exa-be9352bba54ef2e6]. - Ad account admins can set spending limits and associate business payment methods [exa-efd394bc62d6f373]. - In Meta's 2-tier Business Manager model, a parent Business Manager can share its line of credit with child Business Managers and assign spend limits to prevent overspend [exa-8061133f8fc0ba1a].
Meta does not publish fixed daily caps for new accounts, a 'trust score,' or promised thresholds for raising limits — so treat any specific number a seller quotes as their claim, not Meta's documentation. Practitioner sources report that agency accounts often come with higher initial spend capacity and faster review queues because of the agency's history, and that serious providers offer replacement service-level terms — one practitioner vetting checklist recommends a written replacement SLA of 24–48 hours [exa-ddc15e9c547f4020]. These are provider-level benefits that vary widely; get them in writing.
For aged accounts, sellers often market accounts as having no spending ceiling. Practitioners warn this should not be read as a literal promise of unrestricted delivery — real limits still come from policy review, payment trust, audience response, creative fatigue, and funnel economics [exa-3c38eb1f73390399]. Support is the bigger gap: an aged-account seller typically offers no documented escalation path, no replacement SLA, and no accountability if the account is restricted after handover. Meta does not document support response timelines for any account type, so any promised resolution speed is a provider commitment, not a platform promise.
Which option is safer for high-spend operators
For operators scaling serious spend, a verified agency ad account is generally the safer structure — with an important caveat. Practitioner analysis describes the agency model as operations-led: it can assign roles, limit credential sharing, separate clients, and preserve continuity when a media buyer leaves, which gives a team more ways to respond when something goes wrong — but it does not make the setup risk-free [exa-3c38eb1f73390399]. You are also trading some platform risk for counterparty risk: if the agency's whole Business Manager gets restricted, every account inside it goes with it [exa-ddc15e9c547f4020].
The safety case for agency infrastructure:
- The access model is documented by Meta, not improvised [exa-efd394bc62d6f373]. - Billing runs through established lines of credit rather than a stranger's payment profile [exa-8061133f8fc0ba1a]. - Serious providers offer written replacement terms — practitioner vetting checklists recommend a documented replacement SLA, typically 24–48 hours [exa-ddc15e9c547f4020].
The case against aged accounts at high spend:
- The operating model — shared or transferred credentials — is one Meta explicitly flags as suspendable [exa-2013d5c682a9083c]. - A purchased aged account with no visible history is still a risk asset; age alone tells you nothing about restriction history, prior policy strikes, or who else holds recovery access [exa-3c38eb1f73390399]. - There is no official transfer mechanism, no documented ownership, and no support path.
Whichever route you take, verify before you fund: check any claimed Meta Business Partner status in Meta's partner directory directly, ask for restriction history and billing ownership documentation, demand written replacement and exit terms, keep your pixel and Page in your own Business Manager, and run a controlled pilot before scaling [exa-ddc15e9c547f4020, exa-3c38eb1f73390399]. And be clear-eyed about the ceiling: no provider can promise immunity from Meta enforcement, and Meta does not document review timelines or outcomes in advance.