FAQ

  1. How do you get the user’s location?
    The location is delivered from location enabled apps with the ad inventory via RTB to your DSP. The geolocation macro of your DSP then passes the location to the adserver and the adserver delivers the ad with geolocation to the user. When the ad is loaded on the user’s mobile device, it makes an AJAX request to LOCLYS and LOCLYS delivers the geo-personalized slogan.
  2. What is better, mobile web or in-app targetting?
    You should only target in-app, because mobile web delivers too many unprecise locations and is not suitable for geo-personalization.
  3. Is it possible to target users only when they are right next to my shops?
    Technically yes, but not recommended, because you end up with very small audiences. Not all mobile phone users have location identifiers enabled and the cases that you catch a user within a radius of, for example 50m from your shop, are very rare. We recommend setting the radius at your DSP to 5 to 10 km and the max driving time at LOCLYS to 15 to 20 minutes. This allows running campaigns with large enough audiences and it still makes your audience aware that your shop can be reached quickly.
  4. What settings do I need when running a campaign with my DSP?
    If you run campaigns at your DSP as hyperlocal, the user’s location will be passed through and can be used for geo-personalization.
  5. My DSP is not on the list of supported DSPs, what can I do?
    We are working on adding support to as many DSPs as possible. Please contact us in case your preferred DSP is not on the list, we will then add it.
  6. How do you ensure that the location of the user is precise?
    We have a list with unprecise locations which is matched against all incoming user locations. If a location is identified as unprecise, a fallback slogan and a map with all location in this area is displayed, without routing.
  7. I am interested, what is the next step?
    You just need to register and you will then guided through the steps necessary to set up a campaign. Registering and testing is free, up to a limit of 10,000 API calls per week.