This guide gives a detailed introduction to create a proof of concept and how to set up a pilot before going into production. Feel free to contact firstname.lastname@example.org for further questions.
You should keep on reading if you want to:
- Run campaigns using beacons or geofences
- Set up location-based services at the point-of-sale
- Collect location data with your own mobile apps
- Integrate location data into your marketing or CRM solution in real-time
Sign up for a Proximity DMP trial account at www.proximitydmp.com to get access to the dashboard and to manage your beacon and geofence infrastructures and proximity campaigns.
If you don't own a mobile app you can directly jump to the NFC/QR section. Your end users do not require an app to tap on the NFC tags or scan the QR codes as part of your campaign.
If you are interested in app-based solutions download the:
Open this app and login with your Proximity DMP account (Request access if you don't have an account) or enter your API token. In the Proximity DMP web client under Settings --> Application you will find your API token that authorizes mobile apps to retrieve data. You have to keep this token private. It's easier to directly scan the QR code.
After testing with the Proximity App you can also directly download the mobile SDKs for iOS or Android from Github. Integration effort is typically only a few hours plus testing. Make sure you check out the READMEs to get a full feature overview.
The same account as for the proof-of-concept can be used. You can also set up a new DEV vs. LIVE access token under Settings --> Applications.
Under Infrastructure -> Beacons you can quickly add your beacon by clicking the + button. If you ordered beacons from Beaconinside we can automatically import all your beacons with the correct settings.
For beacons and geofences you can add meta data. This simplifies the handling and integration into 3rd-party systems, e.g. StoreID=123, Zone=Cashier, ERP_ID=123.
Testing geofencing is as simple as setting up a 100-150m geofence in Infrastructure --> Geofences.
See also the complete geofencing guide.
Nearly everything you can do with beacons you can also do with geofences but with less location accuracy. It's recommended to test beacons along geofences.
Proximity campaigns are used to define interactions between mobile users and beacon or geofence zones. Campaigns include a notification message when entering a zone and a target action like an image or a custom in-app landingpage. You can also define your own scheduling and additional targeting criteria like the day of the week or the mobile operating system. Select the All Beacons or All Geofences group to create a trigger event. With the help of groups you can flexible create various campaign triggers, e.g. a zip code area, all shopping windows or all entrances.
Go to Marketing --> Campaigns to create a new one. Campaigns require a mobile SDK integration.
Test your campaigns with Demo app
Once you setup beacons and set the appropriate campaign live, the end user will still require an app (with our SDK) to receive the notifications. If your app is not ready yet, you can use the aforementioned Proximity App for demos.
Under Analytics you'll find various charts to show what's going on.
It's possible to use collected visitor data to create your own dashboards if needed.
You can also easily do custom analytics with business intelligence tools like Tableau.
Unfortunately Nearby Notifications has been deprecated by Google since December of 2018 (Read more).
NFC tags are low cost and can be attached to products or objects. Your mobile app can interact with your tags and the customer profile can be enriched with product-level interests. NFC tags can be linked to web pages (e.g. product info pages) that are opened directly within the application.
QR Codes can store contact information, venue details, an image or a URL to your landing page. When printed, they can be deployed immediately since all one needs is a smartphone with a camera to scan it.
Check here for more details: NFC/QR campaigns
How do I ensure everything is set up in the right way?
- Check if the beacon is turned on and can be detected with the Proximity App.
- Grant location and notification permissions within the application (typically at app start)
- Check if device is online (to request beacon and campaign content)
- Android: Enable Bluetooth on your device (not required with iOS 11+)
- iOS: Check in App Settings if Background App Refresh is active
iOS: Did you provide the right app permissions? (in Settings > App)
What is the battery drain of the SDK?
In short, below 1-2% of the daily energy usage. See the battery drain guide.
|Proximity DMP Introduction|