Google Ads guide

How to Set Up Google Ads Audience Signals for Agencies

To set up Google Ads audience signals for an agency client, document the client’s customer goal, prepare a client-owned first-party segment, add account-specific research inputs, and attach the signal to the Performance Max asset group whose offer and landing page match. Name, permission, refresh, and review the signal so another account manager can understand it. Explain before launch that the signal guides Google AI and does not strictly fence delivery.

Google’s audience-signal guidance states that Performance Max may find converters outside supplied signals. The agency workflow should make that behavior, the data owner, and the quality threshold clear to the client.

Write the client brief before opening Google Ads

Record client, account, product or service, buyer, market, offer, campaign goal, primary conversion, later quality stage, value model, and capacity. An ecommerce account may need margin and repeat purchase; a local account may need qualified calls and completed jobs; a B2B account may need opportunity and closed-won stages. Do not assume an agency-wide template answers those questions.

Separate raw events from business outcomes. Keep signup, lead, appointment, qualified lead, purchase, activation, renewal, and revenue distinct. Write the expected lag and who at the client can approve a quality decision. If no later stage is available, label the signal a provisional learning hypothesis rather than claiming it represents the ideal customer.

Define the client boundary: locations, plans, products, service capacity, regulated claims, existing-customer policy, and markets the team can serve. This brief becomes the reason for the list and the review standard for the media team.

Prepare and protect client-owned data

Ask the client to provide approved data segments for purchasers, qualified leads, activated users, booked appointments, opportunities, or retained customers as appropriate. Keep every-signup, site-visitor, and newsletter data separate from the stronger lifecycle stages. Remove employees, partners, tests, duplicates, and contacts the client has not authorized for the campaign.

For each segment, record client, account, source, consent basis, product, market, stage, recency, owner, and refresh date. The client should confirm data rights and retention requirements; the agency should not assume that access to a CRM means permission to reuse its data for any account or campaign.

Use the client’s buying cycle to choose recency. A short list may fit urgent local work, while a longer list may fit enterprise sales or renewals. Keep separate CRM queries rather than combining them into an audience whose size looks impressive but whose intent is unclear.

Add account-specific custom segments

In the relevant Performance Max asset group, create or select an audience signal and add the client’s data. Build custom segments from the buyer’s actual problem, service, product, role, industry, location, comparison, and integration language. Use sales notes, search-term reviews, call themes, and client-approved research—not the same generic agency list in every account.

Add in-market, affinity, demographic, or other relevant segments only when they fit the account. A broad category can be useful for a new test; a specialized service may need tighter customer and page context. Name each signal with client, product, stage, recency, market, and date, such as “Northwind — SQLs 180d — analytics platform — US — Aug 2026.”

Keep a written hypothesis: what the input should teach, which asset group it supports, how long it will be reviewed, and what quality signal would justify keeping it. This turns a setup task into an account decision the client can understand.

Connect the signal and explain its reach

Choose the asset group whose creative, offer, page, price, proof, and CTA match the audience. Do not send enterprise intent to a self-serve page or local service intent to a national form. Check product availability, service area, lead routing, and client approval of claims before saving.

Google’s audience segment documentation describes data, custom, in-market, affinity, and demographic concepts. Exact options depend on campaign type and account. Add the inputs under the current Audiences panel, then save the change with a date and approver.

Tell the client that Performance Max may reach people outside the signal when Google predicts a likelihood of conversion. A signal is not an audience-only allowlist, an ICP guarantee, or a substitute for location, product, landing page, conversion, and brand controls. Record that explanation in the client notes so it is not lost during an account handoff.

Test permissions, routing, and quality

Confirm that the agency has the right account access and that client data is not visible in another account. Test the list source, recency, removal process, and refresh ownership. For lead accounts, submit a test form or call where allowed and verify consent, deduplication, CRM assignment, notification, and response. For ecommerce or SaaS, verify transaction, activation, or paid events and their identifiers.

Review performance in two layers. The agency can use common delivery metrics, but the client quality layer must match its model: margin and repeat order, activation and retention, opportunity and close, or completed local work. Wait for conversion lag and annotate changes to offer, page, CRM, sales coverage, budget, and creative. Do not change signal, bidding, targeting, and form qualification together.

Use the agency audience-signal framework for input choices and Google’s measurement guidance for reporting context. adz.so can inspect supported settings, but it does not manage client permissions, CRM quality, or the agency relationship.

Agency setup checklist

Before launch, confirm that:

  1. client goal, customer stage, value, market, and capacity are documented;
  2. data ownership, consent, retention, access, and refresh are approved;
  3. lists are isolated by client, account, product, stage, and recency;
  4. custom segments use account-specific customer language;
  5. asset group, page, offer, creative, and form agree;
  6. the client understands that audience signals guide rather than fence reach;
  7. test conversions and downstream stages are attributable; and
  8. the review owner and quality threshold are written down.

Use a consistent agency checklist for governance and account-specific reasoning for the actual audience. The client should be able to explain what the signal contains, what it is intended to teach, and what later result will determine whether it stays.