Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Right and Wrong Ways to Use Geofencing

DZone's Guide to

The Right and Wrong Ways to Use Geofencing

For apps that have any sense of location awareness, geofencing can be a really useful addition. However, with great power, comes great responsibility

· Mobile Zone ·
Free Resource

As marketers who know our way around apps, we understand that users expect a personalized experience. Now with the launch of location-based capabilities? It’s official: personal’s in, generic is out — way out. Broad, generic messaging that feels like a robot churns them out all day just won’t cut it anymore. Users want experiences that are relevant to them.

Along with beacons and geotargeting, geofences make up a group of powerful location-based marketing tools that are changing the way marketers connect with their users. And like Pokemon Go just proved, users are more than ready for the right kind of location-based marketing.

"Tell me again: What are geofences and how do they work?"

Geofences are virtual fences placed around a real-world location. Create them around brick-and-mortar businesses, big industry events — wherever you want. When a users enters or exits a geofence, it triggers a push notification you can target to where they are at that moment, increasing engagement.

But with great power comes great responsibility, and you want to make sure you’re creating geofences that offer real value to users. Our Dos and Don’ts of Geofencing cheat sheet has tips you need (and the mistakes to avoid) so you can create geofences that make a difference to your mobile marketing.

Check it out below:

geofencecheetsheet.jpg

Download it here!

Are you using geofencing in your mobile app marketing strategy yet? Tell us how in the comments.

Topics:
app ,geofencing ,geotargeting

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}