Agency Guide: Managing Meta Custom Audience Sync Across Multiple Client Ad Accounts

An agency running QR campaigns for multiple client brands out of one SMLLR account needs to know this upfront, the same way it matters for Email Marketing: Meta Sync's connection is one per SMLLR account (organization-wide), not one per client. You connect a single ad account and maintain a single Custom Audience from it, regardless of how many clients you manage inside Client Management. This isn't a configuration you're missing; it's how the feature is built, and it changes how you should scope, price, and pitch it.

If your agency manages five clients, each with their own Meta ad account, Meta Sync as it exists today can only be connected to one of those five ad accounts at a time from a single SMLLR account. There's no way to sync Client A's consented leads into Client A's ad account and Client B's into Client B's ad account simultaneously from one shared agency login — connecting a new ad account replaces which account SMLLR's Meta Sync is pointed at, it doesn't add a second parallel connection alongside the first.

Given that constraint, agencies land on one of two structures:

Client Management still does real work for a Meta Sync engagement even under a single shared connection — tagging QR codes under a specific Client record lets you filter which leads' consent is even feeding the connected audience in the first place, and branded client reporting shows scan and lead performance scoped to that client's codes. What it doesn't do is give each client their own isolated ad-account connection or their own separate Custom Audience within one shared SMLLR account — that's the same shared-infrastructure pattern as Email Marketing's single sending domain and template cap, not a gap specific to Meta Sync.

This is worth naming directly during a sales conversation rather than letting a client discover it after signing — a client asking "can you run Meta Sync for my ad account while also running it for another client under the same agency login" needs to hear, upfront, that the honest answer is either a dedicated SMLLR account for their Meta Sync work specifically, or a shared account where Meta Sync attention rotates between clients rather than running for all of them at once. Positioning this clearly protects the relationship better than a client finding out mid-engagement that "multi-client Meta Sync" meant something narrower than they assumed.

A separate SMLLR organization per client needing simultaneous Meta Sync means a separate Pro plan (₹4,999/month) or Premium (₹14,999/month) subscription per client, each with its own 100 or 300 monthly credit allowance and its own top-up packs if needed. For an agency serving a handful of clients who specifically want ongoing, always-on Meta Sync (rather than QR generation and Lead Hub alone, which can still run under one shared account), that per-client subscription cost needs to be built into what you charge for the Meta Sync service itself, not absorbed into your existing agency plan's price.

This limitation is specific to Meta Sync's ad-account connection — it doesn't affect your ability to run QR code creation, Lead Hub, Email Marketing's client-scoped campaign targeting, or Play & Win across many clients from one shared agency account, all of which work the same multi-client way Client Management is designed for. Meta Sync is the one channel among the three where the underlying third-party connection (a Meta ad account, not SMLLR's own infrastructure) forces a one-per-account limit.