Cross-Device Bridge
The Cross-Device Bridge has to be activated in your Mapp Intelligence account!
The Cross-Device Bridge technology makes it possible to identify the user anonymously across multiple devices, apps, and websites. Numerous unique user characteristics are collected in a pool and assigned for this purpose. The Cross-Device plugin includes the functionality for anonymizing unique user characteristics and transferring them to Mapp Intelligence.
To use qualitative data in your login pool, additional characteristics for the active users on your website have to be provided. The Cross-Device Bridge offers standardized parameters for this purpose. You should use these for data enrichment insofar as this information is available to you.
The more characteristics are available to the pool for each user, the better the matching that can be assured across various websites, apps, and devices.
In order to meet data privacy requirements, all private data of the user that are transferred to Mapp Intelligence are anonymized by a client-side hash function so that they cannot be reset to the original value. Should various private data of the user already be available as "MD5" or "SHA256" hash, you can transfer these directly to Mapp Intelligence and specify the hash type. Please note the information on the normalization of data.
Identifier
Parameters | Example | Can be hashed for transferring |
---|---|---|
E-mail address | max.mustermann@example.com | yes |
Telephone number | 49307554150 | yes |
Address | max|mustermann|10115|robertkochplatz|4 | yes |
Facebook User ID | 123456789 | no |
Twitter User ID | 123456789 | no |
LinkedIn User ID | 123456789 | no |
Google+ User ID | 113551191017950459231 | no |
Android Advertising ID | 38400000-8cf0-11bd-b23e-10b96e40000d | no |
iOS AdID | aaaaaaaaa-bbbb-cccc-1111-222222220000 | no |
Windows Advertising ID | 750c6be243f1c4b5c9912b95a5742fc5 | no |
Criteo XDevice ID | 1d640b86-aa8a-43d8-8e8c-b231aa2e821b | no |
AdClear User ID | 3497109703320666112 | no |
Custom parameter 51-79 | 103942815740852792445 | yes |
Normalizing user characteristics
If user characteristics are already available with MD5 or SHA256 hashed values, or you want to have the values independently anonymized, you have to ensure that the values are prepared in the same style implemented in the Cross-Device Bridge plugin.
E-mail address
- Convert all characters to lowercase
- Remove all spaces
- Transfer once as MD5 and once as SHA256
Telephone number
- All characters in lowercase
- Remove all spaces
- Remove all characters that are not numbers
- Transfer once as MD5 and once as SHA256
Address
- All characters in lowercase
- "ä" becomes "ae", "ö" becomes "oe", "ü" becomes "ue", "ß" becomes "ss"
- Remove all spaces, underscores and dashes
- Regular expression "/str(.)?(s||)/" becomes "strasse|"
- Transfer once as MD5 and once as SHA256
Social media IDs
- All characters in lowercase
Methods and properties
name
Get the name of the extension.
/**
* @type {string}
*/
wtSmart.extension.cdb.name
version
Get the version of the extension.
/**
* @type {string}
*/
wtSmart.extension.cdb.version;
setEmail
/**
* @param {string} email
*/
wtSmart.extension.cdb.setEmail(email);
setPhone
To ensure comparability, the telephone number has to be transferred with the country code and no zero in the area code.
/**
* @param {string} phone
*/
wtSmart.extension.cdb.setPhone(phone);
setAddress
To ensure comparability, the address must be complete with first name, last name, postal code, street and house number. The values have to be transferred in a string separated by a vertical line.
/**
* @param {string} address
*/
wtSmart.extension.cdb.setAddress(address);
setAndroid
/**
* @param {string} android
*/
wtSmart.extension.cdb.setAndroid(android);
setIOS
/**
* @param {string} ios
*/
wtSmart.extension.cdb.setIOS(ios);
setWindows
/**
* @param {string} windows
*/
wtSmart.extension.cdb.setWindows(windows);
setFacebook
You can also transfer the profile IDs from Facebook to the Cross Device Bridge plugin to enrich your login pool with additional qualitative data.
/**
* @param {string} facebook
*/
wtSmart.extension.cdb.setFacebook(facebook);
setTwitter
You can also transfer the profile IDs from Twitter to the Cross Device Bridge plugin to enrich your login pool with additional qualitative data.
/**
* @param {string} twitter
*/
wtSmart.extension.cdb.setTwitter(twitter);
setGoogle
You can also transfer the profile IDs from Google+ to the Cross Device Bridge plugin to enrich your login pool with additional qualitative data.
/**
* @param {string} google
*/
wtSmart.extension.cdb.setGoogle(google);
setLinkedIn
You can also transfer the profile IDs from LinkedIn to the Cross Device Bridge plugin to enrich your login pool with additional qualitative data.
/**
* @param {string} linkedIn
*/
wtSmart.extension.cdb.setLinkedIn(linkedIn);
setCriteo
If this option is activated the CDB Plugin automatically reads the Criteo XDevice ID and sends it to the Mapp Intelligence CDB.
As a precondition, you need your account to be activated from Mapp Intelligence and Criteo. If you have questions on this don't hesitate to contact your consultant or send an e-mail to support@webtrekk.com.
wtSmart.extension.cdb.setCriteo();
setAMP
wtSmart.extension.cdb.setAMP();
setAdClear
If this option is activated the CDB Plugin automatically reads the AdClear User ID and sends it to the Mapp Intelligence CDB.
- adClearTrackDomain: This parameter contains the account specific URL of the AdClear tracking server. The tracking domain also defines whether AdClear uses "first party tracking" or "third party tracking" to collect data.
- adClearTrackId: AdClear uses this parameter to assign server requests to your account.
As a precondition, you need your account to be activated from Mapp Intelligence and AdClear. If you have questions on this don't hesitate to contact your consultant or send an e-mail to support@webtrekk.com.
/**
* @param {string} adClearTrackId
* @param {string} adClearTrackDomain
*/
wtSmart.extension.cdb.setAdClear(adClearTrackId, adClearTrackDomain);
setCustom
In order to request CDB data, you need to hand over custom Ids first by using the custom parameters (51 – 79). Afterward you can use them with our READ API. The exact usage is explained in the API Chapter. Typically, cookie_ids or own AdServerIDs are given to the pool by using the custom parameter. If you want to send Ids from other partners, as Google Ad Exchange or Adform, we recommend to contact us, in order to do the implementation.
/**
* @param {number} id
* @param {string} custom
*/
wtSmart.extension.cdb.setCustom(id, custom);
Example
/* set email */
// as MD5
wtSmart.extension.cdb.setEmail('ef8ca1c0ff7d2e34dc0953d4222655b8');
// as SHA265
wtSmart.extension.cdb.setEmail('1f9e575ad4234c30a81d30c70affd4bba7b0d57d8e8607ad255496863d72c8bb');
// plain
wtSmart.extension.cdb.setEmail('foo@bar.com');
/* set telephone */
// as MD5
wtSmart.extension.cdb.setPhone('6af3cc537ab15ffb500167af24d2b9d6');
// as SHA265
wtSmart.extension.cdb.setPhone('629d99e8350b704511f8fe6506c38888c0749dacc0f091d7f8914cdd6b5b7862');
// plain
wtSmart.extension.cdb.setPhone('+49307554150');
/* set assress */
// as MD5
wtSmart.extension.cdb.setAddress('fa06dd5d3ad984d54e31885e8d9887a3');
// as SHA265
wtSmart.extension.cdb.setAddress('6e65555ea5d3c707ef3e7bbc6a7e09d33c23dd2e23c36d6750b25bf86efdf843');
// plain
wtSmart.extension.cdb.setAddress('John|Doe|10115|Robert-Koch-Platz|4');
// set android advertiser id
wtSmart.extension.cdb.setAndroid('abc123def456');
// set ios advertiser id
wtSmart.extension.cdb.setIOS('abc123def456');
// set windows advertiser id
wtSmart.extension.cdb.setWindows('abc123def456');
// set facebook user id
wtSmart.extension.cdb.setFacebook('1000016038xxxxx');
// set twitter user id
wtSmart.extension.cdb.setTwitter('33388xxxxx');
// set google+ user id
wtSmart.extension.cdb.setGoogle('1039428157408527xxxxx');
// set linkedin user id
wtSmart.extension.cdb.setLinkedIn('1R2xxx');
// set criteo x-devide id
wtSmart.extension.cdb.setCriteo();
// set amp cookie everid
wtSmart.extension.cdb.setAMP();
// set adclear user id
wtSmart.extension.cdb.setAdClear('123451234512345', 'track.adclear.net');
// set custom identifier
window.wtSmart.extension.cdb.setCustom(51, 'custom id 51');
window.wtSmart.extension.cdb.setCustom(61, 'custom id 61');
window.wtSmart.extension.cdb.setCustom(79, 'custom id 79');