Places are shared across apps within ONE organization, so different teams within one organization can access the same Places that have been built. Note that Places CANNOT be shared across multiple organizations, so you will need to create them separately for each organization. Places can be created and edited by any account type, so there are no locks or restrictions once Places have been created.
Naming is important for Places as they could reflect multiple attributes of your Place. Is your Place a simple geofence? Is it radial or polygonal? A group of beacons? Depending on what is in your Place should be accurately reflected in the Place name. (see Beacon & Place Naming Best Practices Guide)
- Create and consistently use a standard naming convention to avoid misunderstandings and issues if/when there is turnover in the department managing the Proximity/Location solution. Some recommended naming convention templates and examples are provided below.
- Determine what information is important to you and your management team to designate where is each Beacon or Place and what they are used for. Some examples of this type of information are the following: Brand Name, Store Name, Store #, City, Department/Location, etc.
- The names you use will appear in your Gimbal Manager Analytics/Dashboards and should be clear and quickly understandable at a glance by your IT, Marketing, Ops, and senior management teams. You should include only the minimal information needed in the Beacon or Place name to distinguish it as a unique location and nothing more. If a name gets too long, it can be truncated or overlap with other names in the Analytics/Dashboards, causing confusion and slowing the interpretation of the data being presented.
Creating Places for competitors’ locations is a fairly common practice with our customers. When creating Places for competitor locations or multiple brands, it’s important to designate which brand the Beacon or Place is being used for in the name. Otherwise, it can become difficult to filter the Analytics/Dashboards to see only certain competitor or brand location information.
Ultimately, the information you include in your Beacon and Place names will be unique to your company and will include what’s most important to you and your management team. We’ve provided some best practices and recommendations above and some templates and examples below to assist you in quickly setting up your Beacons and Places in your Gimbal Manager account. Hopefully, this advice will allow you to get the most from your Analytics/Dashboards in Gimbal Manager and quickly get you the data and insights you’re looking for from our Proximity and Location Solution. Good luck with your implementation and hope that this information will allow you to be successful in your Proximity/Location marketing efforts!
Geofence Place Name Template: [Brand Name]-Geo-[Store #]-[Store Name or City]
- Ex 1: JT Apparel-Geo-1123-LA Galleria
- Ex 2: Toms Supply-Geo-987-Miami
Beacon Name Template: [Brand Name]-[Store #]-[Store Name or City]-[Department Name or Location]
- Ex 1: JT Apparel-1144-Long Beach-Kids
- Ex 2: Toms Supply-912-Village Center-Front Door
For large geofence rollouts, is it best to use radial or polygonal geofences?
Radial is the easiest to scale and what most retailers use. Gimbal offers a premium geofence offering in which Gimbal pre-builds polygonal geofences, if polygonal is preferred. Most retailers will use large (200-500m) radial geofences around a central lat/long if the goal is to drive traffic to those areas. This can also be done with polygonal though radial is easier to scale.