An agency running Meta for twelve clients usually has twelve ad accounts, twelve tracking setups and twelve sets of numbers that cannot be compared, because each was configured slightly differently by a different person at a different time.
DropCPL is multi-tenant by design. One agency account holds a subaccount per client, and every subaccount runs the same measurement model.
What is separated
| Scope | |
|---|---|
| Landing pages | per subaccount |
| Tracking domains | per subaccount |
| Meta connection and ad accounts | per subaccount |
| Leads, clicks and spend | per subaccount |
| Membership and access | per subaccount |
Nothing crosses between clients: not identifiers, not pages, not data. A tracking problem on one client cannot contaminate another client’s numbers.
What is shared
- The measurement model. Every subaccount attributes leads the same way — same click identifier, same attribution window, same deduplication. That is what makes a CPL from client A comparable with a CPL from client B, which is the only reason cross-client reporting is worth anything.
- The interface. One login, a subaccount switcher, and the same vocabulary everywhere.
Why this matters more than it sounds
Most reporting problems at agencies are not analysis problems. They are consistency problems: two clients with the same real performance show different numbers because someone installed the pixel differently in March. Fixing the model per account is the only way to make the comparison meaningful.
Related
- Creative attribution — what each subaccount measures
- Lead routing — where the leads go, per client