Agency Ad Account vs Aged Facebook Account: Compliance, Ownership, Risk, and Spend Limits

What an agency ad account is

An agency ad account is an ad account that lives inside a certified partner's business portfolio (formerly Business Manager) and is made available to advertisers through a formal agency relationship. This is not a marketing invention — Meta's own Business Management APIs define an agency as "a type of business entity that can manage or access assets owned by another business," and Meta's API explicitly records whether a business acts as an OWNER or an AGENCY of each ad account.

In practice, the structure works like this:

• The partner holds the platform relationship. The ad account sits in the partner's business infrastructure, and Meta's API supports formally declaring the agency relationship on the account via the agency_client_declaration field.
• You get task-based access. Meta's permission model assigns tasks such as Advertiser (ADVERTISE, ANALYZE) or Admin (MANAGE, ADVERTISE, ANALYZE) on the ad account, so you run campaigns without holding title to the underlying entity.
• Billing runs through documented partner mechanisms. Meta's 2-tier Business Manager model lets a parent business share its line of credit with child Business Managers and assign spend limits to each one.

Practitioner providers such as AdsInfra describe agency accounts as provisioned through official platform partner programs, with elevated trust signals and direct escalation channels. Those performance characteristics are provider-reported rather than Meta-documented, so treat them as claims to verify with any provider you evaluate.

What matters for this comparison: an agency ad account is a structure Meta's APIs and help center explicitly document. That is the baseline difference from an aged account.

What an aged Facebook account is

An aged Facebook account is not a Meta product category. It is a gray-market term for an older personal Facebook profile — often with an attached ad account, spending history, and sometimes a Business Manager — that is sold or rented to advertisers who want an account with "history" instead of starting fresh.

Meta's documentation does not recognize buying, selling, or renting personal accounts as a legitimate arrangement, and no official source describes a sanctioned transfer mechanism. What Meta's documentation does say is directly relevant:

• Meta warns that if a business "creates a fake Facebook user and allows multiple employees to login using that user, Facebook might identify that user as a spam user and suspend it." A purchased profile operated by someone other than the original person fits this pattern closely.
• Meta explicitly states that storing end customer passwords "is not an approved model" — and credential handover is the core mechanic of the aged-account market.
• Meta's Ad Account API tracks account age ("Amount of time the ad account has been open, in days"), and its documented disable reasons include GRAY_ACCOUNT_SHUT_DOWN, MISREPRESENTED_AD_ACCOUNT, and COMPROMISED_AD_ACCOUNT — categories that map directly onto the risks of operating an account registered to someone else.
• Meta's API also notes that personal accounts with no history of activity are not eligible for migration into a Business Manager, which shows Meta evaluates account history on its own terms rather than honoring purchased history.

Important uncertainty: Meta does not publish how account age weighs in its enforcement or trust systems, and it documents no outcome guarantees for aged accounts. Any claim that an aged account is "pre-trusted" or "ban-proof" is a seller claim, not a Meta-documented fact.

Compliance and platform-policy risk

Meta's enforcement applies to every account type. According to Meta's Business Help Center, when advertisers go against its policies and standards, or Meta "observes any unusual or high-risk activity," it may place restrictions that include:

• Limits on the amount an advertiser can spend per day, or a lower payment threshold
• Loss of access to some payment features
• Loss of access to some advertising features
• Loss of the ability to advertise on Meta platforms entirely

Restrictions also operate at different levels, and it helps to separate them:

• Person: Meta can suspend individual users — its docs note fake or shared users may be identified as spam and suspended.
• Ad account: the API's account_status field includes DISABLED, with disable reasons ranging from ADS_INTEGRITY_POLICY to MISREPRESENTED_AD_ACCOUNT and COMPROMISED_AD_ACCOUNT.
• Page: Meta enforces per-Page ad limits; when a Page is at its limit, new ads do not publish and existing ads can only be paused or archived.
• Business portfolio: Meta can restrict an entire business, and one documented disable reason (BUSINESS_MANAGER_INTEGRITY_POLICY) operates at this level.

For aged accounts, the exposure is compounded: the account's history belongs to someone else, the login pattern changes abruptly at handover, and the underlying profile may be misrepresented — all signals Meta's systems can treat as high-risk. If the account is disabled, Meta's documented path is a review request through Business Support Home, and Meta does not publish review timelines or outcome rates.

Agency accounts are not exempt. Meta's 2-tier documentation explicitly references notifications "when an ad Account has been blocked due to policy violation," confirming partner accounts still face enforcement. The difference is structural: a policy-compliant advertiser in an agency structure operates inside a documented relationship, while an aged-account operator carries an extra layer of identity and integrity risk before a single ad is reviewed. All advertising remains subject to Meta's Self-Serve Ad Terms regardless of account type.

