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:
You can find the value of the account attribute 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]/
- To avoid caching issues it is necessary to add a timestamp.
The request URL can contain additional parameters for the purpose of Targeting.
An URL which contains targeting will look like this:
A 2-letter combination (e.g. br, dt or in) prefixes every target parameter and the actual target(s) comes after. If a parameter contains more than one target, use a semicolon to separate the different values.
The configuration of your Adhese account determines the available targeting parameters and their prefixes. Please contact our Support team for more details.
Every account contains the following default parameters:
/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. Adhese returns an empty JSON object (just two curly brackets) if it cannot deliver a suitable ad for the request.