Skip to main content

Configure ATS.js for Agentic Audiences

The Agentic Audiences integration allows ATS.js to collect publisher-provided context and turn it into an audience signal for automated bidding. Agentic Audiences lets a publisher share approved context, such as page type, content category, topic, or declared user journey stage, and have that context converted into a standardized user-context embedding.

The embedding is stored in the browser and made available to Prebid and downstream bidding platforms, which will then be used as a signal for context-based audience and bidding decisions.

How it Works

  1. The publisher exposes contextual signals through the supported sources, such as the data layer script provided in Console.

  2. ATS.js sends those signals to the embedding resolver, together with an ATS envelope and consent information.

  3. The resolver returns a standardized embedding.

  4. ATS.js stores the embedding in first-party browser storage under _lr_agentic_audiences_.

  5. The Prebid Agentic Audiences module reads the stored embedding and makes it available through the OpenRTB bidding flow.

ATS.js does not scrape the page, infer additional signals, or directly modify bid requests. The data layer script accepts the following contextual signals:

  • Page URL

  • Page title

  • Keywords

Configuring Agentic Audiences Integration

  1. From the navigation pane, select ATS → Web and click the ATS configuration you want to set up Agentic Audiences for.

  2. Select the Integrations tab.

  3. Click New and select Agentic Audiences.

  4. Use the Trigger dropdown option to select how data layer detection should be initiated:

    • Manually: You trigger the detection manually by calling THE ats.detectDataLayerEvents() function when you know the event data have been stored on data layer.

    • Automatically: Data layer events are automatically detected.

  5. Copy the code snippet and click Add.

  6. Click Publish to save the changes.

Add the code snippet in the <head> of the pages of your website. If you are leveraging Launchpad to install your ATS configuration, you can replace the ATS wrapper tag with the Launchpad tag. To find the Launchpad tag, select Admin and click open the Launchpad configuration under the Install ATS section.

In this section: