Adhese supports the integration of the Adhese ad server into mobile applications by means of ad tags.
Ad tags are pieces of code that inform the Adhese ad server about the inventory it can target. This happens by sending an ad request URL that contains the necessary information and targeting parameters. In reply to this request, Adhese returns a JSON delivery response that enables the application to deliver an ad and track its impressions and clicks in a correct way.
An example of a request URL which contains only the basic (required) parts:
The value of the account attribute can be found in your Adhese subscription information or through our support portal.
- Adding this part to the URL makes sure that the result you receive is JSON formatted.
- JSON has a fixed structure and, therefore, fixed fields. Refer to List of JSON response structure object fields for an explanatory list of the fields.
/sl[location code]-[format code]/
- Adding a timestamp is necessary to avoid caching issues.
If necessary, additional parameters can be added to the request URL for the purpose of Targeting.
An URL which contains targeting will look like this:
Every target parameter is prefixed by a 2 letter combination, followed by the actual target(s). If more than one value is sent within one target, the values should be separated by a semicolon.
The available targeting parameters and their prefixes are determined by your Adhese account configuration. Please contact our Support team for more details.
The following list contains default parameters which are set up on every account:
/br: brands or data about the browser and operating system;
/dt: device type, such as phone, tablet, desktop or unknown;
/in: interests, this parameter is user defined.
The request returns a JSON object with the fields described at List of JSON response structure object fields. An empty JSON object (just two curly brackets) is returned if Adhese cannot deliver a suitable ad for the request.