Quick Start

This page will guide you through the process of getting started with the proximity platform and receiving your first Splash Push Bluetooth beacon or region notification.

Download the app

To use beacons and geo-fences (regions), you need the Splash Push mobile app. The app is basically a browser you can use for mobile sites (apps) and landing pages created with the proximity platform or any other content you’re hosting online.

Information on where to download and how to use the app, can be found on our website or within the portal.

Prerequisites

Before we can start using the app’s proximity features, we need to add a beacon, a mobile site or landing page and a scenario board to the Proximity Platform.

Beacons

Go to Proximity > Beacons and click the New beacon button at the right top. Here we can enter the UUID, major and minor of the beacon. Usually, you can retrieve these settings with the app of your beacon vendor. You can also call Cisco Meraki support and they can add the UUID and unique major / minor details to all your Ap’s.

For ease of management, it’s recommended to use the same UUID for all your beacons and differentiate between beacons with the major and minor numbers.

Regions

If you don’t have any Bluetooth beacons, you can use regions. Go to Proximity > Regions and click the New region button at the right top. Here we can manage the location and radius.

When testing regions, you need to move a couple of meters (in case of iOS even a lot more) in order to trigger geo-fence changes.

Mobile site

For now we’re going to add a mobile site instead of a landing page, but both are possible. Mobile sites are called apps in the Proximity Platform. That’s because there’re a lot of similarities between these mobile sites and hybrid apps.

Create a mobile site at Apps > Apps and click the New App button at the right top. Follow the instructions and create at least one page for the app. A simple content page like About Us is enough.

Scenario board

A scenario board brings the beacons and mobile sites and landing pages together. When creating a scenario board, you can select the mobile site (app) we’ve just created. You can add or remove apps at Scenarios > Edit scenario board > Options > Board settings.

Scenarios

Now all prerequisites are met, we can add a few scenarios to test our beacons or regions. Make sure that if the Bell icon (between the If someone and Location columns) is visible, you enter a notification text. If there’s no text, the scenario won’t be triggered in the app. Also make sure there is content available at the Then column. Depending on the type of content selected, an icon will show between the Then and When columns. Click this icon and select or enter the content you want to show.

If you’re testing regions, be aware of the fact they behave differently per device by design (Android or iOS). You need to move at least a couple of meters on Android in order for the region to be triggered, and on iOS it can be up to a hundred meter (or more).

Finally, make sure the app has the right permissions. Allow the app to access your location even when you’re not using the app, allow permission to receive push notications and make sure Bluetooth is enabled.

If you use the enter or exit region scenarios, make sure you have a notification text at the Bell icon, or nothing will happen.

Some example scenarios.

To test these scenarios with the app, go to Apps > Edit App > Options > QR code. Scan this QR code by tapping the QR scanner icon in the SplashPush app

You can also enter the code. The code of a mobile site or landing page, is the last part of the url. In the case of https://portal.splashpush.com/mobile/XYTT-J4LS-625-U4NV, the code is XYTT-J4LS-625-U4NV.

Of course this is tedious for an app user to enter, so you can change this to for example DISCOUNT10 or ADVENTURE by updating the domain when editing a mobile site or landing page at Options > App settings (or Website settings) > Domain.

     

Scenarios Timings

A scenario Timing is set at the moment to milliseconds . This is the Amount of milliseconds that must pass in order to retrigger this scenario. This is defaulted to 1 hour but can be changed at Scenarios > Edit scenario board > Options > Board settings > Timming.