Zeropark Documentation

Direct URL Integration

The Direct URL feed integration model allows publishers to send traffic directly to Zeropark servers. 

Since there is no external auction, Zeropark bids do not compete with other advertisers, ad exchanges or DSPs. 

Publishers cannot decide in real-time whether to sell the visit based on the returned bid. Publisher payout for a visitor is determined based on the winning campaign’s bid and the minimal CPM/CPC if provided. 

Traffic that is not bought by Zeropark is sent back to the publisher’s fallback URL declared in the request or set in the feed’s setup.

Integration overview:
  • Feed Language: XML

  • Accepted Traffic: Pop, Domain, Search

  • Bid Format: CPV/CPC

  • Auction: internal only

Integration flow:
  1. For a Direct URL Ad tag, publishers receive the Campaign URL (including CPM and fallback parameter) that they need to redirect the visits to.

  2. Publishers must set a fallback URL. Otherwise, traffic that isn’t bought by Zeropark will be lost.

  3. Publishers need to set the URL parameters both in the Zeropark platform and in their own system, too.

  4. The Direct URL integration is very simple, yet it comes with certain limitations.

  5. The Direct URL integration does not support the real-time bidding process.

  6. That means publishers cannot decide (in real-time) whether to sell the visit based on the Zeropark bid response.

  7. The auction is based on the CMP set by publishers in their Campaign URL.

  8. If the bid response from Zeropark meets the CPM floor price set by publishers, the visit will be sold.

  9. If the bid response from Zeropark doesn’t meet the CPM floor price set by publishers, the visit will be redirected to the fallback URL.

  10. That means publishers integrating via Direct URL cannot send bid requests to multiple partners at the same time.

Prerequisites:
  • Create a publisher account on Zeropark.com

  • Every query must be unique; feed responses cannot be cached.

  • Publishers can add more parameters than the ones required by Zeropark or described below.

  • Receive a feed ID

  • Every query must be unique; feed responses cannot be cached.

  • Publishers can add more parameters than the ones required by Zeropark or described below.

Feed queries specification:
  • Every query must be unique; feed responses cannot be cached.

  • The Direct URL feed contains a range of required parameters that must be passed in the feed call.

Feed parameters specification:
  • Publishers can add more parameters than the ones required by Zeropark or described below.

  • Parameters always come after the Zeropark domain with the protocol*: http://feed.zeropark.com/

    * The domain provided above is just an example, please reach out to us for a proper link. We are able to set/change dedicated domains for our publishers.

  • They are provided after ‘?’ indicating the start of query parameters and separated with ‘&’.

  • Parameters in a request can be placed randomly.

  • All parameters must be URL encoded. Most web programming languages provide a method of encoding the URL to ensure that invalid characters are not included in the HTTP GET request.

  • Reference can be made to the HTTP specification from W3C for URL encoding details (http://www.w3.org/).

Feed request syntax:
http://feed.zeropark.com/{domain}?adTagId=<adTag_id>&cpm=<cpm>&keywords=<keyword1,keyword2>&fallbackUrl=<fallback.example.com>

*Curly bracket that the domain value is placed in means that this information has to be replaced with the actual domain name.

** Zeropark system accepts two version of fallback query parameter: fallbackUrl or fallbackurl

The required parameters include:

  • domain URL of the site where the user was generated. If not provided then we need domainid (one below).  

  • adTagId our unique ID assigned to that feed/AdTag 

  • cpm/cpc minimal CPM/CPC set by publishers expressed in USD, e.g.: $5 CPM = $0.005 CPV or CPC = $0.015

  • fallbackUrl all unsold traffic is sent to the fallback URL provided by publishers. Extra parameters can be added to the Fallback URL.

Publishers often include the following parameters, too:

  • keywords keywords associated with the visited domain or site that generated the user.

  • ip visitor’s IP(v4) address in the dotted format to determine geolocation.

Example of query call:

http://feed.zeropark.com/text.com?adTagId=262bf110-2e0c-11e9-97c9-0a15cb739170&cpm=5&keywords=movies,videos&fallbackUrl=fallback.test.com
Feed response format:

There is no response for the Direct URL feed as a visitor is already in our system.