{"__v":26,"_id":"5720f21d10ffe40e00485b1f","category":{"__v":10,"_id":"5601c22c22ecf60d002b27b4","pages":["5601d37b70694e0d00e3c67e","5601d3a0d3ffde0d006abbd0","5601d3fd96e0f70d0044b110","5601d42096e0f70d0044b112","5601d45d7435de0d00fabc27","5601d48170694e0d00e3c680","561c925fac06982100493d19","56606f35bb77350d0073249b","567090d51dabd80d00b122ca","56abc1004e8ba20d006a23c9"],"project":"5429beef1163360800ed31fa","version":"5429beef1163360800ed31fd","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-22T21:03:40.067Z","from_sync":false,"order":7,"slug":"demand-manager","title":"Demand Manager"},"parentDoc":null,"project":"5429beef1163360800ed31fa","user":"56f305ac92cce10e00eaf0d9","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":"2016-04-27T17:08:45.251Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":5,"body":"**Pro Tip (status quo): **Yield/Mediation tools available in market today (or built in-house) lack the granular controls (audience rules, targeting), intelligence (automation of waterfall, holistic yield optimization, unified/reverse auctions) and automation (aggregated reporting) which modern day companies seek for.  \n\nFollowing are technical modules that make for a robust programmatic yield/mediation system to manage your programmatic partners.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"1. OpenRTB Engine\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Live\"\n}\n[/block]\nAbility to broadcast to multiple DSPs using the OpenRTB protocol that an ad opportunity exists in your site/app. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"2. Server-Side Integration Engine\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Live\"\n}\n[/block]\nMany Exchanges, SSPs and Ad Networks might themselves connect with DSPs to bring ads. These partners do not use OpenRTB but instead have their own custom APIs to connect with your audience. Ability to conform to their custom specifications and making ad-calls from server side. This is the right way to integrate partners that favor Header Bidding also. The goal is evaluate all partners equally in real-time without the overhead of client side code bloat.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"3. Real Time Data Aggregation Engine\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Live\"\n}\n[/block]\nSome partners don’t provide eCPM data in real-time, so you need the ability to pull it from their dashboards as frequently as possible. An overall ability to pull data via APIs and screen-scraping from every partner. If you are getting ad revenue from Facebook, Google or Twitter; you need to make them play nice (compete at same time versus getting “first look”) because perhaps their tools are biased to their ads?  \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"4. Automated Inventory Allocation Engine\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Live\"\n}\n[/block]\nUsing #3 Data from partners, building price models and trends to automatically adjust your priority; this is also known as the waterfall of which partner should be called at what point. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"5. Audience Rules & Targeting Engine\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Live\"\n}\n[/block]\nA lot of partners specialize in providing ad dollars for certain set of your audience (geography, gender, interests). It is best to target those partners for that audience and reduce noise everywhere else. Also remember that your team needs precise and granular controls like you have for direct-sold deals. Examples - what if you wanted to send 1st party data to Partner A and not to Partner B? Or say you wanted to monetize only certain segments of your users (who spend less than X minutes in a month) vs everyone? Or you want to roll out a policy to show maximum of only 2 ads to users in a specific country?\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"6. Bidding Patterns/Price Predictions Engine\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Coming Soon\"\n}\n[/block]\nAdvanced insights and recommendations based on bidding patterns/trends tied to your inventory (physical placement and at an audience level) \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"7. Holistic Yield Optimization / Reverse Auction Engine / Unified Auctions\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Live\"\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/SeWPCw8LRfK7Q5pTZiEf_Native%20Mediation%20Yield.png\",\n        \"Native Mediation Yield.png\",\n        \"1162\",\n        \"655\",\n        \"#153650\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nThis is a very important module. Ranking partners at a global level does not do any help. You need to optimize partners at an audience level. Doing this will enable you to get the best out of each of them. Ability to take price information from OpenRTB (DSPs), custom APIs (SSPs/Exchanges) and price predictions (Ad Networks) overlaid with forecasting insights to determine the best partner for every user and every ad opportunity in real-time. Modules from #3 to #6 feed into this engine. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"8. A/B Testing Partners\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Live\"\n}\n[/block]\nAbility to easily test new revenue partners against one-another using #5 Audience Rules Engine. Engineers hate adding tags, SDKs for every new partner. Neither the business teams should wait for engineering resources to test every new partner. It should be as simple as flipping ON/OFF switch.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"9. Creative Library\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Live\"\n}\n[/block]\nFull creative assets of ads that ran on your audience with full transparency from all partners (DSPs, SSPs and Ad Networks). All stored in one place forever. You can block them or better use it as a sales intelligence tool to form direct relationships with those advertisers. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"10. Cookie/User Sync Engine\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Live\"\n}\n[/block]\nAbility to sync cookies/User IDs with chosen partners, so they can pay higher when they have advertisers who are looking for a specific audience that you have. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"11. Quality Control Engine\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"success\",\n  \"title\": \"Live\"\n}\n[/block]\nNatural Language Processing and Textual Analysis to block ads and advertisers that will hurt user-experience when shown to your users.","excerpt":"What is inside AdsNative Demand Manager?","slug":"inside-demand-manager-yieldmediation-capabilities","type":"basic","title":"Yield/Mediation Capabilities"}

