{"_id":"5c52c6500b42b6003f4efebb","project":"54aa7f773b56130b0056c86e","version":{"_id":"576a656c6f15260e001f8938","__v":3,"project":"54aa7f773b56130b0056c86e","createdAt":"2016-06-22T10:16:12.661Z","releaseDate":"2016-06-22T10:16:12.661Z","categories":["576a656c6f15260e001f8939","576a656c6f15260e001f893a","576a656c6f15260e001f893b","576a656c6f15260e001f893c","576a656c6f15260e001f893d","576a656c6f15260e001f893e","576a656c6f15260e001f893f","5797787ce2d8f40e0052b4a6","5b041bc0769904000374c645"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":false,"codename":"For Marketers","version_clean":"4.0.0","version":"4.0"},"category":{"_id":"576a656c6f15260e001f893a","version":"576a656c6f15260e001f8938","__v":0,"project":"54aa7f773b56130b0056c86e","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-01-05T12:25:25.590Z","from_sync":false,"order":3,"slug":"working-with-pulsate","title":"Working with Pulsate"},"user":"5bf2ee36be2bc3003811336e","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2019-01-31T09:56:32.449Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":4,"body":"**What is a beacon?**\n\nA beacon is a simple device that transmits a bluetooth signal. The bluetooth signal typically includes the following data: \n\n       UUID - a unique identifier for each beacon\n\n       Major - a custom identifier that is typically used to determine the macro location of the \n       beacon (ie \n       which store in a retail use case)\n\n       Minor - a custom identifier that is typically used to determine the micro location of the beacon \n       (ie where the beacon is located within the store for a retail use case)\n\nMobile devices can monitor for beacons and this allows us to track various metrics including customer footfall and visit frequency. Users within a beacon zone can also be sent individually targeted marketing communications based on their location. This is much more granular than geofences which can only send content to users when they are within 100m of a location. \n\nBeacons, on the other hand, can target users within a couple of metres or less of a specified location. \n\n**To add a Beacon to your Pulsate account.**\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"UUID Upper Case\",\n  \"body\": \"Please note that the beacon UUID must be added to Pulsate in uppercase only.\"\n}\n[/block]\nTo add a beacon to your Pulsate account, simply click on ‘Locate’ in the top navigation bar followed by the 'New Beacon’ button as indicated below.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/e894da5-ConverseBeacons.png\",\n        \"Converse:Beacons.png\",\n        1280,\n        624,\n        \"#dadce0\"\n      ]\n    }\n  ]\n}\n[/block]\nThis gives you options for uploading a .CSV file or adding a beacon manually.\n(Note: Pulsate no longer supports providing beacons to clients). \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/68bfdbb-Selecting_how_you_would_like_to_add_a_beacon.png\",\n        \"Selecting how you would like to add a beacon.png\",\n        926,\n        272,\n        \"#dcdcd5\"\n      ]\n    }\n  ]\n}\n[/block]\n**Adding Beacons Manually:**\n\nClick Add Manually and fill out the following fields for each beacon: \n\nBeacon Nickname: - a custom Pulsate identifier for each beacon that is typically the location of the beacon \nBeacon ID: - a custom Pulsate identifier for each beacon that is typically a unique identifier for the beacon added by Pulsate clients\nMajor\nMinor\nUUID\n\nWhen all of the fields have been filled in, click Save to add the beacon to Pulsate. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/713bf47-Adding_a_3rd_party_beacon.png\",\n        \"Adding a 3rd party beacon.png\",\n        935,\n        305,\n        \"#373737\"\n      ]\n    }\n  ]\n}\n[/block]\n**Adding Beacons By .CSV:**\n\nUpload a .CSV file in the format of: UUID, Major, Minor, Beacon ID, Nickname\n\n\n**How to Edit a beacon?**\n\nHover over the edit button of the beacon you wish to edit and select ‘edit’ from the drop down. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/529295b-Edit-Delete_Beacon.png\",\n        \"Edit-Delete Beacon.png\",\n        697,\n        282,\n        \"#ecf1f2\"\n      ]\n    }\n  ]\n}\n[/block]\n**How to delete a beacon?** \n\nFrom your list of previously created beacons, hover over the edit button of the beacon you wish to delete and select ‘delete’ from the drop down. You will get a confirmation message in advance. To the right of the bar, a delete icon will appear. Clicking the 'x' will remove the beacon. You will be asked to confirm if you would still like to remove it. If so, choose ‘delete’. If not, press ‘cancel’.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/a781328-Beacon_deletion_warning.png\",\n        \"Beacon deletion warning.png\",\n        548,\n        225,\n        \"#5d7f78\"\n      ]\n    }\n  ]\n}\n[/block]\n**Check Status**\n\nSometimes beacons run out of battery or need to be replaced for a host of reasons. To help identify when a beacon might need to be checked, Pulsate operates a traffic light system. If Pulsate has received an event for the beacon within the last week, a green traffic light symbol will be visible for that beacon. If no event has been received for a beacon within the last two weeks, that symbol will be changed to amber and if no event has been recorded for a beacon for over two weeks the traffic light symbol will change to red. \n\nIt is good to keep an eye on the status of individual beacons and to proactively check any beacons that have an amber or red traffic light symbol. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/005d9c7-Beacon_-_Traffic_Light_System.png\",\n        \"Beacon - Traffic Light System.png\",\n        847,\n        304,\n        \"#dbdce2\"\n      ]\n    }\n  ]\n}\n[/block]\n**Exporting Beacon Data **\n\nPulsate has a number of different methods for exporting beacon data to help you measure footfall and visitor frequency. To export beacon data from the Pulsate CMS, go to the beacon section and click “Export All”\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/1f51d90-Export_Beacon_-_Date_range.png\",\n        \"Export Beacon - Date range.png\",\n        850,\n        294,\n        \"#eaeaed\"\n      ]\n    }\n  ]\n}\n[/block]\nYou will then be prompted to choose a timeframe for the beacon export  (the default period is 1 month) and when that is selected you can click “Export” and Pulsate will compile the necessary data and send an email to the admin who is currently logged in with a csv attachment that includes all of the beacon events for the time period that was specified. \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/423bcce-Beacon_-_Export_started.png\",\n        \"Beacon - Export started.png\",\n        282,\n        111,\n        \"#d9ebf2\"\n      ]\n    }\n  ]\n}\n[/block]\nIn addition, Pulsate can also automatically send any beacon events that are recorded to a url of your choice via webhook. As soon as a beacon enter or exit event is recorded by Pulsate. it will be automatically sent to the specified webhook. To enable this feature, click Settings and then App Settings in Pulsate and scroll down to the Webhooks section. \n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/4ae12b4-Webhooks__Save.png\",\n        \"Webhooks & Save.png\",\n        1147,\n        428,\n        \"#e6e6e5\"\n      ]\n    }\n  ]\n}\n[/block]\nSwitch the toggle to ON and then enter a url where you would like Pulsate to send beacon events. \n\nThen scroll down to the bottom of the App Settings page and press Save.","excerpt":"","slug":"beacons","type":"basic","title":"Beacons"}
**What is a beacon?** A beacon is a simple device that transmits a bluetooth signal. The bluetooth signal typically includes the following data: UUID - a unique identifier for each beacon Major - a custom identifier that is typically used to determine the macro location of the beacon (ie which store in a retail use case) Minor - a custom identifier that is typically used to determine the micro location of the beacon (ie where the beacon is located within the store for a retail use case) Mobile devices can monitor for beacons and this allows us to track various metrics including customer footfall and visit frequency. Users within a beacon zone can also be sent individually targeted marketing communications based on their location. This is much more granular than geofences which can only send content to users when they are within 100m of a location. Beacons, on the other hand, can target users within a couple of metres or less of a specified location. **To add a Beacon to your Pulsate account.** [block:callout] { "type": "warning", "title": "UUID Upper Case", "body": "Please note that the beacon UUID must be added to Pulsate in uppercase only." } [/block] To add a beacon to your Pulsate account, simply click on ‘Locate’ in the top navigation bar followed by the 'New Beacon’ button as indicated below. [block:image] { "images": [ { "image": [ "https://files.readme.io/e894da5-ConverseBeacons.png", "Converse:Beacons.png", 1280, 624, "#dadce0" ] } ] } [/block] This gives you options for uploading a .CSV file or adding a beacon manually. (Note: Pulsate no longer supports providing beacons to clients). [block:image] { "images": [ { "image": [ "https://files.readme.io/68bfdbb-Selecting_how_you_would_like_to_add_a_beacon.png", "Selecting how you would like to add a beacon.png", 926, 272, "#dcdcd5" ] } ] } [/block] **Adding Beacons Manually:** Click Add Manually and fill out the following fields for each beacon: Beacon Nickname: - a custom Pulsate identifier for each beacon that is typically the location of the beacon Beacon ID: - a custom Pulsate identifier for each beacon that is typically a unique identifier for the beacon added by Pulsate clients Major Minor UUID When all of the fields have been filled in, click Save to add the beacon to Pulsate. [block:image] { "images": [ { "image": [ "https://files.readme.io/713bf47-Adding_a_3rd_party_beacon.png", "Adding a 3rd party beacon.png", 935, 305, "#373737" ] } ] } [/block] **Adding Beacons By .CSV:** Upload a .CSV file in the format of: UUID, Major, Minor, Beacon ID, Nickname **How to Edit a beacon?** Hover over the edit button of the beacon you wish to edit and select ‘edit’ from the drop down. [block:image] { "images": [ { "image": [ "https://files.readme.io/529295b-Edit-Delete_Beacon.png", "Edit-Delete Beacon.png", 697, 282, "#ecf1f2" ] } ] } [/block] **How to delete a beacon?** From your list of previously created beacons, hover over the edit button of the beacon you wish to delete and select ‘delete’ from the drop down. You will get a confirmation message in advance. To the right of the bar, a delete icon will appear. Clicking the 'x' will remove the beacon. You will be asked to confirm if you would still like to remove it. If so, choose ‘delete’. If not, press ‘cancel’. [block:image] { "images": [ { "image": [ "https://files.readme.io/a781328-Beacon_deletion_warning.png", "Beacon deletion warning.png", 548, 225, "#5d7f78" ] } ] } [/block] **Check Status** Sometimes beacons run out of battery or need to be replaced for a host of reasons. To help identify when a beacon might need to be checked, Pulsate operates a traffic light system. If Pulsate has received an event for the beacon within the last week, a green traffic light symbol will be visible for that beacon. If no event has been received for a beacon within the last two weeks, that symbol will be changed to amber and if no event has been recorded for a beacon for over two weeks the traffic light symbol will change to red. It is good to keep an eye on the status of individual beacons and to proactively check any beacons that have an amber or red traffic light symbol. [block:image] { "images": [ { "image": [ "https://files.readme.io/005d9c7-Beacon_-_Traffic_Light_System.png", "Beacon - Traffic Light System.png", 847, 304, "#dbdce2" ] } ] } [/block] **Exporting Beacon Data ** Pulsate has a number of different methods for exporting beacon data to help you measure footfall and visitor frequency. To export beacon data from the Pulsate CMS, go to the beacon section and click “Export All” [block:image] { "images": [ { "image": [ "https://files.readme.io/1f51d90-Export_Beacon_-_Date_range.png", "Export Beacon - Date range.png", 850, 294, "#eaeaed" ] } ] } [/block] You will then be prompted to choose a timeframe for the beacon export (the default period is 1 month) and when that is selected you can click “Export” and Pulsate will compile the necessary data and send an email to the admin who is currently logged in with a csv attachment that includes all of the beacon events for the time period that was specified. [block:image] { "images": [ { "image": [ "https://files.readme.io/423bcce-Beacon_-_Export_started.png", "Beacon - Export started.png", 282, 111, "#d9ebf2" ] } ] } [/block] In addition, Pulsate can also automatically send any beacon events that are recorded to a url of your choice via webhook. As soon as a beacon enter or exit event is recorded by Pulsate. it will be automatically sent to the specified webhook. To enable this feature, click Settings and then App Settings in Pulsate and scroll down to the Webhooks section. [block:image] { "images": [ { "image": [ "https://files.readme.io/4ae12b4-Webhooks__Save.png", "Webhooks & Save.png", 1147, 428, "#e6e6e5" ] } ] } [/block] Switch the toggle to ON and then enter a url where you would like Pulsate to send beacon events. Then scroll down to the bottom of the App Settings page and press Save.