Connect Ad audience signals
Expose audience labels to the Google tag or tag manager already on your page.
All connectors · Checked against AXO’s implementation in October 2026.
Prepare access
Use an owner or admin account in AXO and confirm the selected site. Have permission to authorize the external account or create its server credentials. Keep secrets in the connector’s protected configuration.
| Setting | Value to prepare |
|---|---|
event_name | Event name; defaults to axo_signal. |
rules | One rule per line: parameter=value: segment, segment. |
Connect
Open Integrations, find Ad audience signals, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Enter a rule such as audience=nurture: deliberator, comparison_shopper.
- Configure your existing Google tag or GTM container to consume the event and parameter.
- For GA4 audiences, register the parameter as a custom dimension before building an audience.
Verify the result
There is no server delivery test. Verify the event and parameter in your tag-management preview and then in the receiving platform.
Record the AXO integration or trigger result and the receiving system’s result. A saved configuration, credential check, and completed delivery establish different things. Use a controlled destination for a test that writes data or sends a message.
Fix a failed connection
This connector emits browser labels; it does not create provider audiences or campaign exclusions for you. Check the downstream rule and consent settings.
For a saved catalog connector, open Health to read the latest error, then repair the settings through the setup method on this page. Pause delivery while correcting an unintended destination. Reconnect OAuth when its grant is revoked; for key-based connections, save the replacement key, verify it, then revoke the old key at the provider.
Next: create an event-triggered action, or implement a webhook receiver.