Movintracks dashboard user guide

This document will help you with the configuration of campaigns in the Movintracks dashboard. Please don´t hesitate to contact the Movintracks team at if you need any help or have any questions. You can also sign up for our next live tutorial on this page: You can watch a 2 minute video overview to get you started.

The directions in this document cover the main actions you can take in the Movintracks dashboard. However, rather than explain every feature exhaustively, its purpose is to give enough information so you are comfortable with the first steps of the campaign creation process.

Please use the username and password given to you in advance by the Movintracks team.

Main navigation menu

The Movintracks dashboard has been designed around usability: we tried to create an easy-to-use, simple working space that anyone can use.


This is why the main navigation menu has only five options:

  1. Campaigns: configure the interactions that will happen on the user’s device.
  2. Points: configure the interest points where the Beacons will be installed.
  3. Reports: get information and monitor the campaigns.
  4. Profile: configure the main settings.
  5. Wake up devices: send a signal to all mobiles with the app installed to download new campaign content.


Of the five menu options, two of them are the ones used to activate the interactions with the user’s device. In “Points” you can define the Beacons/NFC areas of interest and you can give the areas an easy-to-remember name. “Campaigns” is where you can configure the interactions and set up where they will be triggered.

The “Profile” section is used to adjust general settings such as the branding (logo, corporate colors, etc.) and the brand’s social profiles.

The “Reports” section gives you access to the statistics of the interactions done by the users, such as most visited points, stay time, survey answers, redeemed coupons, etc. All this information is presented both with graphics and data tables.

Finally, ‘Wake up devices’ is a button that allows the user handling a campaign to send a signal to all mobiles with the app installed to download new campaign content. When used, any changes made up to that moment will be stored on users’ device caches, as the download is initiated wherever the user is, even if they are not close to the area where the campaigns are programmed to take place. Due to limits put in place by Apple in the communications system used to make this functionality possible on iOS, this feature may only be used once every 24 hours.

When you access the dashboard you will be presented with a list of all the active campaigns. From this page you can also create new ones and modify or delete the existing ones. You can also access the expired and future campaigns.

How to create a campaign

Now that you are familiar with the different options of the main menu, we will cover the process of creating a new campaign.

1) The first step is to verify that the UUID in the “Profile” section matches the one given to your company. The Movintracks team will have set it up in advance in your “Profile”, so at the beginning this parameter should be the right one by default. If you don’t know the UUID for your Beacons, please contact the Movintracks team.


2) Create as much as points as you want. Each point needs to have at least one Beacon, but you can have more if you want to cover a bigger area or add specific points of interest. You can create points and zones in the “Points” section.


Points are grouped into “Zones”. Assigning a point to a zone is mandatory and will help you find the points when creating a campaign. Each zone can be linked to a real geographical area (a “geofence”). The general use case will be creating a zone for each of the locations your company has. This allows battery saving for both the Beacons and the user’s device, as Beacons will not be listened to if the user is not close to the geographical area you set up. And you can even deliver an interaction to a user when the user enters or leaves into a geofence (an your user don’t have to have the bluetooth turned on). You will need to create at least one zone before setting up a point.

When a user crosses the boundary of a geofence you can send them any of the Movintracks actions (or a couple of them), but this will come later, when creating the campaign. The checkbox “Send message when user enters geofencing” have another use case: if you click it, it allows you to define a message that will be delivered to every user entering in the geofence with the bluetooth disabled. This is your chance to convince the user to turn on bluetooth, if needed for your campaign.


When you create a point you have to specify its type: “Register” will be used if the point is the cash register, and “Entrance” if it is an entrance or exit point. In most cases, or if you are not sure about it, you should use use the “Regular” type.


If no zones are set up, you must do so before creating a point. You can create a zone by accessing the “Points” section, clicking the “Zones” tab and pressing the orange “New Zone” button.

3) After this you can create the first campaign (i.e. a specific interaction). To do so, click on the “Campaigns” section in the menu and then click the orange “New campaign” button you will find in the top right corner.


The field “Campaign name” lets you assign a name to the campaign. This name will be used on the users’ device when notifications are sent.

You can also set up a start and an expiration date of the campaign. Once the expiration date is over the campaign will stop having an effect and it will be listed in “expired”.


The “Campaign delivery” field is used to define whether the campaign will be served only once to each user, or more than once. If the last option is chosen, a delivery frequency can be set up in minutes, hours or days.