Yield/Mediation Capabilities

What is inside AdsNative Demand Manager?

**Pro Tip (status quo): **Yield/Mediation tools available in market today (or built in-house) lack the granular controls (audience rules, targeting), intelligence (automation of waterfall, holistic yield optimization, unified/reverse auctions) and automation (aggregated reporting) which modern day companies seek for. Following are technical modules that make for a robust programmatic yield/mediation system to manage your programmatic partners. [block:api-header] { "type": "basic", "title": "1. OpenRTB Engine" } [/block] [block:callout] { "type": "success", "title": "Live" } [/block] Ability to broadcast to multiple DSPs using the OpenRTB protocol that an ad opportunity exists in your site/app. [block:api-header] { "type": "basic", "title": "2. Server-Side Integration Engine" } [/block] [block:callout] { "type": "success", "title": "Live" } [/block] Many Exchanges, SSPs and Ad Networks might themselves connect with DSPs to bring ads. These partners do not use OpenRTB but instead have their own custom APIs to connect with your audience. Ability to conform to their custom specifications and making ad-calls from server side. This is the right way to integrate partners that favor Header Bidding also. The goal is evaluate all partners equally in real-time without the overhead of client side code bloat. [block:api-header] { "type": "basic", "title": "3. Real Time Data Aggregation Engine" } [/block] [block:callout] { "type": "success", "title": "Live" } [/block] Some partners don’t provide eCPM data in real-time, so you need the ability to pull it from their dashboards as frequently as possible. An overall ability to pull data via APIs and screen-scraping from every partner. If you are getting ad revenue from Facebook, Google or Twitter; you need to make them play nice (compete at same time versus getting “first look”) because perhaps their tools are biased to their ads? [block:api-header] { "type": "basic", "title": "4. Automated Inventory Allocation Engine" } [/block] [block:callout] { "type": "success", "title": "Live" } [/block] Using #3 Data from partners, building price models and trends to automatically adjust your priority; this is also known as the waterfall of which partner should be called at what point. [block:api-header] { "type": "basic", "title": "5. Audience Rules & Targeting Engine" } [/block] [block:callout] { "type": "success", "title": "Live" } [/block] A lot of partners specialize in providing ad dollars for certain set of your audience (geography, gender, interests). It is best to target those partners for that audience and reduce noise everywhere else. Also remember that your team needs precise and granular controls like you have for direct-sold deals. Examples - what if you wanted to send 1st party data to Partner A and not to Partner B? Or say you wanted to monetize only certain segments of your users (who spend less than X minutes in a month) vs everyone? Or you want to roll out a policy to show maximum of only 2 ads to users in a specific country? [block:api-header] { "type": "basic", "title": "6. Bidding Patterns/Price Predictions Engine" } [/block] [block:callout] { "type": "warning", "title": "Coming Soon" } [/block] Advanced insights and recommendations based on bidding patterns/trends tied to your inventory (physical placement and at an audience level) [block:api-header] { "type": "basic", "title": "7. Holistic Yield Optimization / Reverse Auction Engine / Unified Auctions" } [/block] [block:callout] { "type": "success", "title": "Live" } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/SeWPCw8LRfK7Q5pTZiEf_Native%20Mediation%20Yield.png", "Native Mediation Yield.png", "1162", "655", "#153650", "" ] } ] } [/block] This is a very important module. Ranking partners at a global level does not do any help. You need to optimize partners at an audience level. Doing this will enable you to get the best out of each of them. Ability to take price information from OpenRTB (DSPs), custom APIs (SSPs/Exchanges) and price predictions (Ad Networks) overlaid with forecasting insights to determine the best partner for every user and every ad opportunity in real-time. Modules from #3 to #6 feed into this engine. [block:api-header] { "type": "basic", "title": "8. A/B Testing Partners" } [/block] [block:callout] { "type": "success", "title": "Live" } [/block] Ability to easily test new revenue partners against one-another using #5 Audience Rules Engine. Engineers hate adding tags, SDKs for every new partner. Neither the business teams should wait for engineering resources to test every new partner. It should be as simple as flipping ON/OFF switch. [block:api-header] { "type": "basic", "title": "9. Creative Library" } [/block] [block:callout] { "type": "success", "title": "Live" } [/block] Full creative assets of ads that ran on your audience with full transparency from all partners (DSPs, SSPs and Ad Networks). All stored in one place forever. You can block them or better use it as a sales intelligence tool to form direct relationships with those advertisers. [block:api-header] { "type": "basic", "title": "10. Cookie/User Sync Engine" } [/block] [block:callout] { "type": "success", "title": "Live" } [/block] Ability to sync cookies/User IDs with chosen partners, so they can pay higher when they have advertisers who are looking for a specific audience that you have. [block:api-header] { "type": "basic", "title": "11. Quality Control Engine" } [/block] [block:callout] { "type": "success", "title": "Live" } [/block] Natural Language Processing and Textual Analysis to block ads and advertisers that will hurt user-experience when shown to your users.