{"_id":"57ec45ab4a04260e009cf431","category":{"_id":"5925d868feb3f90f000a7595","project":"5661bda6f5a87e0d00db3285","version":"5661bda7f5a87e0d00db3288","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-05-24T19:00:56.518Z","from_sync":false,"order":1,"slug":"access-audiences","title":"How To: Access Audiences"},"parentDoc":null,"user":"5661cc12f183880d004d3193","githubsync":"","version":{"_id":"5661bda7f5a87e0d00db3288","project":"5661bda6f5a87e0d00db3285","__v":9,"createdAt":"2015-12-04T16:21:59.490Z","releaseDate":"2015-12-04T16:21:59.490Z","categories":["5661bda8f5a87e0d00db3289","5661cd4bf183880d004d3195","5666281e3fcf5a0d000ef16b","56902d2e18c3920d00be8b5f","56afc7545b1f01170014dc31","56f9a06a4d2b4f3400edb648","5761c2fe207db7170022fc51","5925d868feb3f90f000a7595","5925db7af33cb40f007604fa"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"Learning the PushSpring UI","version_clean":"1.0.0","version":"1.0"},"__v":1,"project":"5661bda6f5a87e0d00db3285","metadata":{"title":"","description":"","image":[]},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-09-28T22:35:23.685Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"The first thing you will need to do to access PushSpring data via The Trade Desk is to submit a send request. That is a pretty simple process, but just in case, we've provided a refresher in Step 1. Once you submit the send request, follow the directions below (See Option 1, 2 & 3) to access those segments for activation.\n\n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\n**Step 1.**  Send Segments to The Trade Desk\nSelect the segments you would like pushed, if you need details on how to send to a partner please refer to [How To Export.](http://docs.pushspring.com/docs/how-to-export)\n\n**When initially configuring The Trade Desk as a partner you will need the following:** \n  * TTD partner ID:* This is normally a 7 character string that consists of numbers and letters. Please reach out to your TTD Rep if you do not know this ID.*\n  * Partner Name: *Your organization name within TTD.*\n  * TTD Account Manager: *You will need to know your account managers name.*\n\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"At this step it is important to choose which format you'd like to receive your data; cookies, mobile ad IDs, or both.\",\n  \"body\": \"If you send as both cookies and mobile ad IDs we will deliver ONE cross-device segment in The Trade Desk platform. Here are some guidelines to keep in mind when choosing which format you'd like to use: \\n· Mobile AD ID's - All ad formats (interstitial, video etc) targeting MOBILE IN-APP inventory only\\n· Cookies - All ad formats (Interstitial, video etc.) on desktop and mobile web inventory\\n\\nDo note, if you select 'cookies' or 'cookies AND mobile ad IDs', this will add to your segment availability SLA. Expect to receive these segments in 7-9 calendar days.\"\n}\n[/block]\n**Option 1.** Access **Mobile Ad ID** Custom Segments via The Trade Desk\n\nIn The Trade Desk console segments can be found by either filtering for 'PushSpring' under Third Party Data or by searching for the name of a particular segment. Mobile Ad ID segments will have 'web: <1000' to indicate that it is in app only.  **HINT: When searching for your segment the name will follow this convention: PushSpring > Custom > Org Name > Segment Name.** \n[block:callout]\n{\n  \"type\": \"success\",\n  \"body\": \"**When can I access the segments?**  within 2 business days\\n**Where can I use these segments?** Use these segments against all ad formats (interstitial, video etc.) against Mobile IN-APP inventory only\",\n  \"title\": \"I sent Mobile Ad ID's only, now what?\"\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/01fef2f-ss3.jpg\",\n        \"ss3.jpg\",\n        981,\n        640,\n        \"#085674\"\n      ]\n    }\n  ]\n}\n[/block]\n**Option 2.** Access **Cookie Only** Custom Segments via The Trade Desk\n\nSegments can be found in TTD by either filtering for 'PushSpring' under Third Party Data or by searching for the name of a particular segment. Cookies segments will have large counts in the 'web' field. This indicates that it can be used against web inventory. **HINT: When searching for your segment the name will follow this convention: PushSpring > Custom > Org Name > Segment Name.** \n[block:callout]\n{\n  \"type\": \"success\",\n  \"body\": \"**When can I access the segments?**  within 7-9 calendar days\\n**Where can I use these segments?** Use these segments against all ad formats (interstitial, video etc.) against desktop and mobile web inventory\",\n  \"title\": \"I sent Cookies only, now what?\"\n}\n[/block]\n **Option 3.** Access both **Cookie** and **Mobile Ad ID** segments via The Trade Desk \n\nWhen selecting both device types, PushSpring will send ONE cross-device segment to The Trade Desk. The segment will arrive in 7-9 calendar days.  Use the access instructions outlined in Option 1 or Option 2 above to find your segment. **HINT: When searching for your segment the name will follow this convention: PushSpring > Custom > Org Name > Segment Name.** \n\n**To easily identify cross-device segments look for a volume count of over 1000 devices in both web and in-app columns.**","excerpt":"","slug":"how-to-access-the-trade-desk-segments","type":"basic","title":"Access The Trade Desk Segments"}

Access The Trade Desk Segments


The first thing you will need to do to access PushSpring data via The Trade Desk is to submit a send request. That is a pretty simple process, but just in case, we've provided a refresher in Step 1. Once you submit the send request, follow the directions below (See Option 1, 2 & 3) to access those segments for activation. [block:api-header] { "type": "basic" } [/block] **Step 1.** Send Segments to The Trade Desk Select the segments you would like pushed, if you need details on how to send to a partner please refer to [How To Export.](http://docs.pushspring.com/docs/how-to-export) **When initially configuring The Trade Desk as a partner you will need the following:** * TTD partner ID:* This is normally a 7 character string that consists of numbers and letters. Please reach out to your TTD Rep if you do not know this ID.* * Partner Name: *Your organization name within TTD.* * TTD Account Manager: *You will need to know your account managers name.* [block:callout] { "type": "warning", "title": "At this step it is important to choose which format you'd like to receive your data; cookies, mobile ad IDs, or both.", "body": "If you send as both cookies and mobile ad IDs we will deliver ONE cross-device segment in The Trade Desk platform. Here are some guidelines to keep in mind when choosing which format you'd like to use: \n· Mobile AD ID's - All ad formats (interstitial, video etc) targeting MOBILE IN-APP inventory only\n· Cookies - All ad formats (Interstitial, video etc.) on desktop and mobile web inventory\n\nDo note, if you select 'cookies' or 'cookies AND mobile ad IDs', this will add to your segment availability SLA. Expect to receive these segments in 7-9 calendar days." } [/block] **Option 1.** Access **Mobile Ad ID** Custom Segments via The Trade Desk In The Trade Desk console segments can be found by either filtering for 'PushSpring' under Third Party Data or by searching for the name of a particular segment. Mobile Ad ID segments will have 'web: <1000' to indicate that it is in app only. **HINT: When searching for your segment the name will follow this convention: PushSpring > Custom > Org Name > Segment Name.** [block:callout] { "type": "success", "body": "**When can I access the segments?** within 2 business days\n**Where can I use these segments?** Use these segments against all ad formats (interstitial, video etc.) against Mobile IN-APP inventory only", "title": "I sent Mobile Ad ID's only, now what?" } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/01fef2f-ss3.jpg", "ss3.jpg", 981, 640, "#085674" ] } ] } [/block] **Option 2.** Access **Cookie Only** Custom Segments via The Trade Desk Segments can be found in TTD by either filtering for 'PushSpring' under Third Party Data or by searching for the name of a particular segment. Cookies segments will have large counts in the 'web' field. This indicates that it can be used against web inventory. **HINT: When searching for your segment the name will follow this convention: PushSpring > Custom > Org Name > Segment Name.** [block:callout] { "type": "success", "body": "**When can I access the segments?** within 7-9 calendar days\n**Where can I use these segments?** Use these segments against all ad formats (interstitial, video etc.) against desktop and mobile web inventory", "title": "I sent Cookies only, now what?" } [/block] **Option 3.** Access both **Cookie** and **Mobile Ad ID** segments via The Trade Desk When selecting both device types, PushSpring will send ONE cross-device segment to The Trade Desk. The segment will arrive in 7-9 calendar days. Use the access instructions outlined in Option 1 or Option 2 above to find your segment. **HINT: When searching for your segment the name will follow this convention: PushSpring > Custom > Org Name > Segment Name.** **To easily identify cross-device segments look for a volume count of over 1000 devices in both web and in-app columns.**