Eligible Platforms
Users are able to self-deploy to a number of partner platforms. Click the links to learn more information about a supported platform.
| Platform | Proximity | Audience |
|---|---|---|
| Adform | No | Yes, via Customer Support |
| AdTheorent | Yes | Yes |
| Amazon (Ads) | No | Yes |
| Basis Technologies (fka Centro) | Yes | Yes |
| Beeswax | Yes | Yes, via Customer Support |
| Epsilon | No | Yes, via Customer Support |
| Google (DV360 & GAM) | No | Yes, for XD via Customer Support |
| Illumin (fka AcuityAds) | No | Yes |
| No | Yes, via Customer Support | |
| META (Facebook) | No | Yes, via Customer Support |
| Nexxen (fka Amobee/Turn) | No | Yes, via Customer Support |
| No | Yes, via Customer Support | |
| No | Yes, via Customer Support | |
| Roku/OneView (fka Dataxu) | No | Yes, via Customer Support |
| Samsung Ads | No | Yes, via Customer Support |
| Snapchat | No | Yes, via Customer Support |
| Spotify | No | Yes, via Customer Support |
| StackAdapt | No | Yes |
| SoundCloud (Pandora) | No | Yes, via Customer Support |
| The Trade Desk | Yes | Yes |
| TikTok | No | Yes, via Customer Support |
| Viant (Adelphic) | Yes | Yes |
| Vistar Media | No | Yes |
| Xandr / Appnexus / Clypd | Yes | Yes |
| Yahoo! (fka Verizon, Oath) | No | Yes |
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.
Still have questions?
Visit our customer support portal for further support.
Updated 21 days ago