{"_id":"58ac5ac34ca6173b0026a30a","parentDoc":null,"user":"54aa7f3f9bb00c0b00cb899b","version":{"_id":"58aad9dd8f862f250076f9f4","project":"54aa7f773b56130b0056c86e","__v":2,"createdAt":"2017-02-20T11:58:21.765Z","releaseDate":"2017-02-20T11:58:21.765Z","categories":["58aad9dd8f862f250076f9f5","58aad9dd8f862f250076f9f6","58aad9dd8f862f250076f9f7","58aad9dd8f862f250076f9f8","58aad9dd8f862f250076f9f9","58aad9dd8f862f250076f9fa","58aad9dd8f862f250076f9fb","58ac26b3d460ce2500185d26"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":false,"codename":"Locate","version_clean":"6.0.0","version":"6.0"},"category":{"_id":"58ac26b3d460ce2500185d26","version":"58aad9dd8f862f250076f9f4","project":"54aa7f773b56130b0056c86e","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-02-21T11:38:27.587Z","from_sync":false,"order":1,"slug":"using-locate","title":"Using Locate"},"project":"54aa7f773b56130b0056c86e","__v":0,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-02-21T15:20:35.837Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":4,"body":"The following are a list of best practises that you should follow when working with radial geofences, polygonal geofences and beacons in Locate. These best practises are not hard and fast rules and at times it may be beneficial to ignore some of them depending on each individual use case. However, they have ben gathered by the Pulsate team based on years of experience working with lots of different clients and we believe if is essential that anyone working with geofences and beacons are aware of them. \n\n\n[block:parameters]\n{\n  \"data\": {\n    \"0-0\": \"Geofence Size\",\n    \"0-1\": \"Although radial geofences can and do work right down to 100m, we have found that slightly larger geofences tend to get the best results. Therefore, for the best possible results, we suggest that your geofences should be at least 150m-200m.\\n\\nFor polygonal geofences, you can go much lower than 100m as we are using GPS. However, you should ensure that your polygonal geofences are at least 10-15mm in size to maximise their success rate.\",\n    \"1-0\": \"Multiple Geofences\",\n    \"1-1\": \"As much as possible, try not to overlap geofences on top of each other. There are times when this is unavoidable but for the best possible implementation, you should aim to have at least 200m between each individual geofence.\",\n    \"2-0\": \"Geofence or Beacon Naming\",\n    \"2-1\": \"Make sure that you give your geofences sensible names that all of your team understand.  The location of the geofence should always form at least part of the name to make it as easy as possible to identify each geofence in the future.\",\n    \"3-0\": \"Adding New Geofences or Beacons\",\n    \"3-1\": \"Please note that when a new geofence is added to the Pulsate CMS, each user must open the app and start a Pulsate session (this usually happens automatically) so that they can pull down the updated list of geofences or beacons to monitor for.\",\n    \"4-0\": \"Permissions\",\n    \"4-1\": \"For you to monitor for geofences and beacons, all of your app users have to accept permissions from Android and iOS. Therefore it is important that you build an on boarding experience to explain why users should accept your permission. For more information, see our guides on [permission priming](http://academy.pulsatehq.com/permission-priming-mobile-app-users) and [app user onboarding](http://academy.pulsatehq.com/app-user-onboarding-how-to-get-more-signups)\"\n  },\n  \"cols\": 2,\n  \"rows\": 5\n}\n[/block]","excerpt":"","slug":"locate-best-practises","type":"basic","title":"Locate Best Practises"}

Locate Best Practises


The following are a list of best practises that you should follow when working with radial geofences, polygonal geofences and beacons in Locate. These best practises are not hard and fast rules and at times it may be beneficial to ignore some of them depending on each individual use case. However, they have ben gathered by the Pulsate team based on years of experience working with lots of different clients and we believe if is essential that anyone working with geofences and beacons are aware of them. [block:parameters] { "data": { "0-0": "Geofence Size", "0-1": "Although radial geofences can and do work right down to 100m, we have found that slightly larger geofences tend to get the best results. Therefore, for the best possible results, we suggest that your geofences should be at least 150m-200m.\n\nFor polygonal geofences, you can go much lower than 100m as we are using GPS. However, you should ensure that your polygonal geofences are at least 10-15mm in size to maximise their success rate.", "1-0": "Multiple Geofences", "1-1": "As much as possible, try not to overlap geofences on top of each other. There are times when this is unavoidable but for the best possible implementation, you should aim to have at least 200m between each individual geofence.", "2-0": "Geofence or Beacon Naming", "2-1": "Make sure that you give your geofences sensible names that all of your team understand. The location of the geofence should always form at least part of the name to make it as easy as possible to identify each geofence in the future.", "3-0": "Adding New Geofences or Beacons", "3-1": "Please note that when a new geofence is added to the Pulsate CMS, each user must open the app and start a Pulsate session (this usually happens automatically) so that they can pull down the updated list of geofences or beacons to monitor for.", "4-0": "Permissions", "4-1": "For you to monitor for geofences and beacons, all of your app users have to accept permissions from Android and iOS. Therefore it is important that you build an on boarding experience to explain why users should accept your permission. For more information, see our guides on [permission priming](http://academy.pulsatehq.com/permission-priming-mobile-app-users) and [app user onboarding](http://academy.pulsatehq.com/app-user-onboarding-how-to-get-more-signups)" }, "cols": 2, "rows": 5 } [/block]