Step 3: Set Up Ad Tags
Learn how to set up ad tags that are essential for sending traffic from your website to advertisers. Read about ad tag types and general guidelines.
This tab provides you with the list of all ad tags.
 |
I. Creating Ad Tag
In order to create the new one, perform the following steps:
Click the
button.
Select the ad tag type. Creation of a Push Ad Tag can be requested at your Account Manager or Zeropark Publisher Team.
Provide the feed name and select the traffic type that you'll be sending. Then click the Continue button.
Provide additional traffic information. Then click the Continue button.
Provide your fallback URL. Then click the Continue button.
Verify your settings in the Summary section. Then click the Save button.
Setup your Ad tag according to the provided instructions. Then click the Finish button.
II. Ad Tag Details And Documentation
You can create Ad Tags (feeds) by yourself in the Zeropark panel or request them from your Account Manager / Zeropark Publisher Team. The number of Ad Tags will be dependent on different traffic types, mainstream or adult visitors, vertical settings or other justified reasons. It is recommended to consult your Account Manager on the creation of new Ad Tags, as their approval is required.
General guidelines are:
Mainstream and adult traffic needs to be separate.
Different traffic types should not be mixed.
Traffic for clean offers only has to be separate.
Below, you can find available options with the descriptions of parameters. It is recommended to discuss the setup beforehand as doing it right from the start will enable the best performance optimization possibilities.
Pop/Domain Redirect URL
Request parameter | Description |
adTagId * | Ad tag (feed) unique ID assigned by Zeropark |
domain * | URL of the site the visitor was generated |
cpm | Min price for which you’re willing to sell the traffic. Amount in $ for 1000 visits |
fallbackUrl | URL where any unsold visitor will be sent. Should start with http:// or https://. It’s possible to use: {domain}, {domainid}, {keywords} tokens within URL. These tokens will pass back the values from the original request |
keywords | sending multiple keywords, they should be separated by commas |
deviceid | Mobile device id: IDFA, ADID, Android ID or WAID, if available |
Pop/Domain Zeroclick (XML/JSON)
Request parameter | Description |
responseformat | Default setting is XML. JSON has to be specified responseformat=json |
feedid * | Ad tag (feed) unique ID assigned by Zeropark |
ip * | Visitor’s IP(v4) address in the dotted format |
useragent * | The URL encoded User Agent string sent by the visitor’s browser |
domain * | URL of the site the visitor was generated |
domainid/domainId | ID of the site / publisher where the visitor was generated. Domainid is not required if the domain parameter is provided, but both are recommendedID of the site / publisher where the visitor was generated. Domainid is not required if the domain parameter is provided, but both are recommended |
pubid | Id of the external publisher who generated the user |
deviceid/deviceId | Mobile device id: IDFA, ADID, Android ID or WAID, if available |
keywords | Keywords associated with the visited domain or site that generated the pop. If sending multiple keywords, they should be comma separated |
fallbackurl/passback | URL where any invalidated visitor will be sent. Should start with http:// or https://. It’s possible to use: {domain}, {domainid}, {keywords} tokens within URL. These tokens will pass back the values from the original request |
ref/referer/referrer | The address of the webpage from which a user is redirected |
forwardedip/proxyip | User’s X-Forwarded-For HTTP header value, whenever available |
secure | true/false - secure flag set to true enforces https protocol in all URLs and limits campaigns to ones that provide valid HTTPS redirection |
Pop/Domain Zeroclick (OpenRTB)
Request parameter | Description |
feedid * | Ad tag (feed) unique ID assigned by Zeropark |
site.domain | URL of the site the visitor was generated |
site.id | ID of the site where the user was generated. site.id is not required if the site.domain parameter is provided, but both are recommended |
device.ua * | The URL encoded User Agent string sent by the visitor’s browser |
device.ip * | Visitor’s IP(v4) address in the dotted format |
id * | RTB request id to be passed back in response |
imp.id * | Impression id to be passed back in response |
Push XML/JSON
Request parameter | Description |
ip/user_ip * | Visitor’s IP(v4) address in the dotted format |
useragent/ua * | The URL encoded User Agent string sent by the visitor’s browser |
feedid * | Ad tag (feed) unique ID assigned by Zeropark |
domain * | URL of the site the subscriber was generated |
domainid | ID of the site / publisher where the subscriber was generated. Domainid is not required if the domain parameter is provided, but both are recommended |
keywords | Keywords associated with the domain or site that generated the notification. If sending multiple keywords, they should be comma separated |
user_id | Unique identifier of the subscriber |
lang | User language setting as: HTTP header “Accept-Language” (example: en-US,en;q=0.9) Or ISO 639-1 (example: en) |
Push OpenRTB
Request Parameter | Description |
Id* | Ad tag (feed) unique ID assigned by Zeropark |
imp id* | Impression id to be passed back in response |
device ip* | Visitor’s IP(v4) address in the dotted format |
device ua* | The URL encoded User Agent string sent by the visitor’s browser |
site domain* | URL of the site the subscriber was generated |
user_id | Unique identifier of the subscriber |
property wlang | User language setting as: HTTP header “Accept-Language” (example: en-US,en;q=0.9) Or ISO 639-1 (example: en) |