> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anteriad.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Programmatic Destinations

## LinkedIn

> ❗️ Requirements for LinkedIn
>
> * **LinkedIn Marketing Account** *(with admin access)*
> * **LinkedIn Ad Account ID**
> * **Deliverable** *(Domain/Site-Level)*\
>   *A postal/site-level account list can be extended by delivering the domains that match to each company. Site-Level will deliver the 1-1 match to the onboarded account.*

**Where does the data go?**\
In LinkedIn Campaign Manager, under **Account Assets** > **Matched Audiences**, the segment delivered will have the prefix "180CST\_"

## Google DV360

> ❗️ Requirements for Google DV360
>
> * **Google Account**
> * **Entity ID**\
>   *Google Account ID (MCC or CID). Remove hyphens.*
> * **Account Type**\
>   *[Refer here](https://support.google.com/displayvideo/answer/7622449?hl=en) or your Google Representative for assistance on which account type to use.*

**Where does the data go?**\
Google Audience Manager

## Facebook

> ❗️ Requirements for Facebook
>
> * **Facebook Marketing Account** *(with admin access)*
> * **Your Facebook authentication**
> * **Facebook ad account you want the audience delivered to**\
>   *Currently, only the ad\_id is sent to Facebook*

**Where does the data go?**\
In LinkedIn Campaign Manager, under **Account Assets** > **Matched Audiences**. The segment will have the prefix "180CST\_".

## Managed Services

> ❗️ Requirements for Managed Services
>
> * **Access to the Managed Services Destination**
> * **Campaign Start Date, End Date, and Name**

**Where does the data go?**\
The data will be housed in our DSP, and the campaign will be managed by our service team.

## Oracle Data Cloud

> ❗️ Requirements for Oracle Data Cloud
>
> * **A seat on ODC**
> * **Access to Onboarding**
> * **Account ID**
> * **Customer**
> * **Oracle Data Cloud AM email address**
> * **Destination Account**

**Where does the data go?**\
Audiences will be found in your ODC seat.

## Lotame DMP

> ❗️ Requirements for Lotame DMP
>
> * **A seat in Lotame DMP**
> * **Access to Onboarding**
> * **Account ID**
> * **Lotame Delivery Folder**
> * **Destination Account Name**

**Where does the data go?**\
Audiences will be found in your Lotame seat

## Pubmatic

> ❗️ Requirements for Pubmatic
>
> * **A seat in Pubmatic*or* a DSP account that Pubmatic can deliver to**
> * **DP ID (Date Partner ID)**
> * **Segment ID**\
>   *(We need to first register the segment in the platform)*
> * **Refresh Token**\
>   *This is found in your Pubmatic admin console.*

**Where does the data go?**\
Data will be found in your Pubmatic Audience Inventory.

## The Trade Desk

> ❗️ Requirements for The Trade Desk
>
> * **A seat in The Trade Desk**
> * **Access to your AM**
> * **Advertiser ID**
> * **Brand**
> * **Data Provider**\
>   *(Ex: 180byTwo)*
> * **Encryption Key**
> * **Partner ID**
> * **TTD Account Manager Email**
> * **Your Email**
>
> *You will also need to reach out to your TTD AM to verify transfer. If using the TTD Enterprise API, you will need to request and sign an API access letter.*

**Where does the data go?**\
The data will be delivered to your TTD seat based on the information provided from above.

## Beeswax

> ❗️ Requirements for Beeswax
>
> * **A seat in Beeswax**
> * **Email/Username & Password for your Beeswax seat**
> * **Buzzkey associated with your Beeswax seat**

**Where does the data go?**\
The data will be in the **Segments** section of your Beeswax seat.