How many roles does a small team actually need?

Usually three levels — CEO, lead, and buyers — are enough; extra intermediate roles mostly just complicate access management.

How do you avoid losing the whole domain pool to one buyer's ban?

Assign domains to a specific buyer or offer and rotate them individually, instead of running one shared pool with no isolation.

Is a shared postback template worth it if buyers run different offers?

Yes — a shared S2S format makes it possible to compare buyer performance and removes the need for separate manual analytics per buyer.

What happens to a buyer's campaigns when they leave the team?

Access is revoked immediately, while domains, stats, and campaign history stay in the team account instead of disappearing with the person.

PWA Team Setup

A PWA team setup isn't solved by any one buyer — it's a process, and access, domains, and reporting need to work the same way for everyone on the team. Without clear role separation, growth turns fast into shared passwords and a mess of spreadsheets. Here's what an actually scalable setup is built from.

Default roles and access levels

In APEX, the working split is: a CEO sees everything, including billing and team-wide stats; a lead manages a group of buyers, their domains, and their budgets; a buyer only works their own campaigns and domains, with no visibility into anyone else's budget or the account's billing. This isn't about distrust — it's protection against a single point of failure, where one compromised or departing account can't touch anyone else.

Domains belong to the team, not the person

The right model is a shared, rotating domain pool where each domain is assigned to a specific buyer or offer, not handed out blind. When one domain gets banned, that isolation keeps the damage from spreading into other buyers' campaigns. One-click rotation keeps ban downtime measured in minutes, not hours of manual reconfiguration.

Shared stats instead of scattered spreadsheets

Leads and the CEO need an aggregated view — installs, CPI trend, push CTR, postback-confirmed deposits — across every buyer at once, not a dozen personal exports. That's the only way budget gets reallocated between buyers and offers based on data instead of gut feel.

One postback standard for the whole team

When every buyer wires up S2S their own way, comparing results across them becomes nearly impossible — data arrives in different shapes with different lag. One shared Keitaro↔FB CAPI schema across the team fixes that: conversion events look the same no matter who ran the campaign, and analytics stops being separate manual work per buyer.

Onboarding and offboarding without risking the domain pool

A new buyer gets access to their own domains and campaigns only, with no visibility into anyone else's budget. When a buyer leaves, access is revoked instantly, while domains, stats, and campaign history stay with the team account rather than tied to a personal account that no longer works with you.

FAQ

How many roles does a small team actually need?: Usually three levels — CEO, lead, and buyers — are enough; extra intermediate roles mostly just complicate access management.
How do you avoid losing the whole domain pool to one buyer's ban?: Assign domains to a specific buyer or offer and rotate them individually, instead of running one shared pool with no isolation.
Is a shared postback template worth it if buyers run different offers?: Yes — a shared S2S format makes it possible to compare buyer performance and removes the need for separate manual analytics per buyer.
What happens to a buyer's campaigns when they leave the team?: Access is revoked immediately, while domains, stats, and campaign history stay in the team account instead of disappearing with the person.

Build your PWA in APEX in minutes

Cloaking, anti-bot, push, split tests and your own domains — in one service.

Get started free