Meta Ads · Cloaked W2A
Meta Ads Architecture — Manufacture & Replace
Ad accounts and landing domains are consumables; the pixel, the pixel-holding BM, and the customer DB are not. Operating metric: profit-per-burn. Scale is set by replacement velocity, not ban avoidance.
Status: designed, not executed · cloaker layer unscreened · profit-per-burn unmeasured
1Layers
Permanent · off-Meta
Customer DB / cashflow / LTV
Web checkout + own user tables. Source of truth; never touches Meta.
▲ protect · burn ▼
Protected
Pixel / dataset
One per vertical. Fed by CAPI. Never bound to a burnable domain.
·
Protected
Business Manager (pixel-holder)
Never advertises. No payment method. Dedicated identity.
·
Disposable · churn
Ad accounts
Bought or rented. Replaced under the BM.
·
Burn on rotation
Landing pages / domains
Cloaked. Rotated. Absorbs the blacklist so the layers above stay clean.
2Data spine
- One protected BM per vertical holds the pixel. It runs no ads and carries no payment method.
- Conversions reach the pixel server-side via CAPI (dataset ID + token) from the funnel server, keyed by click ID; browser pixel is secondary.
- Pixel is shared to disposable ad accounts via Assign Partner for optimization. Audiences and lookalikes are built and held in the protected BM, shared downward.
- Domains are never verified to the protected BM. Where AEM is required for web-conversion optimization, verify the burnable domain to a throwaway BM instead.
- Reseed of last resort: upload the customer list as a Custom Audience onto a fresh dataset.
3Domain / cloak layer
- Landing domains are bulk-registered, paired to the cloaker, rotated on burn.
- Cloak serves a self-consistent white page to review/crawler traffic and the offer to real users. The white page is crawled directly and must stand on its own.
- The money / brand domain never appears in an ad. Ads point only at burnable bridge domains.
⛔Cloak detection is terminal
A caught cloak reads as intent to deceive — it kills the ad account/BM it ran under and blacklists the domain. Isolation contains that blast; it does not prevent it. Cloaker quality is the load-bearing dependency of the whole model.
4Isolation
A burn at the domain or account layer must not reach the pixel, BM, or customer DB.
- Pixel-holding BM: no ads, no payment method, dedicated admin identity that touches nothing else.
- One antidetect profile per account, unique fingerprint, one account per profile.
- One residential/mobile proxy per profile, geo-matched; never shared across layers.
- Authenticator-app 2FA; no shared phone number.
- No payment instrument reused across BMs, including virtual cards.
- Burnable domains unverified to the protected BM.
Risk-graph edges — what makes a burn cascade:
| Edge | Weight | |
|---|
| BM membership | permanent | Everything in one BM is one node; dies together. |
| Payment method | permanent | One card across two BMs binds them; a reused virtual card is enough. |
| Admin identity | hard | Same human admin across BMs = bound. |
| Browser fingerprint | strong | One fingerprint across many BMs auto-flags as coordinated. |
| IP cluster | monitored | Accounts sharing an IP get clustered. |
| Assign-Partner pixel share | weak | Legitimate B2B edge; does not drag the protected layer. |
5Capacity — buy vs rent
Buy (own)
- Own the account; attach the pixel directly, no permission.
- Carry the ban yourself; cheaper per unit.
- Warm only what you keep.
Rent (agency, 4–15% of spend)
- Agency owns and replaces the account; no warming.
- No privacy — they see the creatives, often pre-moderate.
- Pixel attach needs their cooperation; CAPI captures the data regardless.
Protected BM is always self-built, never bought. Vendors, prices, reputation → market_refresh_2026-06-14.md
6Warming
- Disposable accounts: geo-matched cage, no bulk day-one edits, spend ramp over 2–3 days, then extract. Not warmed beyond survival-to-first-dollar.
- Protected BM & retained assets: aged, clean, full discipline.
- Each replacement account restarts the ad-set learning phase; the per-burn re-ramp is a line item in profit-per-burn.
7Economics
◎Profit-per-burn is the scoreboard
Positive with fast payback → scale by replacement. Negative → a money incinerator that loses slower.
profit_per_burn = revenue_before_death − (account + domain + cloak + proxy + spend_burned)
Single points of failure are the supply chain, not the assets: funding card · account supplier · cloaker subscription · registrar. Redundancy goes there — a frozen card or a dead cloaker stops the whole factory.
8Open
- Cloaker — unscreened; the load-bearing dependency. Detection resistance, price, domain-swap speed, verification interaction.
- AEM vs arm's-length domain verification — unresolved.
- W2A payment placement — web checkout vs bridge-to-IAP; determines whether the domain carries money flow.
- Profit-per-burn — unmeasured; the first small run exists to measure it.
- CAPIG-MA — official multi-account gateway (~$350–500/mo / 50 accounts); cleaner path for lower-risk verticals.
- TikTok mirror — via Business Center asset sharing.