Implementing Cross Device Bridge
The Cross Device Bridge technology allows users to be identified anonymously across multiple devices, applications, and websites. Unique user characteristics are collected in a pool and assigned to a user profile for this purpose.
To comply with the German data protection regulations, all of the user's private data transmitted to Mapp Intelligence has already been made anonymous so that it cannot be reset to its original value.
If the user's private data already exists in "MD5" or "SHA256" encryption, you can transfer it directly to Mapp Intelligence.
Please read the notes on normalizing the data in the Normalizing User Characteristics section before you encrypt the values yourself.
Implementation Options
Example
Cross Device Bridge parameters are only allowed in GlobalProperties.
Tracker.global.crossDeviceProperties.emailAddress = .hashed(
md5: "acbd18db4cc2f85cedef654fccc4a4d8" ,
sha256: "2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae"
)
Tracker.global.crossDeviceProperties.address = .hashed(
md5: "acbd18db4cc2f85cedef654fccc4a4d8" ,
sha256: "2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae"
)
Tracker.global.crossDeviceProperties.phoneNumber = .hashed(
md5: "acbd18db4cc2f85cedef654fccc4a4d8" ,
sha256: "2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae"
)Parameter | Description |
|---|---|
| emailAddress | Optional. Email address of the user. |
| address | Optional. The address must be completed with first name, surname, postcode, street, and house number. The values must be converted into a string, whereby the fields are separated by a vertical line (pipe). Example max|mustermann|10115|robertkochplatz|4 |
| phoneNumber | Optional. Phone number of the user. |
| iosId | |
| androidId | Optional. The Android ID is the advertiser_id which is available through the Google API. |
| Social media IDs | Optional. You can also transfer the profile IDs of Facebook, Twitter, LinkedIn and Google+ to the Cross Device Bridge plugin to enhance your login pool with additional qualitative data. |
| Custom 1 - 29 |
None of the identifiers is mandatory, but to ensure the best possible match, we recommend passing at least the email address to the Cross Device Bridge.
Example
webtrekk.track( new WebtrekkUserParameters().
setEmail( "maxmustermann@email.org" ).
setAddress( "max|mustermann|10115|robertkochplatz|4" ).
setPhone( "12345678" ).
setAndroidId( "Android ID" ).
setFacebookID( "Facebook ID" ).
setTwitterID( "Twitter ID" ).
setGooglePlusID( "Google plus ID" ).
setLinkedInID( "LinkedIn ID" ).
setCustom( 1 , "Custom value1" ).
setCustom( 2 , "Custom value2" ));Parameter | Description |
|---|---|
Optional. Email address of the user. | |
| Address | Optional. The address must be completed with first name, surname, postcode, street, and house number. The values must be converted into a string, whereby the fields are separated by a vertical line (pipe). Example max|mustermann|10115|robertkochplatz|4 |
| Phone | Optional. Phone number of the user. |
| AndroidId | Optional. The Android ID is the advertiser_id which is available through the Google API. |
| Social media IDs | Optional. You can also transfer the profile IDs of Facebook, Twitter and LinkedIn to the Cross Device Bridge plugin to enhance your login pool with additional qualitative data. |
| Custom 1 - 29 | Optional. You can also use additional user-defined identifiers (for example, your own user IDs). The assignment to the parameters used on the site is as follows: Custom ID 1 -> cdb51 … Custom ID 29 -> cdb79 |
None of the identifiers is mandatory, but to ensure the best possible match, we recommend passing at least the email address to the Cross Device Bridge.