{"_id":"564f0d9aaf8ae235002db90e","project":"564621e00c30fb2100ba3814","user":"56499dade2efd717002afc83","parentDoc":null,"category":{"_id":"568585153703ed1700e420b0","pages":["568585ded96a760d00545da2","5685860f009a8d0d0079711c","5685865554f9a50d00f982dc","56858741d96a760d00545da4","5685a6e00ffbaf17007c6859","56ee9edbb76bc319004627ee"],"project":"564621e00c30fb2100ba3814","__v":6,"version":"564621e10c30fb2100ba3817","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-12-31T19:42:13.206Z","from_sync":false,"order":1,"slug":"mobfox-supply-side-platform","title":"Publisher Resources"},"version":{"_id":"564621e10c30fb2100ba3817","__v":14,"project":"564621e00c30fb2100ba3814","createdAt":"2015-11-13T17:46:09.275Z","releaseDate":"2015-11-13T17:46:09.275Z","categories":["564621e10c30fb2100ba3818","564624cf0c30fb2100ba3822","564628d69f3f550d00fa3db6","564dafeeda00e82b00ed601d","564daff8fc36dc3700882b95","564db0ccda00e82b00ed601f","564dcf87d3320b0d0028ca10","5661a6e436398e0d00f79566","568585153703ed1700e420b0","56858767d96a760d00545da6","56858d693703ed1700e420b2","56858d8d22c41b0d00e4666c","56859e9c009a8d0d00797130","5685a6453703ed1700e420d3"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"__v":15,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-11-20T12:10:02.842Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"Here we capture common issues that a Publisher/Supply Partner may have.\nTypically, these issue(s) manifest with low earnings or figures being reported the MobFox dashboard incorrectly.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Render Rate (RR)\"\n}\n[/block]\nWe express the Render Rate as a % (Impressions/ads served*100). The Render Rate is one measure that the Exchange uses to establish the quality of an integration a typically good render rate is expected to be around the 90%+ mark.\n\nPoor Render rates can affect the ability of a property to monetise and cause issues with Demand Partners.\n\nSee below information that will help you address possible integration issues that could lead to a low render rate.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Render Rate Issues Troubleshooting\"\n}\n[/block]\nThere are various factors that can affect your render rate.\n\n**The issue could be due to one or a combination of factors:**\n\n**1)** The possible incorrect parsing of our ad response.  \nIn the example below , there is a [CDATA] section. This section should be rendered on the device without being manipulated.\n\nAd response structure and [CDATA]\n\nThere are two ad response examples below. The section in yellow is the part that should not be manipulated. The section in purple is an example of the impression tracking url (Impression Beacon).\n\nThe impression tracking URL is the URL that needs to be fired on the user device for us to recognise that the render occurred and we should count the impression.  \nThere can be multiple impression pixels. \n\n**2)** If you are an aggregator of content then you may have a minimum amount of time that you wish MobFox to respond.  If we do not respond with in that time threshold you may ignore our response\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/1oeaX5PSfyuMWDdb4jKE_renderrateissues1.png\",\n        \"renderrateissues1.png\",\n        \"864\",\n        \"194\",\n        \"#916c48\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/omAWwPwQVeBfLYd1aPiW_renderrateissues2.png\",\n        \"renderrateissues2.png\",\n        \"500\",\n        \"347\",\n        \"#cc5fcc\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n See below example of two issues that result if Impression Beacon is not fired.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/7j520DODSM6gOZKwdifW_renderrateissues3.png\",\n        \"renderrateissues3.png\",\n        \"864\",\n        \"225\",\n        \"#ab534a\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n**The following scenarios could be the cause of the low impression count:**\n\n**1)** You have a mediation layer and an Ad is served to you but the mediation layer denies use of the ad. If this is the case please contact technical support to discuss this problem.\n\n**2)** You parse our response and strip out the impression beacon. \nThis will result in no revenue earnings. \n\n**3)** You cache the Ad and the click URL \n\nThis is not permissible.  If the impression beacon does not fire, your publication will not be paid the appropriate revenue for the impression.   Our system also counts clicks without impressions in this scenario.  This results in the CTR being greater than 100%. \n\n**4)** You ignore our ad response due to time out.\n\n**5)** You conduct some sort of internal auction and do not use all ads served.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Possible Resolutions\"\n}\n[/block]\n**1)** Do not parse the ad response.  Render the [CDATA] section without manipulation. \nPlease do not cache banners or click links as they all have unique identifiers.\n\n**2)** Firing the impression beacon on the server side can not be considered a resolution to this issue.  Our system will recognise this behaviour and will not allow revenue from server side impression beacon firing. See point 3 below.\n\n**3)** The system cross checks both the User Agent (UA) and the IP address between 3 specific events (Ad request, Impression and Click) both the UA and IP must match between the 3 events for us the system to accept the advertising activity from your publications or inventories. \n\n**4)** If you must parse the ad response to enable click counting for your system, ensure that the redirect of the user on to our click URL is performed in the most efficient manner possible.\nThis is necessary  to reduce the render time of the Landing Page.\nPlease bear in mind that the click URL must originate from the device, do not insert a click counter in front of the MobFox click URL.","excerpt":"Supply Side Issues","slug":"common-publisher-issues-supply-side-issues","type":"basic","title":"Common Publisher Issues"}

Common Publisher Issues

Supply Side Issues

Here we capture common issues that a Publisher/Supply Partner may have. Typically, these issue(s) manifest with low earnings or figures being reported the MobFox dashboard incorrectly. [block:api-header] { "type": "basic", "title": "Render Rate (RR)" } [/block] We express the Render Rate as a % (Impressions/ads served*100). The Render Rate is one measure that the Exchange uses to establish the quality of an integration a typically good render rate is expected to be around the 90%+ mark. Poor Render rates can affect the ability of a property to monetise and cause issues with Demand Partners. See below information that will help you address possible integration issues that could lead to a low render rate. [block:api-header] { "type": "basic", "title": "Render Rate Issues Troubleshooting" } [/block] There are various factors that can affect your render rate. **The issue could be due to one or a combination of factors:** **1)** The possible incorrect parsing of our ad response. In the example below , there is a [CDATA] section. This section should be rendered on the device without being manipulated. Ad response structure and [CDATA] There are two ad response examples below. The section in yellow is the part that should not be manipulated. The section in purple is an example of the impression tracking url (Impression Beacon). The impression tracking URL is the URL that needs to be fired on the user device for us to recognise that the render occurred and we should count the impression. There can be multiple impression pixels. **2)** If you are an aggregator of content then you may have a minimum amount of time that you wish MobFox to respond. If we do not respond with in that time threshold you may ignore our response [block:image] { "images": [ { "image": [ "https://files.readme.io/1oeaX5PSfyuMWDdb4jKE_renderrateissues1.png", "renderrateissues1.png", "864", "194", "#916c48", "" ] } ] } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/omAWwPwQVeBfLYd1aPiW_renderrateissues2.png", "renderrateissues2.png", "500", "347", "#cc5fcc", "" ] } ] } [/block]  See below example of two issues that result if Impression Beacon is not fired. [block:image] { "images": [ { "image": [ "https://files.readme.io/7j520DODSM6gOZKwdifW_renderrateissues3.png", "renderrateissues3.png", "864", "225", "#ab534a", "" ] } ] } [/block] **The following scenarios could be the cause of the low impression count:** **1)** You have a mediation layer and an Ad is served to you but the mediation layer denies use of the ad. If this is the case please contact technical support to discuss this problem. **2)** You parse our response and strip out the impression beacon. This will result in no revenue earnings. **3)** You cache the Ad and the click URL This is not permissible. If the impression beacon does not fire, your publication will not be paid the appropriate revenue for the impression. Our system also counts clicks without impressions in this scenario. This results in the CTR being greater than 100%. **4)** You ignore our ad response due to time out. **5)** You conduct some sort of internal auction and do not use all ads served. [block:api-header] { "type": "basic", "title": "Possible Resolutions" } [/block] **1)** Do not parse the ad response. Render the [CDATA] section without manipulation. Please do not cache banners or click links as they all have unique identifiers. **2)** Firing the impression beacon on the server side can not be considered a resolution to this issue. Our system will recognise this behaviour and will not allow revenue from server side impression beacon firing. See point 3 below. **3)** The system cross checks both the User Agent (UA) and the IP address between 3 specific events (Ad request, Impression and Click) both the UA and IP must match between the 3 events for us the system to accept the advertising activity from your publications or inventories. **4)** If you must parse the ad response to enable click counting for your system, ensure that the redirect of the user on to our click URL is performed in the most efficient manner possible. This is necessary to reduce the render time of the Landing Page. Please bear in mind that the click URL must originate from the device, do not insert a click counter in front of the MobFox click URL.