Data integration requires these steps:
Audience Source creation
Registering audience segments requires an Audience Source/data partner ID (DPID); see, Create and Edit an Audience Source.
|Register only the new segments you send.|
You can bulk-register segments by uploading a correctly formatted CSV file. Download the CSV template from PubMatic:
Transfer audience data to PubMatic using one of the following methods:
- Server-to-server (S2S) data transfer
- Browser-side real-time (HTTP 302 redirect) data transfer
- Bulk audience data transfer using SFTP
PubMatic automatically removes user IDs older than 30 days. The best practice is to refresh data at least every 25 days.
The transfer options listed above require data submission using a specific set of parameters listed in the table below.
Data transfer parameters
PubMatic data partner ID (DPID) assigned to the data partner at time of integration.
The PubMatic user ID passed to the data partner by PubMatic.
A integer value that determines what the identity partner's PubMatic user ID represents:
Use segid to send the complete list of audience segment IDs to which the user belongs. Each subsequent request for that user with the segid parameter overwrites the user’s already existing segments list.
DO NOT send
You can include
You can include
Last known IP address of the user; optional when you send
Two-letter code for the user's country; for example,
Server-to-server (S2S) data transfer
Server-to-server data transfer is the best practice for submitting data to PubMatic since the servers communicate directly, so data transfer is highly-efficient. Build API calls using the parameters from the data transfer parameter table and make HTTP calls to the API endpoint:
Sample: standard call with segment IDs
In this request:
89is the data partner's PubMatic-assigned ID (DPID).
- The user belongs to three audience segments with IDs
uidtype=0means the user ID represents a cookie ID.
If your user IDs represent PubMatic cookie IDs, you must first use UID sync .
Sample: appending/removing segments
This request for the same data partner (
dpid=89) and user (
Browser-side real-time (HTTP 302 redirect) data transfer
Data partners who do not support server-to-server data transfer can pass data to PubMatic using browser-side real-time data transfer for each visitor as follows:
- A user visits the website using a browser, which upon loading, executes the PubMatic pixel.
- The PubMatic pixel invokes the data partner's pixel or URL to request the audience segment data for this visitor. To reduce the latency, this request is sent to the data partner only once in a pre-configured time interval per user; for example, once per day.
The data partner's system then redirects to the PubMatic Data Ingestion API using the HTTP 302 redirect. PubMatic shared the API URL with the data partner before the start of the integration. While redirecting to the API URL, the data partner's system must include all the IDs of the audience segments to which the visitor belongs.
Info title Data partner must also
Provide the segment ID-to-segment name mapping to PubMatic only once at the start of the integration.
Browser-side sample requests
In this request, which updates the entire audience segments list:
89is the data partner's PubMatic-assigned ID.
B8CB98E6-0FF0-4C2B-A161-4F89155C28Fis the PubMatic user ID (from UID sync).
the last known IP of the user:
the user's country:
the user's DMP audience segment IDs:
uidtype=0specifies that the user ID should be handled as a cookie ID (use UID sync when passing
For more information on all available parameters, see Data transfer parameters.
Bulk audience data transfer using SFTP
Use SFTP to transfer audience segment data to PubMatic within a tab-delimited file, where each row of the file contains the audience segment parameters separated by a tab character, with each row ending with a carriage-return as follows:
[SEGID] parameter refers to the Source Seg ID that was assigned to the segment during segment registration. You can submit multiple, comma-separated, source segment ID's.
For more information on the other parameters, see Data transfer parameters.
File name format
File names follow the pattern:
The tsv.gz suffix must follow the uploaded file name. Please verify that the file name is correct once upload completes.
103 5AFCD4CD-F9B6-4E53-B63D-BFB2CF44941D 4666 188.8.131.52 0
SFTP server details and access
Provided separately by PubMatic. Contact your PubMatic account manager with questions.
The data provider must provide PubMatic with an image pixel similar to:
<img src=" http://partner.com/xxxx?id=UID" width=1 height=1>
- If data comes from a publisher, then PubMatic incorporates the image pixel from step 1 in a PubMatic pixel. The publisher must fire the PubMatic pixel across their website to maximize coverage across their users. Firing the pixel also lets the data provider create the match-table.
- If data comes from a buyer, PubMatic fires the image pixel from step 1 across PubMatic's site.
Remove a user from audiences
Use one of the following methods to remove a user from all of their audiences (DMPs and publishers can use either method):
To send a list of segments to remove using the remseg parameter:
When sharing data via a bulk file, do not pass any segment ID in the file for the user record. Audiences in the latest record are stored for the user ID, overwriting the user's previous audiences.
API response codes
Once your API request has been processed by PubMatic, the system returns a response to let you know whether the request was successful or a problem occurred. When you send the request, the following happens at the HTTP layer:
- Returns HTTP response code 200 (Ok) when the request successfully completes.
- Returns HTTP response code 400/500 if issues occur while processing the data.
A successful request also includes a
StatusOK: Success code from PubMatic. If an error occurs, the response includes codes from PubMatic to identify what may have gone wrong. The table below lists all PubMatic response codes for this API.
|1||Bad request: |
|2||Internal Server Error: demand partner settings not found.|
|3||Bad Request: |
|4||Internal Server Error: failed to validate |
|5||Bad request: unregistered |
|6||Following segments are unregistered: |
|10||Bad request: user |
|11||Bad request: |
|12||Bad request: multiple |
|13||Bad request: multiple |
|15||Bad request: no segments present in this request.|
|16||Bad request: no |
|17||Bad request: |
|18||Bad request. user |