Campaign settings: triggers and actions

What are triggers and actions?

When setting up an interaction, we distinguish between triggers and actions. “Triggers” define which behavior the user of the device must occur for the campaign to be triggered, and “Actions” are the interactions the users receive in their devices: a coupon, product information, etc.

As you will see the default trigger is “On visit”. Each interaction needs to happen in relation to the user getting close to one of your defined zones or points. For example, If you want to trigger a campaign when the user enters your controlled area, you can put a beacon in your entrance, create a point, name it “entrance”, and finally choose the point named “entrance” for your campaign.


When you click the “Zone” field, it will display the list of zones you set up in the “Zones” section. When you click one of these zones, it will be linked to this campaign, so the campaign will be triggered when the user gets close to this zone. Please keep in mind that the underlying technology used here, geofencing, has its limitations. It shows its best results when you define zones that have at least 200 meters of radius. Its precision depends on a couple of factors: it’s more quick in responses if the user have Wi-Fi, GPS or both turned on, but can work if it’s not the case in a lot of devices (usually better in cities than in rural areas). Users don’t need to have the Bluetooth enabled to get this kind of interactions.

When a zone is selected, a “Proximity campaign with beacons” checkbox shows up. In case you would like your campaign to be more precise it’s a good idea to check it: then your campaign will run with beacons instead than with geofencing, so you can be very precise (but your users need bluetooth enabled to get campaign’s content).

What beacons will trigger your interaction? When you click the “linked points” field, it will display the list of points you set up in the “Points” section, filtered by zones. When you click one of these points, it will be linked to this campaign, so the campaign will be triggered when the user gets close to this point. More than one point can be linked to a campaign.


The “proximity” field is used to set up the distance from the Beacon the campaign will be triggered in. You can choose between “immediate” (very close distance), “near” (medium distance) and “far” (any distance inside the range of the Beacon). On Android devices, this will work for applications running both in the foreground and the background. On iOS (Apple) devices, it will work only if the app is in foreground, but in background mode they will always be launched as if the “far” value was selected. This is a restriction imposed by the operating system. If you need to achieve a similar functionality in iOS, you need to change the maximum range of the Beacons. Please do not hesitate to ask for help from the Movintracks team at


The “NFC” field is only available to the users who bought Near Field Communication tags through Movintracks. It allows you to run actions when the user moves their device close to one of the NFC stickers and functions only for devices that have the appropriate hardware. One of the advantages of using NFC is that the user does not need to have an installed application to receive the interactions. The user consent is implied when they move their device near the NFC tag.

Other triggers

You can also set up extra conditions that will affect whether the specific campaign will be delivered to a specific user. Apart from having the user visit a point, you can also choose from one of the following triggers:


  • Point not visited: this trigger determines whether the campaign will be delivered or not based on the previously visited points by the user during the same experience. You can specify a point and if the user did not previously visit it, the campaign will be delivered.
  • Social follow: campaigns with this trigger will only be delivered to followers of your brand’s page on one of the social networks you specified in your “Profile”. If they are not already followers, they will be asked for permission. If the user does not authorize access to their social profiles, or there is any privacy setting that prevents access (especially in Android), the campaign will not be delivered to the user.
  • After a certain time: the campaign will be delivered to the user after the specified time has passed after they visited the point, regardless of whether they are still visiting the point or not.
  • At time: the campaign will only be delivered if the interaction time is between the defined slot, such as 3-4pm.
  • Target specific customers: it’s Movintracks’ most flexible trigger. It allows you to define what particular users should get your campaign. It can be a single one or a couple of ones. When used in conjunction with a customer relationship manager (CRM) it’s even more powerful: you can search in your CRM for a group of people, get the Movintracks user id of each one, and use it as a comma-separated list of users in the target specific customers trigger of your campaign. For this to work, you need tell your app that it should send the user ID of each user (when the user log in) to the CRM, to make the matching possible. This way you can target specific customers without revealing to any third party (not even Movintracks!) any personal detail from your users and clients. You typically would like to use Movintracks REST API to work with that plugin. Learn more on how get all devices through this API.

Triggers are accumulative, so all the defined trigger criteria must be met for the campaign to be delivered. For example, you may want to deliver a campaign only if the user visits a specified point of interest, follows your Twitter account, and the current time is between 2-4pm.

Once you set up the conditions that need to be met to deliver (or not to deliver) a campaign to the user, the next step is deciding which actions you want for the campaign.


