Advertiser Specific Segments in Console

Advertiser specific segments in Console

Overview

This update introduces publisher-controlled audience visibility within Console. Advertisers now only see the audience segments they’re approved to use when configuring campaign targeting—keeping things clean, safe, and brand-aligned. Shared “agency template” segments remain available to all advertisers, while custom segments can now be restricted on a per-advertiser basis.

Who’s Impacted?

• Publishers looking to manage brand exclusivity and reduce manual oversight
• Advertisers who build campaigns within Console
• Agency teams who rely on shared audience templates

What’s New

• Audience Segments Now Match Each Advertiser’s Permissions
• When an advertiser creates a campaign, the Segments dropdown now shows only the segments they’re allowed to use. Console automatically filters segments by Advertiser ID via the Segment API.

What advertisers will see:

• Only their assigned custom segments
• All standard agency-template segments (still shared across advertisers)
• A clear “Shared” or “Custom” label on each segment

If no segments are assigned:

• Advertisers see an empty state: “No segments are currently available for this advertiser.”
• A brief explanation clarifies that segment access is managed by the publisher.

Why It Matters

• Protects brand exclusivity: Advertisers can only target audiences approved for them.
• Prevents targeting mistakes: No more accidental use of the wrong segments.
• Reduces publisher workload: Less manual monitoring and cleanup.
• Streamlines the advertiser experience: Simpler, faster, safer campaign setup.

Enhancements Under the Hood

To support this logic cleanly, several improvements were made across services:

Backend

• Added a NIPE endpoint to fetch segment IDs based on Advertiser ID
• Extended Campaign Service to merge:
• Segments retrieved via advertiser permissions
• Segments already assigned via agency templates
• Updated Advertiser model to include Segment Access, similar to Catalog Access
• Management API now accepts an array of segment IDs during create/update for easier bulk updates

Management UI

• Added new controls in the advertiser form to assign or remove segment access
• Publishers can now directly manage which advertisers can use which audience segments

Frontend

• No workflow changes—just smarter data behind the scenes
• Segments are now visually marked as Shared or Custom to help advertisers understand their options

Fixed Issues

• Resolved inconsistencies where some advertisers could see segments not intended for them
• Eliminated the need for publishers to manually clean up mistakenly used segments
• Improved reliability of audience rendering by syncing template and advertiser-specific lists

Known Limitations

• Segment-level permissions still assume that template-based and advertiser-assigned segments refer to the same underlying segment entity
• Any future expansion of segment types may require updates to the access model

Verification & Test Results

• Testing covered both existing and newly created advertisers across multiple agencies. Confirmed that:
• Advertisers only see their assigned custom segments
• Shared agency-template segments remain fully visible
• New advertisers do not inherit custom segments from others
• Frontend labels for “Shared” vs “Custom” render correctly
• Everything passed across scenarios in Console.