Ownership, access, and portability

Ownership is where the two options diverge most sharply.

Agency ad account:

• Ownership stays with the partner's business. Meta's API marks the partner as OWNER or AGENCY of the account, and you receive task-based permissions (analyst, advertiser, or admin tasks) rather than title to the account.
• Access is formal and revocable in both directions. Meta documents that a business with AGENCY access can remove the ad account, while accounts a business owns with CONFIRMED status cannot be removed. Claiming an account into a Business Manager is a one-time procedure — once claimed, it can only be managed in that Business Manager.
• Billing uses documented mechanisms. A partner can share its line of credit, designate a shared legal entity as the bill-to party for monthly invoicing, or grant credit-line access — which Meta notes is "especially useful for agencies or partners managing ads."
• Portability is limited by Meta itself: "once an ad account is created in your business portfolio, it can't be transferred to a business portfolio of another business." Plan for this in your offboarding terms — ask any provider how pixels, audiences, and campaign data are handled at exit. Practitioner guidance from AdsInfra recommends owning your pixel in your own Business Manager and sharing it into the agency account so your first-party data stays with you.
• Once an ad account sits in a business portfolio, permissions are managed from Settings in Meta Business Suite, not from Ads Manager.

Aged Facebook account:

• "Ownership" is possession of login credentials. The profile remains registered to another person, who may be able to reclaim it, and there is no Meta-documented process for transferring a personal account to you.
• Access is fragile: the seller, the original owner, or anyone holding recovery details can re-enter the account, and Meta can suspend the underlying user.
• Billing typically means attaching your payment method to someone else's account, or trusting a prepaid balance you do not control.
• Offboarding effectively does not exist: if the account is disabled or reclaimed, Meta's documented recovery and review paths are built for the account's real owner, not a purchaser.

Spend limits and support

Spend limits:

• Meta documents hard structural limits: a maximum of 25 ad accounts per person and 25 people with access per ad account, plus per-account caps on active ads, ad sets, and campaigns.
• Meta can impose spend-based restrictions as an enforcement outcome — its restrictions documentation lists "limits on the amount an advertiser can spend per day or a lower payment threshold."
• Every ad account has a spend_cap field; when the cap is reached, all delivery stops.
• Meta's API can block new ad account creation when a Business Manager has accounts "in bad standing or in review," requiring all accounts to be in good standing first.
• In the documented agency model, a parent Business Manager can share its line of credit with child Business Managers and assign a spend limit to each — a sanctioned way to govern spend across many accounts.

Practitioner providers report that agency accounts carry higher or negotiated spend ceilings and faster ramp tolerance. Meta does not publish these thresholds, so treat specific numbers as provider claims to verify — and be skeptical of any provider claiming an account is exempt from spend caps or enforcement review.

Support:

• The standard, Meta-documented path for any disabled or restricted account is Business Support Home: select the restricted account under Account status overview and choose Request review.
• Meta does not document support response times or review timelines for either account type — any provider promising fixed resolution windows is going beyond what Meta states.
• Meta's 2-tier documentation does give partner businesses "actionable notifications for critical errors when an ad Account has been blocked due to policy violation," and practitioner sources describe dedicated escalation channels through partner programs. For aged accounts, there is no equivalent documented support relationship — you are an anonymous operator on someone else's profile, in a standard queue, with a review process designed for the account's real owner.

Which option is safer for high-spend operators

For high-spend operators, the agency ad account is the safer option on every dimension Meta actually documents:

• Structure: agency access is a first-class relationship in Meta's APIs — OWNER vs AGENCY access types, the agency_client_declaration field, and the 2-tier Business Manager model. Aged accounts have no documented existence at all.
• Enforcement exposure: both account types face identical advertising-policy enforcement, but aged accounts add person-level and integrity-level risk — shared or fake users can be suspended, and misrepresented or compromised accounts have their own documented disable reasons.
• Continuity: agency arrangements can be governed by contract, with documented billing mechanisms and defined, revocable access. Aged accounts can be reclaimed by their original owner or disabled with no documented recourse for a purchaser.
• Scalability: the documented agency model is built for scale — shared credit lines, per-child spend limits, consolidated invoicing — while aged accounts "scale" by multiplying the number of at-risk identities your spend depends on.

Two cautions before you act. First, "safer" is not "safe": Meta restricts accounts for policy violations and high-risk activity regardless of structure, review outcomes depend on Meta's process, and no provider can promise immunity from enforcement or exemption from spend limits. Second, provider quality varies — verify current partner certification, ask how offboarding and data ownership are handled, and get support commitments in writing before moving meaningful spend.

If you are weighing these options because of past restrictions or because you are scaling, the evidence points one way: build on infrastructure Meta documents, not on accounts Meta can treat as someone else's.