Campaigns and Privacy

This article describes how Meridian uses device ID with Campaigns.

Campaigns and Privacy

Campaigns use device ID in two ways.

First, Campaigns use a device ID to limit the number of notifications a device generates from a specific Campaign and from a specific Beacon.

Second, Campaigns that notify a third-party endpoint send a device ID to a custom third-party endpoint.

Device ID

The device ID used with Campaigns differs between iOS and Android. The ID includes information about the device that triggered the Campaign, including what app was being used at the time.

The device_id value is slightly different on iOS and Android.

On iOS, the device_id is made up of the app's `identifierForVendor` value and the app's `bundleIdentifier`.

On Android, the device_id is made up of the device's advertising ID value and the app's `bundleIdentifier`.

The device_id tends to look something like `3fnk1gn3hhghbytjv:com.arubanetworks.Campus`.
	

Device ID and Personally Identifiable Information (PII)

Although the device ID is tied to a specific device, this piece of data isn't tied to a specific person and unless you already knew that a specific device ID was related to a specific person, it would be extremely difficult to to relate a device ID to a specific individual.

Custom Endpoints

In addition to generating push notifications, Campaigns can also notify 3rd-party custom endpoints.

When a device triggers a custom endpoint campaign, the Meridian Editor sends campaign_id, broadcaster_id, and device_id. Also, whether the Campaign was triggered on enter or exit.

The custom endpoint posted URL structure: is_enter=1&campaign_id=#####&broadcaster_id=#######&device_id=######

The campaign_id is the unique identifier for the Campaign in the Meridian Editor.

The broadcaster_id is information about the specific Beacon that was used to trigger the Campaign. The broadcaster_id includes the UUID and ends with the major/minor of the Beacon that notified the endpoint.

For mapless campaigns, the broadcaster ID only includes the UUID and major value. It does not include the minor value. This means that all of the Beacons associated with a single campaign will send the same broadcaster_id value.

The device_id includes information about the device that triggered the Campaign, including what app was being used at the time.

The device_id value is slightly different on iOS and Android.

On iOS, the device_id is made up of the app's `identifierForVendor` value and the app's `bundleIdentifier`.

On Android, the device_id is made up of the device's advertising ID value and the app's `bundleIdentifier`.

The device_id tends to look something like `3fnk1gn3hhghbytjv:com.arubanetworks.Campus`.