Skip to content
- How do you get the user’s location?
Location enabled apps deliver the location with the ad inventory via RTB to your DSP. Your DSP’s geolocation macro then passes the location to the adserver, and the adserver delivers the ad with geolocation to the user. When the ad loads on the user’s mobile device, it makes an AJAX request to StoreBoost, and StoreBoost delivers the geo-personalized slogan.
- What is better, mobile web or in-app targeting?
You should only target in-app, because mobile web delivers too many imprecise locations and is not suitable for geo-personalization.
- Is it possible to target users only when they are right next to my shops?
Technically yes, but it is 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 50 meters from your shop, are very rare. We recommend setting the radius at your DSP to 5 to 10 kilometers and the maximum driving time at StoreBoost 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.
- What settings do I need when running a campaign with my DSP?
If you run campaigns with your DSP as hyperlocal, the user’s location will be passed through and you can use it for geo-personalization.
- 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.
- How do you ensure that the location of the user is precise?
We have a list with imprecise locations that is matched against all incoming user locations. If a location is identified as imprecise, a fallback slogan and a map with all locations in this area are displayed, without routing.
- I am interested; what is the next step?
You just need to register, and you will be guided through the process to set up a campaign. Registering and testing are free, up to a limit of 10,000 API calls per week.