The Movintracks dashboard has the following built-in actions:


Deliver coupon

Use this action to deliver coupons to the user to reward their interest and loyalty.

The dashboard includes a content management system (CMS) that will allow you to generate customized coupons with your brand colors and logo. If you set them up in your “Profile” section they will be pre-loaded in the form, but you can always modify the values.


In case the brand has their own coupon generation and redemption tracking system, the Movintracks API allows massive coupon uploads so they don’t have to be created manually, one by one.

You can also configure how the coupon is going to be redeemed. By default the coupon has a QR code, and scanning it can either show whether the coupon is valid or not, or can also show a EAN barcode to be used together with your barcode reader.


Movintracks can also create coupons with a barcode instead of a QR code. Due to limitations in the Passbook specifications, only HTML coupons can be served with a barcode. Coupons with barcodes are only available by demand. Again, do not hesitate to contact the Movintracks team at for more information.

Both in iOS and Android, the Movintracks SDK serves Passbook coupons whenever possible. If it is not possible, it opens a view inside the app containing the HTML version. There could be a number of reasons why Passbook coupons could not be delivered. The most frequent of them is that the user does not have a Passbook-ready application on their device. This happens more often with Android systems.

Show product info

Use this action to show the user a product information page.


There are two ways to display the product information. You can either create a static page (consisting of a heading image, title, and a visual text editor), or provide a EAN barcode number to be queried to the GS1 database: if product information is available it will be automatically loaded.

If you need more flexibility than provided for product information pages, we would recommend creating a HTML page, uploading it to a web server, and deliver it to the customer using the “visit URL” action.

Show alert

Use this action to create notifications that will be delivered to the user in a similar fashion as the push notifications.


Apart from the notifications you set up in the campaign using this actions, end users will also receive other notifications generated by the Movintracks SDK. For example, if the user has the device screen locked but meets all the criteria to receive a campaign, they will be sent a notification informing them that a campaign is available, which will be delivered when they click on it. For this reason, it is not necessary for you to set up specific notifications to inform the user a campaign is available for them.

Download vCard

Use this action to send the user a virtual business card using the vCard specification. With one click the user will be able to add the received contact information to their device’s contacts book.


You can either upload an existing vCard file, created with an external tool, or you can fill out the form displayed on the Movintracks content management system. The Movintracks API also allows you to programmatically create and upload vCards.

Visit URL

Use this action to show a website on the user’s device. It will be opened in a web view inside the brand application, so no external browser needs to be loaded. If there is another action set up after this one, the second action will not be shown to the user until they close the web view.


Launch app

Use this action to open an installed application on the user’s device. You can also use it to display a specific section, view or functionality inside that application, if the application to be opened supports custom URL schemes. You can get more information on URL Schemes on the Apple
Developer website: Introduction.html


To know more about URL Schemes and the limitations of the app you want to launch, please check with the application developer team or contact our technical service.


Use this action to make the user’s phone vibrate.


Show survey

Use this action to create a survey and deliver it to the end user. You can upload an image to customize the look and feel. Surveys consist of a question and at least two answers, and also need an identifying name.


The user will be able to select one of the answers, and you can view the results and statistics in the “Reports” section of the dashboard.

If you have your own survey system outside Movintracks, you might be interested in generating publicly accessible URLs and using the “visit URL” action to deliver them to the user.

Show audio

Use this action to deliver an audio message to the customer. Currently audio files have to be hosted on SoundCloud.


Show video

Use this action to display a video to the customer. Currently video files have to be hosted on either YouTube or Vimeo.


Show image

Use this action to show an image to the customer. Additionally you can set up an accompanying text and link.


Visit social profile

Use this action to display one of your brand’s profile on a social network to the end user. Remember you can set up your social profiles in the “Profile” section of the dashboard.


Unlike the “Follow social profile” action, this action displays the wall / timeline of the specified profile but does not invite the end user to follow it.

Follow social profile

Use this action to invite the end user to follow your brand’s profile on a social network. After they do so, users will get your brand’s messages in their own “newsfeed” or “timeline” on the social network.


If you want to display your own social profile and its publications directly to the user, the “Visit social profile” action is more suitable for you.

Post message social

Use this action to post a message on the end user’s social profile (not the brand’s own), after they give their consent. Messages can consist of text with an optional link and image.


This action will not run if the user’s device has any privacy setting that prevents it.

Post image social

