{"id":296,"date":"2024-05-25T17:52:57","date_gmt":"2024-05-25T17:52:57","guid":{"rendered":"https:\/\/adtransfer.org\/documentation\/?p=296"},"modified":"2024-05-25T17:52:57","modified_gmt":"2024-05-25T17:52:57","slug":"integrating-demand","status":"publish","type":"post","link":"https:\/\/adtransfer.org\/documentation\/index.php\/2024\/05\/25\/integrating-demand\/","title":{"rendered":"Integrating demand"},"content":{"rendered":"\n

Adding a new demand endpoint is a slightly more complex process which will thoroughly be explained in this section. It involves querying and interpreting the response of an XML or JSON feed which you received from your demand partner.<\/p>\n\n\n\n

    \n
  1. Select the ad format of the demand endpoint you are adding.
    <\/li>\n\n\n\n
  2. Copy \/ Paste the feed URL as received from your demand partner in the textarea with the same name.
    <\/li>\n\n\n\n
  3. For the interpretation of the feed to be correctly handled, you will need to manually replace the parameters within feed URL with our platform’s parameters.

    Important!<\/strong> Please keep in mind that each feed you receive from your demand partners is different and will most likely use different parameters and terminology. Pay close attention when replacing, otherwise your newly added feed will only return errors.

    COMPLETE LIST OF AVAILABLE PARAMETERS Parameter Format Description {ip}<\/code>ALL<\/small>Will be replaced with the IP address within the request. {ua}<\/code>ALL<\/small>Will be replaced with the USER AGENT within the request. {seid}<\/code>ALL<\/small>Will be replaced supply endpoint ID as listed within the database. {subid}<\/code>ALL<\/small>Will be replaced with the subid as provided by the supply endpoint within the request. {referrer}<\/code>ALL<\/small>Will be replaced with the referrer URL as provided by the supply endpoint within the request. {lang}<\/code>ALL<\/small>Will be replaced with the language as provided by the supply endpoint within the request. {category}<\/code>ALL<\/small>Will be replaced with the IAB category ( if any ) as provided by the supply endpoint within the request. If empty, the category of the supply endpoint’s parent website will be used. {age}<\/code>PUSH<\/small>Will be replaced with the subscription age ( unix timestamp ). {size}<\/code>PUSH<\/small>Will be replaced with the banner size as provided by the supply endpoint within the request. {today}<\/code>ALL<\/small>Helper parameter. Used for refined tracking. Will be replaced with the current date in the format YYYYMMDD<\/li>\n\n\n\n
  4. There are 2 available options for fetching the response of the feed you are adding.
    Important!<\/strong> Regardless of option you pick, make sure to select the response encoding properly ( XML or JSON ).

    \n
      \n
    1. Automated response fetching<\/strong> – the platform will perform a live request to the feed using the parameters inputed in the fields. (Recommended)
      <\/li>\n\n\n\n
    2. Manual response input<\/strong> – you copy \/ paste a response from the feed.
      <\/li>\n<\/ol>\n<\/li>\n\n\n\n
    3. The next step is to select the parameters received in the response of the feed and match them with the platform’s parameters. This is a very important step as well, so please pay close attention when selecting.

      Example:<\/strong> In the image below, you will see that the feed response has “description” named as “body”, the “click URL” named as “link” and the “bid” parameter named “cpc”, therefor we select them accordingly.
      <\/li>\n\n\n\n
    4. The last step consists of naming your newly added demand endpoint, setting the budget ( if any ), daily budget limits, selecting the revenue share, throttling and setting the targeting options ( if any ).


      Once submitted, the newly integrated demand endpoint will immediately go live and start being interrogated.<\/strong><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

      Adding a new demand endpoint is a slightly more complex process which will thoroughly be explained in this section. It involves querying and interpreting the response of an XML or JSON feed which you received from your demand partner.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"_links":{"self":[{"href":"https:\/\/adtransfer.org\/documentation\/index.php\/wp-json\/wp\/v2\/posts\/296"}],"collection":[{"href":"https:\/\/adtransfer.org\/documentation\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/adtransfer.org\/documentation\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/adtransfer.org\/documentation\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/adtransfer.org\/documentation\/index.php\/wp-json\/wp\/v2\/comments?post=296"}],"version-history":[{"count":1,"href":"https:\/\/adtransfer.org\/documentation\/index.php\/wp-json\/wp\/v2\/posts\/296\/revisions"}],"predecessor-version":[{"id":297,"href":"https:\/\/adtransfer.org\/documentation\/index.php\/wp-json\/wp\/v2\/posts\/296\/revisions\/297"}],"wp:attachment":[{"href":"https:\/\/adtransfer.org\/documentation\/index.php\/wp-json\/wp\/v2\/media?parent=296"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/adtransfer.org\/documentation\/index.php\/wp-json\/wp\/v2\/categories?post=296"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/adtransfer.org\/documentation\/index.php\/wp-json\/wp\/v2\/tags?post=296"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}