Bulk Importing BLE Tags in Telematics Guru
Bulk Importing BLE Tags in Telematics Guru
Use Import Tags to create multiple Bluetooth tag assets from a CSV file. The tag template includes identification, organisation assignments, custom fields and asset details. The identifier entered in TagSerial depends on the tag's DeviceType.
Before You Begin
Select the organisation in which you want to create the tag assets.
Have the correct identifier and device type for each tag. Do not assume that every tag uses a MAC address or a numeric serial number.
Use the current Bulk Tag Import CSV Template from Telematics Guru, rather than the asset import template.
Use Import Tags, Not Import Assets
The Bulk Import page has separate operations and templates for assets and tags. For BLE tag assets, select Import Tags and use Download Bulk Tag Import CSV Template.
Download and Prepare the Template

Go to Admin > Bulk Import.
Select Download Bulk Tag Import CSV Template, beside Import Tags.
Keep the column headers unchanged. Replace the example rows with your own tag assets, using one row per tag.
Complete each tag's asset details, DeviceType and matching TagSerial using the references below.
Save the completed file as CSV. If you edit raw CSV text, keep identifiers containing commas enclosed in double quotes so that each identifier remains in one column.
Template Field Reference
The tag template contains the following columns. Preserve their exact names. The examples illustrate the template format; they are not an exhaustive list of allowed values or a statement that every field is mandatory.
| Column | Purpose | Entry Guidance |
|---|---|---|
AssetName |
The tag asset's name in Telematics Guru. | Use a name that identifies the tagged equipment or item. |
Description |
A description of the tag asset. | Record its role or other useful identifying details. |
AssetType |
The type of asset being tracked. | This is separate from the tag's DeviceType. The template includes examples such as Car. |
Department |
The asset's department assignment. | Enter the intended department in the target organisation. |
Project |
The asset's project assignment. | Enter the intended project in the target organisation. |
TagSerial |
The identifier of the tag. | Use the format for its DeviceType. See the identifier reference below. |
Custom1 |
The first custom asset field. | Enter the value appropriate to your organisation's first custom field. |
Custom2 |
The second custom asset field. | Enter the value appropriate to your organisation's second custom field. |
Custom3 |
The third custom asset field. | Enter the value appropriate to your organisation's third custom field. |
DeviceType |
The tag type used to interpret the identifier and tag data. | Use the exact type name from your current tag template, for example Tag: iBeacon or Tag: DM DOT Tag. |
AssetCode |
The asset's code or reference. | Enter the reference used by your organisation. |
AssetHealthTrackingEnabled |
The asset health tracking flag. | The template uses 0 and 1. |
Manufacturer |
The manufacturer recorded against the asset. | Enter the applicable asset information. |
Model |
The model recorded against the asset. | Enter the applicable asset information. |
TagSerial Formats
Use the identifier format shown for the selected device type in the current template. The following examples show how numeric identifiers, MAC addresses and compound identifiers differ.
| DeviceType | TagSerial Example | Format |
|---|---|---|
Tag: DM Guppy |
1029384 |
Numeric identifier. |
Tag: iBeacon |
e2c56db5-dffb-48d2-b060-d0f5a71096e0, 1, 23 |
UUID, MajorID, MinorID, together in one field. |
Tag: Eddystone |
61:0d:6c:28:e1:a4:bd:b7:22:a3, 00:00:00:00:12:71 |
The two-part identifier shown in the template, together in one field. |
Tag: Ingics iBS01: Basic |
f8:12:cb:e7:4a:19 |
MAC address. |
Tag: Ingics iBS01: Temp/Humidity |
f5:4b:fb:e1:4c:12 |
MAC address. |
Tag: DM Sensor Node |
2089492 |
Numeric identifier. |
Tag: Eddystone TLM |
f8:12:cb:e7:4a:20 |
MAC address. Do not substitute the compound format used by Tag: Eddystone. |
Tag: ELA MAG |
a5:24:fb:e1:4e:19 |
MAC address. |
Tag: ELA MOV |
b6:74:fb:e9:b9:19 |
MAC address. |
Tag: ELA ANG |
f5:44:fb:e1:4e:19 |
MAC address. |
Tag: ELA ID |
f5:44:ab:e1:4e:18 |
MAC address. |
Tag: ELA T |
a3:4e:f5:e7:4e:b9 |
MAC address. |
Tag: ELA RHT |
f5:44:fb:e1:4e:98 |
MAC address. |
Tag: ELA ProxIR |
a3:4e:f5:e7:4e:ba |
MAC address. |
Tag: ELA DI |
a3:4e:f5:e7:4e:bb |
MAC address. |
Tag: DM Barra Radar |
3104857 |
Numeric identifier. |
Tag: DM DOT Tag |
70:b3:d5:a1:b2:c3 |
MAC address. |
Tag: DM DOT Sensor |
70:b3:d5:a1:b2:c4 |
MAC address. |
Tag: Teltonika Eye Sensor |
7c:d9:f4:12:34:56 |
MAC address. |
Tag: DM DOT Glow |
70:b3:d5:a1:b2:c5 |
MAC address. |
iBeacon CSV Example
iBeacon tags use the same import workflow and asset fields as other tag types. Set DeviceType to Tag: iBeacon and enter the UUID, MajorID and MinorID together in TagSerial. In raw CSV text, the commas inside that identifier must be quoted:
AssetName,Description,AssetType,Department,Project,TagSerial,Custom1,Custom2,Custom3,DeviceType,AssetCode,AssetHealthTrackingEnabled,Manufacturer,Model
Tag: iBeacon Template,Client Vehicle,Car,Testing,Project X,"e2c56db5-dffb-48d2-b060-d0f5a71096e0, 1, 23",Custom1,Custom2,Custom3,Tag: iBeacon,TEST_RUN,1,Mazda,2Use your own tag's identifier and asset details, not the example values.
Import the Tags
Return to Admin > Bulk Import and select Import Tags.
Upload the completed tag CSV file.
Review the import page's feedback and correct any reported issues before completing the import.
After completing the import, check that the resulting tag assets have the intended names, device types and identifiers.
Troubleshooting
Values Have Shifted into the Wrong Columns
Check CSV quoting. iBeacon and Eddystone identifiers contain commas, but the entire identifier belongs in one TagSerial cell. In raw CSV, enclose that complete cell value in double quotes.
The Tag Identifier Is Not Accepted
Check that DeviceType matches the tag and that TagSerial follows the corresponding template example. A MAC address, numeric identifier and iBeacon UUID/MajorID/MinorID combination are not interchangeable.
The File Uses DeviceSerial Instead of TagSerial
Download the Bulk Tag Import CSV Template. DeviceSerial belongs to the asset import template; this workflow uses TagSerial and Import Tags.
Next Steps
To get tag observations into Telematics Guru, follow Tags in Telematics Guru for gateway setup and the tag data workflow. Then configure Bluetooth Tag Alerts for your monitoring requirements. For non-tag asset imports, use Bulk Importing Assets in Telematics Guru.