Eligible Platforms
Users can self-deploy to a number of partner platforms. After designing your segment, refer to information below to check if you can self-deploy or need Customer Support assistance.
| Company | Targeting Types | Supports File Upload | File Support Ticket |
|---|---|---|---|
| Adform | Audience | N/A | File Support Ticket |
| AdTheorent | Proximity, Audience | Yes | Yes |
| Amazon (Ads) | Audience | N/A | Yes |
| Basis Technologies (fka Centro) | Proximity, Audience | Yes | Yes |
| Beeswax | Proximity, Audience | Yes | File Support Ticket |
| Epsilon | Audience | N/A | File Support Ticket |
| Google (DV360 & GAM) | Audience | N/A | File Support Ticket |
| Illumin (fka AcuityAds) | Audience | N/A | Yes |
| Audience | N/A | File Support Ticket | |
| META (Facebook) | Audience | N/A | File Support Ticket |
| Nexxen (fka Amobee/Turn) | Audience | N/A | File Support Ticket |
| Audience | N/A | File Support Ticket | |
| Audience | N/A | File Support Ticket | |
| Roku/OneView (fka Dataxu) | Audience | N/A | File Support Ticket |
| Samsung Ads | Audience | N/A | File Support Ticket |
| Snapchat | Audience | N/A | File Support Ticket |
| Spotify | Audience | N/A | File Support Ticket |
| StackAdapt | Audience | N/A | Yes |
| SoundCloud (Pandora) | Audience | N/A | File Support Ticket |
| The Trade Desk | Proximity, Audience | Yes | Yes |
| TikTok | Audience | N/A | File Support Ticket |
| Viant (Adelphic) | Proximity, Audience | Yes | Yes |
| Vistar Media | Audience | N/A | Yes |
| Xandr / Appnexus / Clypd | Audience | N/A | Yes |
| Yahoo! (fka Verizon, Oath) | Audience | N/A | File Support Ticket |
More Information
Additional information about providers from the table above.
AdTheorent (Audience)
- Naming convention:
[AdTheorentAdvID]_[Advertiser/Campaign]_[Audience]_[DateDesign]
Basis (Proximity)
- Naming convention:
[AdvID]_[Advertiser/Campaign]_[Targeting]_[CampaignEndDate] - Size of segment must be <= 5MB, please reach out to Customer Support if segment is invalid
Basis (Audience)
- Naming convention:
[AdvID]_[Advertiser/Campaign]_[Targeting]_FSQ
Google (Audience)
(DV360 & GAM)
- Mobile & Cross-Device (XD) must be broken out into two separate segments:
- Mobile can be deployed self-served
- XD must be through LiveRamp, please submit a ticket through the Customer Support Portal
StackAdapt (Audience)
- Naming convention:
[AccountID]_[Advertiser/Campaign]_[Targeting]_FSQ
The Trade Desk (Proximity)
-
Partner ID needs to be onboarded, please reach out to Customer Support for assistance.
-
One Set cannot be larger than 400K locations. Please break out into multiple Sets/Targeting Codes when POI count is >400K.
-
For all national Proximity segments, two Sets of segments must be built to follow state privacy laws:
- A segment that filters out POIs in NY, WA & CT. This segment can be built with any desired radius.
- A segment that includes NY, WA & CT only, that will be branded with "_WANYCT". This segment must be built with a minimum radius of 3,000 feet (914m).
The Trade Desk (Audience)
- Partner ID needs to be onboarded, please reach out to Customer Support for assistance.
- Naming convention:
[Advertiser/Campaign]_[Targeting]_FSQ
Viant
- Provider ID (Advertiser Credential) needs to be onboarded, please reach out to Customer Support for assistance.
- For segments with custom rates, please submit a ticket to Customer Support.
Xandr
- Please submit a ticket to Customer Support to confirm the ID you are deploying to is enabled for Data Clearing.
Updated 20 days ago