CRM for an advertising or digital marketing agency, where the client boundary is the whole design problem
An agency runs two pipelines and many client accounts at once. What that does to the CRM choice, and the Google manager account and Analytics limits, read on 22 October 2026, that set the boundaries.
Published by AI Knows Us · Updated 22 October 2026
An agency CRM has to hold two unrelated pipelines and keep them apart. One is the agency's own new business. The other is the work and the contacts inside each client account. Buying one system and using it for both is the mistake that makes agency CRM projects fail, because the two pipelines have different owners, different retention needs and different confidentiality rules.
The two pipelines, and why they do not merge
| Agency new business | Client delivery | |
|---|---|---|
| Record | A prospective client company | A client's own customers or leads |
| Owner | The agency principal or new business lead | The account team, and often the client |
| Confidentiality | Internal | The client's data, held under a contract |
| What happens at the end of the relationship | Nothing | It has to be handed back or deleted, cleanly |
That last row is the one that decides the architecture. If client leads sit in the agency's own CRM with no separation, the day a client leaves becomes an extraction project and a contractual argument. Design for the exit on day one and the rest gets easier.
What the platforms already give you, and what they do not
Google has built the separation you need on the advertising side. Its manager account documentation, read on 22 October 2026, opens: "If you're an agency or someone who manages multiple Google Ads accounts, a manager account is a tool that" lets you work across them from one login. The practical rule follows from that: each client keeps their own Google Ads account, linked to your manager account, so access can be granted and withdrawn without moving data.
Bulk editing has the same shape. Google Ads Editor's documentation, read on 22 October 2026, describes exporting "your entire account, your current view (such as advanced search results), a single campaign or ad group, or specific campaigns and ad groups you select" to CSV, importing a CSV to apply changes, and a "Make changes to multiple accounts" path. It also carries a warning worth repeating to any new starter: select "Include original columns in CSV/ZIP exports" under export settings if you want to keep performance history for prior items when you edit a CSV.
Analytics is where the boundary is least forgiving. Google's event collection limits page, read on 22 October 2026, states the limits "apply on a per-property basis", and that some can be raised by upgrading the property to Google Analytics 360 but not the event and parameter character limits. One property per client, owned by the client, is therefore both the clean contractual answer and the one that does not have you sharing a ceiling between two unrelated businesses.
What the agency CRM has to do that a generic one does not
Five things, in order of how often they are missed. Hold a client as an organisation with a contract, a renewal date and a named day to day contact. Hold the scope, so somebody can answer "is this in the retainer" without reading a PDF. Separate client data by client, with access granted per account team rather than per role. Record every access you hold on a client's behalf, which is the list you will need on the day the relationship ends. And track the agency's own pipeline in a place the account teams cannot see, because win probability on a pitch is not information to leave lying around.
The access register is the one worth building first. For each client, list every platform you hold access to, the kind of access, the person who holds it and the date it was granted. When a contract ends you work down that list. Without it, the handover is a series of discoveries.
Buying order, and one thing to refuse
Start with the client and contract records, because they are what the whole agency asks about daily. Then the access register. Then the agency's own new business pipeline, which is small and does not need much. Then client lead capture, and only for the clients who want you to run it. Refuse any arrangement where client leads land in a shared pool with no per client separation, however convenient it looks in month one.
For how the agency's own fee and scope decisions interact with this, see our guide to what an AdWords management agency is selling and the clauses to settle, and for the supplier side of capacity, white label PPC services compared on what each provider publishes.
A figure that does not exist: there is no published benchmark for how many agencies hold platform access they have never audited. We could not find one to cite. Count your own and record it with the date.
We sell the thing this page measures, so the disclosure belongs here rather than at the bottom. AI Knows Us reads five AI surfaces and reports whether a business is named and whether its own pages are cited, as two separate findings. Our own result on 22 October 2026 was named 0 and cited 0 across 635 readings, which is in our own published null result. Where a rival is stronger, say so plainly: Profound publishes SSO and SAML, SOC 2 and up to nine engines, and our rendered pricing page carries none of those words and five surfaces, not nine. Our cheapest plan that reads all five surfaces is Growth at 299 dollars a month in the US and the UK; the 149 dollar SEO Start plan reads 0 questions, 0 credits and 0 engines, so it is not an AI visibility plan.
Questions agency owners ask about CRM
Should client leads live in our CRM or the client's
The client's, wherever possible, with your team given access to it. The data is theirs, and the exit is clean. Where you must hold it, hold it in a separate space per client with its own access list.
Do we need a separate tool for new business
Not necessarily, but you do need a separate space. The pitch pipeline should not be visible to people who sit in client meetings every day.
Who should own the Google Ads account
The client, linked to your manager account. Google's own documentation frames manager accounts as the way an agency works across multiple accounts, which is exactly the separation a clean handover needs.
What belongs in the handover pack
The access register, the account and property IDs, the exported campaign structure, the contract and the scope, and the last reporting period with its denominators printed.
When can we judge whether the agency CRM is earning its place
Judge it on measurements: the share of clients with a complete access register, the share of enquiries that became a record with a source, the number of scope questions answered without opening a PDF, and pitch conversion with the count of pitches beside it.
The question a client will ask you next
Clients have started asking agencies what an assistant says when a buyer asks for a supplier in their category. It is a different measurement from rankings or traffic, it is taken on a recorded question set, and citation and naming are two separate findings that must never be added.