This page will tell you all about the data feed queries that your can make to sort the data your would like to show in your creatives. This documentation is ment for developers that are writing their own logic within creatives / banners.
Adcombi feeds are used for DCO campaigns and can do heavy lifting for you as they can handle a very high number of requests. This happens in advertising very often that you will have millions of requests per day and also multiple requests at the same time.
A typical feed looks like:
feedUrl: https://feed.adcombi.com/feeds/[yyyymmdd]_example
You can add custom parameters to the url to filter the feed.
In the rest of this page we will give you an overview for all queries that can be made on the feedUrl.
Getting started
Good to know is that there is no authorisation required on the feedUrl, because the feedUrl needs to be usable in creatives for campaigns while being used cross domain.
The standard feedUrl will show 100 results (see also "limit" query).
TIP: Loading the feedUrl for the first time in your browser will say "Forbidden". But when you select the feedUrl and hit "enter", the feedUrl will load in your browser. This does not mean that the feedUrl is not loading the first time in your creative, this is purely browser dependant.
The feedUrl contains text or images that can be used in the creatives. With filtering the feedUrl you can show the right information to the user and increase your relevance.
The attribute-value pairs can differ per campaign. Extra attribute-value pairs can be made while booking or updating a campaign via the Adcombi Technology. An example of an attribute-value pair is {"name": "Foodmarkt Veghel"}. Creating new attribute-value pairs allows you to add data to increase the local relevance even more.
Possible feed supplier queries:So let us list the different kind of queries your can do on a Adcombi feedUrl
1) where
2) reject
3) nearby_latlong
4) nearby_ids
5) random
6) limit
1) where
The “where” keyword is preceded by a question mark (?) and followed by an equals sign (=)
Then look in the feed for the thing you want to filter on. For example campaign_id, address, city or reference_code, followed by another equals sign followed by the value you are looking for.
Example:
https://feed.adcombi.com/feeds/yyyymmdd_example?where=campaign_id=1337
https://feed.adcombi.com/feeds/yyyymmdd_example?where=city=Amsterdam
Be aware of capital letters, as these have to be precisely as written in the feed itself. In other words, this is case-sensitive.
2) reject
“reject” is the keyword that will deny objects containing the keywords with the chosen value
Example:
https://feed.adcombi.com/feeds/yyyymmdd_example?reject=city=Den%20Bosch
Note: the space in between the city name is written as a "%20".
3) nearby_latlong
“nearby_latlong” Will find the nearest object based on coordinates. The objects are listed in ascending order.
Example:
https://feed.adcombi.com/feeds/yyyymmdd_example?nearby_latlong=43.89,1.87
Important to know is that this query is only available when the feedUrl has been geocoded. This means that you will need to be able to see the attribute "geolocation" in your feedUrl.
Example:
When you execute this query you will see that a new attribute becomes available at the bottom of all your attributes: "distance".
The number you will get back is in meters and is the measurement in a straight line between the coordinates given from the query and the location "geolocation" coordinates. In this case it is 84 meters (rounded up).
4) nearby_ids
“nearby_ids” will essentially do the same as “nearby_latlong” but instead of zip code you are filling in the campaign_id the search will still be geographical nonetheless.
Example:
https://feed.adcombi.com/feeds/yyyymmdd_example?nearby_ids=10139603
5) random
“random” wil give back an amount of random objects, depending on the number after random=. So adding "?random=2", will give back 2 results.
Example:
https://feed.adcombi.com/feeds/yyyymmdd_example?random=1
6) limit
“limit” will set a limit on the amount of objects you’ll get back.
Example:
https://feed.adcombi.com/feeds/yyyymmdd_example?limit=1
7) order
"order" can be used to order a numerical or text value in the feed. The order is always in ASC (ascending).
For ordering the you mention the attribute that you like to order.
Example:
https://feed.adcombi.com/feeds/yyyymmdd_example?order=campaign_id
8) reverse_order
"reverse_order" can be used to order a numerical or text value in the feed. The order is always in ASC (ascending).
For ordering the you mention the attribute that you like to order.
Example:
https://feed.adcombi.com/feeds/yyyymmdd_example?reverse_order=city
9) distance
"distance" will set a maximum limit to the returned items. In other words if you set the distance of 20km, you will only get items back that are in the radius of 20km.
Important! Distance will only work in combination with “nearby_latlong”, as there has to be a distance available.
Example:
https://feed.adcombi.com/feeds/yyyymmdd_example?nearby_latlong=43.89,1.87&distance=20
Note that the distance is always in kilometer, this is the same as the attribute "dist" and "distance" you get back.
Usage limits and policies
At the moment there are no limits on the number of requests set.
There might be other queries available in the future. Let us know if you are missing any like: country, table, query, contains, subject_ids, min/max, indexed_order, prio.