Cloaking X for Agencies — Multi-Client Streams
Running cloaking for more than one client means isolating each client's streams, staying compliant with each platform's review process per campaign, and not letting one client's traffic or settings bleed into another's. The Agency plan is built around exactly that: 30 concurrent streams, 10 team seats, and full API/MCP access for managing campaigns programmatically across clients.
What Changes When You're Running Cloaking for Multiple Clients
Every client campaign needs its own stream — its own money page(s), fallback page, delivery mode, and filtering thresholds — since a shared stream would apply one client's settings (or, worse, one client's blacklist/whitelist) to another client's traffic. Concurrent stream count becomes the real ceiling on how many client campaigns you can run at once, not click volume.
A media-buying team also needs more than one person with access, at different permission levels — a team member should be able to check Live/Reports on a client's stream without necessarily being able to change its filtering settings or billing.
How the Agency Plan Is Built for This
30 concurrent streams and 100 money pages on the Agency plan give enough headroom to run a genuinely separate stream per client/campaign rather than sharing configuration across clients, with 200,000 monthly clicks and 180 days of history to report back to each client from actual data.
10 team seats let more than one person work across client streams, with each member's own role — including read-only — enforced consistently everywhere: on the dashboard, and for any API key or MCP integration a team member issues, which can never exceed their own account permissions.
30 Concurrent Streams
Run each client's campaign on its own isolated stream — money pages, fallback page, and filtering thresholds never bleed between clients.
10 Team Seats, Role-Enforced
Add media buyers at the permission level that fits — a read-only member's own API keys and MCP integrations can't exceed that role either.
API & MCP Access
Manage streams and pull reports programmatically, or connect an MCP-compatible AI client — both included on Agency.
Unlimited Fallback Page Generator
Generate a distinct, on-brand fallback page per client campaign without hand-building one for every stream.
Setting Up Multi-Client Cloaking in 3 Steps
- 1
Create one stream per client campaign
Keep each client's money pages, fallback page, and filtering thresholds isolated from every other client.
- 2
Add your team
Invite media buyers at the seat/permission level that fits — up to 10 seats on Agency.
- 3
Automate with the API or MCP server
Pull stream-level reporting into your own client dashboards, or manage streams from an AI client via the MCP server.
Related Documentation
Start Free — No Time Limit
One stream, 300 clicks/day, every delivery mode and detection layer included — see how Multi-Client Cloaking looks on a real stream before committing to a paid plan.