{"_id":"5b695d9aeb010600032934d1","project":"5429beef1163360800ed31fa","version":{"_id":"5429beef1163360800ed31fd","__v":22,"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","5a3718305c66a60012d960ba"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"55f9dbefc7ef770d00d9bf6d","version":"5429beef1163360800ed31fd","__v":6,"pages":["55f9eec4c7ef770d00d9bf83","55f9fb8daba81f0d00a11566","5601ca6870694e0d00e3c66f","5601cb9b96e0f70d0044b0fd","56157d7af2d81d0d006c895f","5671d738c17bf90d00b95822"],"project":"5429beef1163360800ed31fa","sync":{"url":"","isSync":false},"reference":true,"createdAt":"2015-09-16T21:15:27.664Z","from_sync":false,"order":4,"slug":"publisher-ui-setup","title":"Trafficking and Inventory"},"user":"59521bff71e9dd0015d8e05e","githubsync":"","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2018-08-07T08:51:38.815Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":true,"order":39,"body":"An option for publishers to set floor prices at various granular levels to ensure maximum price for their inventory\n\nCustom floor is available under Placements\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/2f24d45-Screen_Shot_2018-08-07_at_16.35.22.png\",\n        \"Screen Shot 2018-08-07 at 16.35.22.png\",\n        920,\n        187,\n        \"#042342\"\n      ]\n    }\n  ]\n}\n[/block]\nClick on the tab to add new custom floor\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/e6f5151-Screen_Shot_2018-08-07_at_16.37.00.png\",\n        \"Screen Shot 2018-08-07 at 16.37.00.png\",\n        1812,\n        680,\n        \"#0d84cc\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"title\": \"Adding a new Custom Floor\"\n}\n[/block]\n1. Click on `+Add New Custom Floor`. Custom floor `Create` view should be seen\n2. As you can see in the image below, four filters are provided for Custom floors \nExample - Placement, Partner Accounts, Campaign, Geo \n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/15ecfa4-Screen_Shot_2018-08-07_at_16.44.27.png\",\n        \"Screen Shot 2018-08-07 at 16.44.27.png\",\n        2414,\n        814,\n        \"#dbdddd\"\n      ]\n    }\n  ]\n}\n[/block]\n3. Under Placement dropdown, you can see all the live placements\n    Under the Partner Accounts dropdown, you can see all the Partner Accounts\n    If a partner account has more than 1 partner, then you can specify the partner name in the Partner \n    field\n    Under Campaigns dropdown, you can see all the live campaigns\n    Under the Geo dropdown, you can see the list of all countries\n4. Select a single or multiple filters based on the requirement\n5. Click on Save\n6. If there aren't any conflicts, the custom rule will be added successfully\n[block:api-header]\n{\n  \"title\": \"Editing a Custom Rule\"\n}\n[/block]\n1. Click on edit button\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/36439c4-Screen_Shot_2018-08-07_at_17.13.44.png\",\n        \"Screen Shot 2018-08-07 at 17.13.44.png\",\n        1808,\n        424,\n        \"#104a73\"\n      ]\n    }\n  ]\n}\n[/block]\n2. Below screen can be seen. \nYou can update the floor price\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/1a6d559-Screen_Shot_2018-08-07_at_17.15.41.png\",\n        \"Screen Shot 2018-08-07 at 17.15.41.png\",\n        2382,\n        778,\n        \"#eeefef\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"title\": \"Deleting the Custom Rule\"\n}\n[/block]\n1. Click on the delete button\n2. If there aren't any conflicts, the custom rule will be deleted successfully\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/0cfe4b4-Screen_Shot_2018-08-07_at_17.17.06.png\",\n        \"Screen Shot 2018-08-07 at 17.17.06.png\",\n        1926,\n        576,\n        \"#f9f9f9\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"title\": \"Search support\"\n}\n[/block]\nYou can search for a custom rule by entering its ID, Placement ID, Placement name, Partner Account name, Partner name, Country code, Campaign ID, Campaign name or the floor price in the search toolbox\n[block:api-header]\n{\n  \"title\": \"Geo Placement View\"\n}\n[/block]\nWe provide a table view of floors at the placement and geo\n\nEach cell represents floor price for a placement at a geo level\nBy clicking on the floor price, you can update the price\nAlso, delete option is available for each cell\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/05db9c7-Screen_Shot_2018-08-08_at_13.31.16.png\",\n        \"Screen Shot 2018-08-08 at 13.31.16.png\",\n        887,\n        308,\n        \"#2c5873\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"title\": \"Query View\"\n}\n[/block]\nUnder query view, \nUser can filter by - geo, partner account, partner placement, campaign\nThe user can control the hierarchy of the results by selecting splits from:  geo, partner account, partner placement, campaign \nBy clicking on the floor price, you can edit the floor price\nDelete option is also available\n\n\nFew examples to help you understand query view better\n\nExample 1 - **To list all the rules at geo-placement level** \n\nSelect the splits as `Geo` and `Placement`\n\nList of custom rules with floor prices will be seen\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/e66462b-Screen_Shot_2018-08-08_at_14.26.55.png\",\n        \"Screen Shot 2018-08-08 at 14.26.55.png\",\n        905,\n        374,\n        \"#e3e4e5\"\n      ]\n    }\n  ]\n}\n[/block]\nExample 2 - **To list all the rules at campaign-placement level **\n\nSelect the splits as `Campaign` and `Placement`\n\nExample 3 - **To list all the rules for a specific Partner account**\n\nSelect the Filter as specific Partner Account\n\nNow add the splits. \n\nTo list all the Partner Account specific rules, add the split as Partner Account\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/55882a8-Screen_Shot_2018-08-08_at_14.50.24.png\",\n        \"Screen Shot 2018-08-08 at 14.50.24.png\",\n        907,\n        287,\n        \"#1786c9\"\n      ]\n    }\n  ]\n}\n[/block]\nTo list combination rule of Partner Account - Geo, select the split as Partner Account and Geo\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/0ab05bd-Screen_Shot_2018-08-08_at_14.50.40.png\",\n        \"Screen Shot 2018-08-08 at 14.50.40.png\",\n        879,\n        349,\n        \"#e1e3e4\"\n      ]\n    }\n  ]\n}\n[/block]\nNote: When you select splits as Geo and Partner Accounts, you won't be able to view Partner Account level floors\n\nIf there is no rule for the selected splits, below screen is seen\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/7dba8f6-Screen_Shot_2018-08-08_at_14.50.51.png\",\n        \"Screen Shot 2018-08-08 at 14.50.51.png\",\n        893,\n        309,\n        \"#1985c6\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"title\": \"Conflict Resolutions\"\n}\n[/block]\nWhile adding new rule/ deleting a rule, you may see a list of conflicts\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/f5e3029-Screen_Shot_2018-08-08_at_15.01.40.png\",\n        \"Screen Shot 2018-08-08 at 15.01.40.png\",\n        864,\n        292,\n        \"#848484\"\n      ]\n    }\n  ]\n}\n[/block]\nTo resolve these, please contact us\n[block:api-header]\n{\n  \"title\": \"What's a conflict?\"\n}\n[/block]\nWe support geo, placement , partner account, partner and campaign filters. Amongst these geo and placement are considered as Publisher filters and partner account, partner and campaign are considered as Advertiser filters\n\n**Granularity of publisher filters**\n\nGeo < placement\n\n**Granularity of advertiser filters**\n\nPartner account < partner < campaign\n\n**Overall granularity**\nNetwork level floor is the least granular\nPartner account, partner and geo have higher granularity than network\nThe most granular levels are placement and campaign\n\n**Note - If there is conflict between publisher level filters and advertiser level filter of same granularity, advertiser filter floor is prioritised**\n\n*Overall granularity in conflict cases\nNetwork<geo<Partner account<partner<placement<campaign*\n\n\n\n**Example - **\n\n1.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"network\",\n    \"h-1\": \"placement\",\n    \"h-2\": \"campaign\",\n    \"h-3\": \"floor\",\n    \"0-0\": \"523\",\n    \"0-1\": \"null\",\n    \"0-2\": \"23415\",\n    \"0-3\": \"1\",\n    \"1-0\": \"523\",\n    \"1-1\": \"27168\",\n    \"1-2\": \"null\",\n    \"1-3\": \"1.5\"\n  },\n  \"cols\": 4,\n  \"rows\": 2\n}\n[/block]\nIn the above table, there are 2 rules. One more a campaign and other for a placement.\nPlacement and campaign are of same granularity.\nSo when we get request from zone 27168 (for which campaign 23415 eligible), it results in a conflict\nSo UI won't allow to add rule 2 until the conflict is resolved\n\nTo resolve the above conflict, you have to add the rule 2 from the table below\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"network\",\n    \"h-1\": \"placement\",\n    \"h-2\": \"campaign\",\n    \"h-3\": \"floor\",\n    \"0-0\": \"523\",\n    \"0-1\": \"null\",\n    \"0-2\": \"23415\",\n    \"0-3\": \"1\",\n    \"2-0\": \"523\",\n    \"2-1\": \"27168\",\n    \"2-2\": \"null\",\n    \"2-3\": \"1.5\",\n    \"1-0\": \"523\",\n    \"1-1\": \"27168\",\n    \"1-2\": \"23415\",\n    \"1-3\": \"1.5\"\n  },\n  \"cols\": 4,\n  \"rows\": 3\n}\n[/block]\n2.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"network\",\n    \"h-1\": \"placement\",\n    \"h-2\": \"geo\",\n    \"h-3\": \"provider_type_id(Partner account ID)\",\n    \"h-4\": \"floor\",\n    \"0-0\": \"523\",\n    \"1-0\": \"523\",\n    \"2-0\": \"523\",\n    \"0-1\": \"29908\",\n    \"1-1\": \"29908\",\n    \"2-1\": \"null\",\n    \"2-2\": \"US\",\n    \"1-2\": \"US\",\n    \"0-2\": \"null\",\n    \"0-3\": \"null\",\n    \"1-3\": \"null\",\n    \"2-3\": \"Taboola\",\n    \"0-4\": \"2.5\",\n    \"1-4\": \"4\",\n    \"2-4\": \"1\",\n    \"3-0\": \"523\",\n    \"3-1\": \"null\",\n    \"3-2\": \"null\",\n    \"3-3\": \"Outbrain\",\n    \"3-4\": \"1.5\"\n  },\n  \"cols\": 5,\n  \"rows\": 4\n}\n[/block]\nThe above rules result in conflict for the case when placement 29908 from US region sends a request and has a campaign from Outbrain eligible \nIn the above example conflict arises between geo and partner account. \n\nTo resolve the above conflict, you have to add row 4 in the below table\n\n\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"network\",\n    \"h-1\": \"placement\",\n    \"h-2\": \"geo\",\n    \"h-3\": \"provider_type_id(Partner account ID)\",\n    \"h-4\": \"floor\",\n    \"0-0\": \"523\",\n    \"1-0\": \"523\",\n    \"2-0\": \"523\",\n    \"3-0\": \"523\",\n    \"0-1\": \"29908\",\n    \"1-1\": \"29908\",\n    \"2-1\": \"null\",\n    \"3-1\": \"29908\",\n    \"0-2\": \"null\",\n    \"3-2\": \"US\",\n    \"1-2\": \"US\",\n    \"2-2\": \"US\",\n    \"0-3\": \"null\",\n    \"1-3\": \"null\",\n    \"2-3\": \"Taboola\",\n    \"3-3\": \"Outbrain\",\n    \"0-4\": \"2.5\",\n    \"1-4\": \"4\",\n    \"2-4\": \"1\",\n    \"3-4\": \"1.5\",\n    \"4-0\": \"523\",\n    \"4-1\": \"null\",\n    \"4-2\": \"null\",\n    \"4-3\": \"Outbrain\",\n    \"4-4\": \"1.5\"\n  },\n  \"cols\": 5,\n  \"rows\": 5\n}\n[/block]","excerpt":"","slug":"custom-floor","type":"basic","title":"Custom Floors"}
An option for publishers to set floor prices at various granular levels to ensure maximum price for their inventory Custom floor is available under Placements [block:image] { "images": [ { "image": [ "https://files.readme.io/2f24d45-Screen_Shot_2018-08-07_at_16.35.22.png", "Screen Shot 2018-08-07 at 16.35.22.png", 920, 187, "#042342" ] } ] } [/block] Click on the tab to add new custom floor [block:image] { "images": [ { "image": [ "https://files.readme.io/e6f5151-Screen_Shot_2018-08-07_at_16.37.00.png", "Screen Shot 2018-08-07 at 16.37.00.png", 1812, 680, "#0d84cc" ] } ] } [/block] [block:api-header] { "title": "Adding a new Custom Floor" } [/block] 1. Click on `+Add New Custom Floor`. Custom floor `Create` view should be seen 2. As you can see in the image below, four filters are provided for Custom floors Example - Placement, Partner Accounts, Campaign, Geo [block:image] { "images": [ { "image": [ "https://files.readme.io/15ecfa4-Screen_Shot_2018-08-07_at_16.44.27.png", "Screen Shot 2018-08-07 at 16.44.27.png", 2414, 814, "#dbdddd" ] } ] } [/block] 3. Under Placement dropdown, you can see all the live placements Under the Partner Accounts dropdown, you can see all the Partner Accounts If a partner account has more than 1 partner, then you can specify the partner name in the Partner field Under Campaigns dropdown, you can see all the live campaigns Under the Geo dropdown, you can see the list of all countries 4. Select a single or multiple filters based on the requirement 5. Click on Save 6. If there aren't any conflicts, the custom rule will be added successfully [block:api-header] { "title": "Editing a Custom Rule" } [/block] 1. Click on edit button [block:image] { "images": [ { "image": [ "https://files.readme.io/36439c4-Screen_Shot_2018-08-07_at_17.13.44.png", "Screen Shot 2018-08-07 at 17.13.44.png", 1808, 424, "#104a73" ] } ] } [/block] 2. Below screen can be seen. You can update the floor price [block:image] { "images": [ { "image": [ "https://files.readme.io/1a6d559-Screen_Shot_2018-08-07_at_17.15.41.png", "Screen Shot 2018-08-07 at 17.15.41.png", 2382, 778, "#eeefef" ] } ] } [/block] [block:api-header] { "title": "Deleting the Custom Rule" } [/block] 1. Click on the delete button 2. If there aren't any conflicts, the custom rule will be deleted successfully [block:image] { "images": [ { "image": [ "https://files.readme.io/0cfe4b4-Screen_Shot_2018-08-07_at_17.17.06.png", "Screen Shot 2018-08-07 at 17.17.06.png", 1926, 576, "#f9f9f9" ] } ] } [/block] [block:api-header] { "title": "Search support" } [/block] You can search for a custom rule by entering its ID, Placement ID, Placement name, Partner Account name, Partner name, Country code, Campaign ID, Campaign name or the floor price in the search toolbox [block:api-header] { "title": "Geo Placement View" } [/block] We provide a table view of floors at the placement and geo Each cell represents floor price for a placement at a geo level By clicking on the floor price, you can update the price Also, delete option is available for each cell [block:image] { "images": [ { "image": [ "https://files.readme.io/05db9c7-Screen_Shot_2018-08-08_at_13.31.16.png", "Screen Shot 2018-08-08 at 13.31.16.png", 887, 308, "#2c5873" ] } ] } [/block] [block:api-header] { "title": "Query View" } [/block] Under query view, User can filter by - geo, partner account, partner placement, campaign The user can control the hierarchy of the results by selecting splits from: geo, partner account, partner placement, campaign By clicking on the floor price, you can edit the floor price Delete option is also available Few examples to help you understand query view better Example 1 - **To list all the rules at geo-placement level** Select the splits as `Geo` and `Placement` List of custom rules with floor prices will be seen [block:image] { "images": [ { "image": [ "https://files.readme.io/e66462b-Screen_Shot_2018-08-08_at_14.26.55.png", "Screen Shot 2018-08-08 at 14.26.55.png", 905, 374, "#e3e4e5" ] } ] } [/block] Example 2 - **To list all the rules at campaign-placement level ** Select the splits as `Campaign` and `Placement` Example 3 - **To list all the rules for a specific Partner account** Select the Filter as specific Partner Account Now add the splits. To list all the Partner Account specific rules, add the split as Partner Account [block:image] { "images": [ { "image": [ "https://files.readme.io/55882a8-Screen_Shot_2018-08-08_at_14.50.24.png", "Screen Shot 2018-08-08 at 14.50.24.png", 907, 287, "#1786c9" ] } ] } [/block] To list combination rule of Partner Account - Geo, select the split as Partner Account and Geo [block:image] { "images": [ { "image": [ "https://files.readme.io/0ab05bd-Screen_Shot_2018-08-08_at_14.50.40.png", "Screen Shot 2018-08-08 at 14.50.40.png", 879, 349, "#e1e3e4" ] } ] } [/block] Note: When you select splits as Geo and Partner Accounts, you won't be able to view Partner Account level floors If there is no rule for the selected splits, below screen is seen [block:image] { "images": [ { "image": [ "https://files.readme.io/7dba8f6-Screen_Shot_2018-08-08_at_14.50.51.png", "Screen Shot 2018-08-08 at 14.50.51.png", 893, 309, "#1985c6" ] } ] } [/block] [block:api-header] { "title": "Conflict Resolutions" } [/block] While adding new rule/ deleting a rule, you may see a list of conflicts [block:image] { "images": [ { "image": [ "https://files.readme.io/f5e3029-Screen_Shot_2018-08-08_at_15.01.40.png", "Screen Shot 2018-08-08 at 15.01.40.png", 864, 292, "#848484" ] } ] } [/block] To resolve these, please contact us [block:api-header] { "title": "What's a conflict?" } [/block] We support geo, placement , partner account, partner and campaign filters. Amongst these geo and placement are considered as Publisher filters and partner account, partner and campaign are considered as Advertiser filters **Granularity of publisher filters** Geo < placement **Granularity of advertiser filters** Partner account < partner < campaign **Overall granularity** Network level floor is the least granular Partner account, partner and geo have higher granularity than network The most granular levels are placement and campaign **Note - If there is conflict between publisher level filters and advertiser level filter of same granularity, advertiser filter floor is prioritised** *Overall granularity in conflict cases Network<geo<Partner account<partner<placement<campaign* **Example - ** 1. [block:parameters] { "data": { "h-0": "network", "h-1": "placement", "h-2": "campaign", "h-3": "floor", "0-0": "523", "0-1": "null", "0-2": "23415", "0-3": "1", "1-0": "523", "1-1": "27168", "1-2": "null", "1-3": "1.5" }, "cols": 4, "rows": 2 } [/block] In the above table, there are 2 rules. One more a campaign and other for a placement. Placement and campaign are of same granularity. So when we get request from zone 27168 (for which campaign 23415 eligible), it results in a conflict So UI won't allow to add rule 2 until the conflict is resolved To resolve the above conflict, you have to add the rule 2 from the table below [block:parameters] { "data": { "h-0": "network", "h-1": "placement", "h-2": "campaign", "h-3": "floor", "0-0": "523", "0-1": "null", "0-2": "23415", "0-3": "1", "2-0": "523", "2-1": "27168", "2-2": "null", "2-3": "1.5", "1-0": "523", "1-1": "27168", "1-2": "23415", "1-3": "1.5" }, "cols": 4, "rows": 3 } [/block] 2. [block:parameters] { "data": { "h-0": "network", "h-1": "placement", "h-2": "geo", "h-3": "provider_type_id(Partner account ID)", "h-4": "floor", "0-0": "523", "1-0": "523", "2-0": "523", "0-1": "29908", "1-1": "29908", "2-1": "null", "2-2": "US", "1-2": "US", "0-2": "null", "0-3": "null", "1-3": "null", "2-3": "Taboola", "0-4": "2.5", "1-4": "4", "2-4": "1", "3-0": "523", "3-1": "null", "3-2": "null", "3-3": "Outbrain", "3-4": "1.5" }, "cols": 5, "rows": 4 } [/block] The above rules result in conflict for the case when placement 29908 from US region sends a request and has a campaign from Outbrain eligible In the above example conflict arises between geo and partner account. To resolve the above conflict, you have to add row 4 in the below table [block:parameters] { "data": { "h-0": "network", "h-1": "placement", "h-2": "geo", "h-3": "provider_type_id(Partner account ID)", "h-4": "floor", "0-0": "523", "1-0": "523", "2-0": "523", "3-0": "523", "0-1": "29908", "1-1": "29908", "2-1": "null", "3-1": "29908", "0-2": "null", "3-2": "US", "1-2": "US", "2-2": "US", "0-3": "null", "1-3": "null", "2-3": "Taboola", "3-3": "Outbrain", "0-4": "2.5", "1-4": "4", "2-4": "1", "3-4": "1.5", "4-0": "523", "4-1": "null", "4-2": "null", "4-3": "Outbrain", "4-4": "1.5" }, "cols": 5, "rows": 5 } [/block]