Managed Whop and Meta
One managed provider account, isolated advertiser resources.
Operating model
MarketingRouter operates the Whop business account and manages Meta advertising on behalf of owners. Owners do not supply their own Whop API keys. The operator explicitly assigns each owner a Facebook Page, approved destination origin, spending allowance, and enabled state. The owner separately consents to managed advertising.
Only the operator can initiate Meta connection through Whop or assign advertiser resources. Customer APIs expose only their assigned resources. Creatives, campaign IDs, payments, and conversion observations are bound to the authenticated owner.
Provider contract
The adapter pins Api-Version-Date: 2026-09-29. Whop's current business identifier is account_id with a biz_ prefix. Provider monetary units differ from this API: campaign/event budgets use dollars, and payment money objects carry decimal strings. Server adapters handle those conversions; agents always send integer cents to MarketingRouter.
Provider drafts explicitly use draft status. After owner approval, the service verifies the remote hierarchy and submits activation. Read delivery_status and issues to distinguish configuration from actual delivery. Whop and Meta may reject or delay an ad.
Operator readiness
Before enabling paid launch, configure ad permissions, connect the correct Facebook assets, validate pixel events, set up a Whop advertising payment method, verify customer funding and allowance, and run a bounded approved pilot. Confirm the managed advertising arrangement with Whop. Capability discovery reports the deployment gate; an enabled deployment still requires per-advertiser checks.
The service currently offers Meta only. There is no automatic channel routing, creative generation, page crawling, budget scaling, or autonomous optimization. Whop's provider sandbox is separate from MarketingRouter's local sandbox mode.