How to Set Up Google Ads Audience Signals Correctly
To set up Google Ads audience signals correctly, choose the Performance Max asset group and business outcome first, verify the source and permission of each customer or visitor list, build custom segments that match the offer, add only relevant signals, and record that they guide discovery rather than restrict delivery. Then monitor qualified outcomes and refresh the signals when the product, market, or customer definition changes.
Audience signals are inputs to an automated campaign, not a promise that ads will serve only to the listed users. A careful setup therefore combines useful examples with accurate conversion tracking, clear exclusions, and a landing page that can serve users beyond the initial signal.
Choose the asset group and goal first
Before creating a signal, record the asset group’s theme, landing-page family, primary conversion, value model, market, language, and customer definition. A signal should explain why a particular group may be valuable, not serve as a generic audience bucket for the entire account.
Google’s Performance Max audience guidance describes the role of audience signals in automated campaigns. Use that context to set expectations with stakeholders: the campaign can discover valuable users beyond the signal, so a signal is not a hard targeting rule.
Decide what the signal should teach
Write a hypothesis such as:
- “Recent purchasers of this category can help the group learn which users are likely to value related products.”
- “Qualified leads for this service describe the quality we want to find.”
- “Visitors to this service page represent the problem this group solves.”
- “These current search themes describe the need behind the offer.”
If the team cannot complete that sentence, do not add the signal yet. Fix the asset-group theme or conversion definition first.
Verify customer data and permission
For every first-party list, record the owner, source, collection context, freshness date, customer stage, retention rule, and permission or consent basis. Remove employees, duplicates, spam, stale records, or users who should not be used for advertising. Do not upload data the business is not allowed to use.
Separate purchasers, qualified leads, unqualified inquiries, and existing customers when the business treats them differently. A larger list is not automatically a better signal.
Prepare custom segments that match the offer
Use custom segments to describe current search, content, app, or interest themes related to the problem the asset group solves. Keep the terms close to the product or service, and remove generic concepts that could describe unrelated users.
Review competitor, brand, sensitive, and regulated terms before using them. A custom segment is a hypothesis about useful users, not a license to make claims the business cannot support. Name the segment for its business meaning, include its source and date, and record the owner.
Test the segment against the landing page and creative. If the terms suggest a different offer, location, language, or customer stage, create a different asset group or revise the segment.
Add the signal to the correct asset group
Open the Performance Max campaign and the asset group from the theme map, then locate the audience signal section. Google can change navigation and labels, so use the current Performance Max audience instructions alongside the interface. Confirm the campaign and group before saving.
Add only the approved lists, custom segments, or other available signal types that match the hypothesis. Give the signal a descriptive name and record:
- asset group and campaign;
- data source, owner, date, and permission basis;
- customer stage or interest hypothesis;
- expected business outcome;
- review date and removal trigger.
Do not add exclusions or customer-acquisition rules as if they were audience signals. Those requirements need their own controls and should be checked separately.
Keep signals useful but not bloated
Start with the smallest set that explains the group. A signal stack with dozens of broad lists can hide which hypothesis was useful and makes governance harder. Add another source only when the group has a clear reason and the previous baseline is understood.
Verify and monitor audience signals
After saving, reopen the asset group and confirm the signal name, source, scope, and status. Check that the intended list or segment is available and that no account-level change has altered the campaign’s customer or exclusion rules.
Set a review window that accounts for audience processing and conversion lag. Compare the group before and after the signal change on:
- impressions, clicks, spend, conversions, and conversion value;
- qualified leads, pipeline, new-customer mix, margin, or capacity;
- search themes, products, devices, locations, and selected pages;
- list freshness, match-quality context, policy status, and tracking.
Because discovery can go beyond the signal, do not label all new conversions as members of the listed audience. Judge whether the signal helped the campaign find the business outcome, not whether delivery stayed inside the signal.
Refresh or remove the signal
Review lists and custom segments after a product, market, season, price, conversion, or customer-quality change. Remove data that is stale, unpermitted, duplicated, or no longer representative. If the signal’s hypothesis is disproved, change the signal or asset-group theme rather than adding more audiences to compensate.
Keep the prior signal definition and the reason for the change. That history helps separate a data-source problem from a bidding, creative, landing-page, or conversion change.
Audience signal setup checklist
Before finishing, confirm that:
- the asset group, offer, landing page, conversion, and customer definition are documented;
- first-party lists have an owner, source, freshness, and permission basis;
- custom segments match the problem and offer without generic or unapproved concepts;
- the signal is attached to the correct campaign and asset group;
- exclusions, customer-acquisition goals, and hard targeting rules are configured separately;
- the signal name, hypothesis, date, expected outcome, and review trigger are recorded;
- conversion tracking and business-quality measures are reliable;
- the post-save review accounts for discovery beyond the signal and conversion lag;
- stale or disproven sources have a removal or refresh process.
For the policy behind these steps, see the best Google Ads audience signal settings guide. The adz.so product overview describes the current audit entry point; it does not imply that adz.so adds or manages audience signals in Google Ads.