Skip to main content

Overview

PubMatic is a global sell-side platform (SSP) that allows publishers to monetise their digital content by connecting them with a network of advertisers. Integrated with Zeotap it helps marketers better understand their customers, improve the targeting of advertising campaigns and optimise the marketing strategies.

Supported Identifiers

This channel supports PubMatic Cookies, MAIDs ,IDP Base and ID5.

Components of PubMatic

Ensure that you have details about the below component of PubMatic available before creating a Destination.

Account ID

Account ID on the PubMatic platform is a unique identifier assigned to each account. It is used to distinguish between different accounts on the platform and is necessary for tracking and reporting purposes. To obtain your Account ID, reach out to your PubMatic POC.

Data Provider ID

Data Provider ID on the PubMatic platform is a unique identifier assigned to each data provider account. It is used to distinguish between different data sources on the platform and is required for activating, managing, and reporting on audience segments. To obtain your Data Provider ID, reach out to your PubMatic POC.

Create a Destination for PubMatic Publisher

Perform the following steps to create a Destination for PubMatic Publisher:
1
Log into the Zeotap CDP App and go to the DESTINATIONS application.
2
Click + Create Destination.
3
Under All Destinations, search for PubMatic Publisher.
4
Click PubMatic Publisher. A screen appears displaying details about the particular destination towards the left. On the right-hand side of the screen find a list of fields that are required for the integration to be established. Enter the required details as mentioned in the following steps:a. Enter a name for the Destination.b.Enter the Account Id number on which the client has requested the Segment.c.Enter the Data Provider ID.d.Review all the values entered above and then click Next to proceed.
5
In the new screen that appears, choose the appropriate action and mapping as explained below.a. Choose the desired action under Choose your Action and then choose the corresponding identifiers under Map the Fields. By default, the Output Identifiers that are accepted by the platform such as, MAIDs, Cookies, IDP base, and ID5 are displayed. However, you can edit, add or remove an identifier from the list. To do so, refer here.b. Click Create Destination. The created Destination gets listed in the Audience application, which can be linked to an Audience/segment.
For information about how to link an Audience or segment to the created Destination in Target and Connect applications, refer here. Note that it can take upto three business days for the segment to be available at the PubMatic seat.
NoteThe terms Audiences and Segments are used interchangeably to refer to customer cohorts belonging to a specific category. For example, an Audience or a segment can be a specific group of customers who are over 18 years of age and have performed an addToCart event within the last 30 days.

View Segments on PubMatic

In the PubMatic console, you can view the segments that are pushed by Zeotap under Audience Segments. However, PubMatic has limitations when it comes to handling map and mwebIDs within the same segment. If you create a segment in the Zeotap CDP App that includes both map and mwebIDs, we internally create two versions of it and push them both to PubMatic. As a result, both versions are listed together under Audience Segments. You are required to update the sharing permissions for both segments accordingly.
Within the Zeotap CDP App you can see two cards with two separate segment IDs (one for cookie and the other for Device IDs).
NotePlease note that once uploads are completed from Zeotap, it may take a few hours for the files to appear and be ingested on the PubMatic platform.

User Disqualifying from Segments

A user may be disqualified from a segment for various reasons like not meeting the segment criteria, consent requirement or any other conditions set for a particular Connect segment.
  • Once a user disqualifies from a Connect segment, Zeotap initiates a user deletion request in the subsequent refresh cycle. These requests are sent to the audiences that were created on PubMatic.
  • The disqualified users are excluded from the segments based on the refresh frequency that was configured for a particular Connect segment.
  • Note that the user disqualification is a programmatic process that works automatically. You do not have to specify anything in particular to trigger the disqualification and exclusion of users from segments. However, you have to enable the deletion of users from segments during the refresh feature on the Admin application.
Last modified on February 26, 2026