Use this action to post a user-taken picture to their own social profile (not the brand’s own). Image will be either chosen from their camera roll, or taken in the same moment using the camera.


This action will not run if the user’s device has any privacy setting that prevents it.

Custom app callback

‘Custom callback app’ is an action that allows you to launch any functionality that is developed within an app that includes in the Movintracks SDK just like any other action on the dashboard. This way, certain features of an app can be launched at any given time thanks to Movintracks’ triggers, or be activated between one action and the next when context requires.

Final steps

After deciding the actions you want to launch on the user’s phone, you will get a summary with all the campaign information. Please check to ensure all the data is correct before confirming, and make changes if necessary.



In this section you can view the statistics from all of the current and expired campaigns.


Campaigns: information about how many campaigns have been delivered.


Points: number of visits in the points assigned to each campaign (number of visits and average visit length).


Social profiles: information about the number of new in-place social follows.

Visits: information about the number of visits, average length and other related information.


Coupons: information about the number of delivered, used and invalidated coupons.

Surveys: information about the number of answers and percentage of each one.

Short URLs: information about the number of visits got it in each of the URLs sent through the SDK and API.


If you would like to know more details about how this technology works or better understand some of the concepts, please read the definitions provided in this section. Do not hesitate to contact the Movintracks team at for any further help.


Hardware devices that send a signal (Wi-Fi or Bluetooth) that allows an app to know which indoors or outdoor area a device is located more precisely than standard geolocation. Not all the beacons in the market are Beacons. The Beacons are beacons that work with Bluetooth 4.0 and follow a specification given by Apple, but they can also work with Android devices, Windows Phone, some Blackberry devices, etc. Only Beacons can launch an app in background mode in iOS (Apple devices), so Movintracks works mainly with this hardware. However, Movintracks can also work with other beacons, Wi-Fi devices and other microlocation systems. Please contact us at for further information.


Triggers are conditions needed to be met for a campaign to be delivered. The manager who sets up the campaign decides a series of behaviour rules that must be accomplished for the campaign to be delivered to the end user’s device. For example, these conditions could be: when a user passes by a point of interest; when a user walks by a point of interest and has not visited another point; when the user follows the brand profile on a social network, etc. This way, triggers define the user behaviour that must be met.

For more information about how triggers work, check the triggers section in this tutorial.


Actions are pieces of content or interactions that happen in the user’s device when all the triggers have been met. Actions are delivered as part of the campaign set up by the manager in the Movintracks dashboard. Examples of actions are: deliver a discount coupon to the user, show a product information page, send a notification or vibrate.

For more information about how triggers work, check the triggers section in this tutorial.


UUID is one of the three uniquely identifying values Beacons have, together with the major and the minor. A UUID identifies all the Beacons of the same brand. For example all the Beacons of “company x” will have the same UUID. This way, a dashboard user can only set up one UUID. An UUID is a string of characters (numbers and letters) separated by a dash, in the following format: { 8 characters} dash {4 characters} dash {4 characters} dash {4 characters} dash { 12 characters}. UUIDs are generated randomly so the probability of collision between two different brands is extremely remote. If this should happen, it would only cause conflicts if the end user has both applications expecting to run campaigns with the same exact beacon configuration, which is an even more remote possibility.


Major is one of the three uniquely identifying values Beacons have, together with the UUID and the minor. In order to get the expected functionality, especially for technical reasons when the app is in background mode, we recommend having up to five different major values for the Beacons in the same location, and placing the Beacons in a way that two nearby beacons do not have the same major value.


Minor is one of the three uniquely identifying values Beacons have, together with the UUID and the major. As all Beacons for the same brand have the same UUID (we recommend a maximum of five different major values), the minor value is used together with the other two to uniquely and precisely identify each of the Beacons.


API is an acronym for Application Programing Interface. It is used to connect the marketer’s own dashboards or solutions to Movintracks, allowing creation and editing of campaigns and contents. To big retail businesses, for example supermarkets, it also allows integration with their own CMS (customer relationship management system), analytic motor or big data solution. They can access and process the statistical data gathered by Movintracks, and effectively combine this information with their own.


SDK is an acronym for Software Development Kit. It is a small file provided by Movintracks that app developers can easily bundle in the brand’s own application. The SDK automatically connects with the Movintracks API and automatically does all the campaign and content delivery to the user, making it very easy to integrate Movintracks to existing apps or to create a new app for the brand.

Project MovinTracks is based on AI technology