For Agencies

How Agencies and Clients Are Structured#Link to How Agencies and Clients Are Structured

Each client is its own organization. The agency is a parent organization linked to those client orgs through a parent/child relationship.

A few terms worth keeping straight: a client org and a sub-account are not the same thing. In The Ad Spend, a sub-account is a connected ad platform account (like a Google Ads or Meta account) living inside one org. A client org is a fully separate organization. The agency sits above client orgs, not inside them.

Adding a Client#Link to Adding a Client

Both options are available from the Agency dashboard:

• Create Organization spins up a brand-new client org already linked to your agency.
• New Request links an existing org into your agency. If you're an admin or owner of that org, it links immediately. Otherwise it goes to the client org as a pending request they need to accept.

Removing a client#Link to Removing a client

An agency can disconnect a client org from the Agency dashboard. You confirm by typing the client's name. A client org can also reject a pending request or be disconnected on their end.

When the link ends, the client's data stops being visible to the agency immediately. The data stays with the client's own org; the agency simply loses access to it.

Team Access to Clients#Link to Team Access to Clients

Agency members can be given automatic access to a client org through virtual members. The client org controls whether this is allowed, and can turn it off from their own Team settings.

The Agency Dashboard#Link to The Agency Dashboard

The Agency dashboard shows all managed clients as cards in a single view, each displaying that client's ad metrics for a selected date range. You can switch directly into any individual client to work inside their account.

There's also a cross-client trends feed that surfaces recent trends from across your clients in one place, ordered most-recent first, one per client.

Client Reports#Link to Client Reports

Reports can be sent to a client contact who doesn't have an Ad Spend account. Delivery goes to whatever destinations are configured for that report (email or Slack). Report cadence is set per report, so different clients can be on different schedules.

Route a client's notifications#Link to Route a client's notifications

Switch into the client organization you want to configure before reviewing its delivery settings. Keep each client's default channel and individual notification destinations with that client's organization.

1. 1.In Settings → Notifications, review the client's default Slack channel.
2. 2.Open the alert or report whose delivery you want to configure, and review its destinations or recipients.
3. 3.Check alert frequency and report schedules separately so each reaches the team on the cadence intended for that client.

See Notifications & Slack for connection and routing guidance. If a report does not reach a channel, check the completed report in the app and review the channel's access before the next delivery.