{"__v":0,"_id":"58fa71c3fb0d3c0f00eafaee","category":{"__v":3,"_id":"5603738d0c78b00d0039af47","pages":["561311eb41a9ec0d00a3fdf8","56958542cb14e11700f8a86e","56ad90e50c1cab0d009f658b"],"project":"5429beef1163360800ed31fa","version":"5429beef1163360800ed31fd","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-24T03:52:45.801Z","from_sync":false,"order":5,"slug":"exchange","title":"Marketplace"},"parentDoc":null,"project":"5429beef1163360800ed31fa","user":"569d8ad30306a10d00ce9a1f","version":{"__v":21,"_id":"5429beef1163360800ed31fd","project":"5429beef1163360800ed31fa","createdAt":"2014-09-29T20:19:59.904Z","releaseDate":"2014-09-29T20:19:59.904Z","categories":["5429beef1163360800ed31fe","55e74e1f5d36b32b002563fa","55e7500a73169617001f2e86","55e76b8196131b2f00bf4b72","55e89569cdbb8a350096df9c","55f8935eb089b71700a8364e","55f8a67d3bb4bb0d0022d093","55f9dbefc7ef770d00d9bf6d","5601c21a22ecf60d002b27b3","5601c21ff12aee0d001bb06e","5601c2256c7b610d00280db5","5601c22c22ecf60d002b27b4","5603738d0c78b00d0039af47","5626f70bfcbbc621004ebf52","566f7a1ae144ab0d00e9732f","566f85ca7820960d00c3b93d","56708ce43a32d20d00c45cbf","56708d436995210d003aad8e","5736471abe10a9200030732c","57a82c7aff9bd30e00a6f1c1","591b8500e3992319007190f4"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-04-21T20:55:31.954Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":13,"body":"Welcome to S2S Demand Partner Setup wiki!\n[block:api-header]\n{\n  \"title\": \"Yahoo! Flurry S2S API Partner\"\n}\n[/block]\n1. On the AdsNative dashboard, go to the \"**Networks**\" tab and add a new **Server to Server** network type\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/cfe8d48-Screen_Shot_2017-04-21_at_2.07.05_PM.png\",\n        \"Screen Shot 2017-04-21 at 2.07.05 PM.png\",\n        706,\n        307,\n        \"#f5f6f7\"\n      ]\n    }\n  ]\n}\n[/block]\n2. On the next screen, choose the network partner \"Flurry API\"\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/e5f60ce-Screen_Shot_2017-04-21_at_2.03.53_PM.png\",\n        \"Screen Shot 2017-04-21 at 2.03.53 PM.png\",\n        699,\n        465,\n        \"#349cdb\"\n      ]\n    }\n  ]\n}\n[/block]\n3. On the next screen enter the Flurry Credentials to create a S2S network campaign. \nNote : Credentials are used to fetch placement information and reports data for revenue optimization only.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/b322d54-Screen_Shot_2017-04-21_at_2.05.37_PM.png\",\n        \"Screen Shot 2017-04-21 at 2.05.37 PM.png\",\n        542,\n        451,\n        \"#fafafa\"\n      ]\n    }\n  ]\n}\n[/block]\n4. On the Flurry API Campaign page you need to fill in THREE main fields\n**Ad Space Name**  (Found in Flurry Dashboard)\n**API Key** (Found in Flurry Dashboard : you need to get the “Programmatic Access Token” from flurry dashboard. Use it as the API Key in the above field)\nFlurry Documentation for API Key : https://developer.yahoo.com/flurry/docs/api/code/apptoken/\n**Publisher URL**  (Ask flurry to provide this for you. It will be usually https://www.yourdomain.com)\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/3c5d000-Screen_Shot_2017-04-21_at_2.19.13_PM.png\",\n        \"Screen Shot 2017-04-21 at 2.19.13 PM.png\",\n        610,\n        312,\n        \"#b6c7d3\"\n      ]\n    }\n  ]\n}\n[/block]\nOnce all three fields are filled, make sure you targeting and scheduling settings are setup according to your needs. Save and done, thats it.\n\nNow, whenever AdsNative receives a ad request from your web / in-app native placements, the ad server will conduct a unified auction, that identifies all of the eligible ads from each partner, each direct sold campaign, and each real-time bidder. \n\nIn this example, we send a real-time API bid request to Flurry on the server side, while we simultaneously make a request to all the integrated DSPs and identify the eligible direct sold campaigns. If a bid is received from Flurry, AdsNative returns the final winning ad from all the demand sources in the iOS / Android / JavaScript SDK response.\n\nClient-side handling does not require any work, if you are handling direct sold campaigns then server-to-server ad responses will look the same and will be automatically be handled in your integration. \n\nFor any questions with integration, please contact us at support:::at:::adsnative.com","excerpt":"","slug":"server-to-server-demand-partner-setup","type":"basic","title":"Server-to-Server Demand Partner Setup"}

Server-to-Server Demand Partner Setup


Welcome to S2S Demand Partner Setup wiki! [block:api-header] { "title": "Yahoo! Flurry S2S API Partner" } [/block] 1. On the AdsNative dashboard, go to the "**Networks**" tab and add a new **Server to Server** network type [block:image] { "images": [ { "image": [ "https://files.readme.io/cfe8d48-Screen_Shot_2017-04-21_at_2.07.05_PM.png", "Screen Shot 2017-04-21 at 2.07.05 PM.png", 706, 307, "#f5f6f7" ] } ] } [/block] 2. On the next screen, choose the network partner "Flurry API" [block:image] { "images": [ { "image": [ "https://files.readme.io/e5f60ce-Screen_Shot_2017-04-21_at_2.03.53_PM.png", "Screen Shot 2017-04-21 at 2.03.53 PM.png", 699, 465, "#349cdb" ] } ] } [/block] 3. On the next screen enter the Flurry Credentials to create a S2S network campaign. Note : Credentials are used to fetch placement information and reports data for revenue optimization only. [block:image] { "images": [ { "image": [ "https://files.readme.io/b322d54-Screen_Shot_2017-04-21_at_2.05.37_PM.png", "Screen Shot 2017-04-21 at 2.05.37 PM.png", 542, 451, "#fafafa" ] } ] } [/block] 4. On the Flurry API Campaign page you need to fill in THREE main fields **Ad Space Name** (Found in Flurry Dashboard) **API Key** (Found in Flurry Dashboard : you need to get the “Programmatic Access Token” from flurry dashboard. Use it as the API Key in the above field) Flurry Documentation for API Key : https://developer.yahoo.com/flurry/docs/api/code/apptoken/ **Publisher URL** (Ask flurry to provide this for you. It will be usually https://www.yourdomain.com) [block:image] { "images": [ { "image": [ "https://files.readme.io/3c5d000-Screen_Shot_2017-04-21_at_2.19.13_PM.png", "Screen Shot 2017-04-21 at 2.19.13 PM.png", 610, 312, "#b6c7d3" ] } ] } [/block] Once all three fields are filled, make sure you targeting and scheduling settings are setup according to your needs. Save and done, thats it. Now, whenever AdsNative receives a ad request from your web / in-app native placements, the ad server will conduct a unified auction, that identifies all of the eligible ads from each partner, each direct sold campaign, and each real-time bidder. In this example, we send a real-time API bid request to Flurry on the server side, while we simultaneously make a request to all the integrated DSPs and identify the eligible direct sold campaigns. If a bid is received from Flurry, AdsNative returns the final winning ad from all the demand sources in the iOS / Android / JavaScript SDK response. Client-side handling does not require any work, if you are handling direct sold campaigns then server-to-server ad responses will look the same and will be automatically be handled in your integration. For any questions with integration, please contact us at support@adsnative.com