PreferenceLink Sync for Mobile SDK
To use PreferenceLink with LRPrivacyManager, you should enable PreferenceLink Sync in your Privacy Manager configuration within Console and add the PreferenceLink vendor key. Then provide a user identifier through the configure method of the TCF SDK, or through the public API identifyUser (Android) and preferenceLink of LRPrivacyManager.shared instance (iOS).
If PreferenceLink is not enabled or if the PreferenceLink vendor key or user identifier is not provided, the sync won't be performed.
Synchronization of consent data is automatically performed when:
Each fresh start of the app
Consent is changed/given
Privacy Manager is (re)surfaced
The app is moved from background to foreground
In order to prevent unnecessary sync calls a timeout can be set on the console. If the timeout period expires the sync will be performed.
After sync is finished an event will be triggered.
For Android: SYNCED_WITH_PREFERENCE_LINK
For iOS: LREvent.syncedWithPreferenceLink
Configuring PreferenceLink within Console
To configure PreferenceLink within Console:
Go to the PreferenceLink product page from the left side menu and create a schema by choosing the option “Custom Schema”.
Choose the option “Privacy Manager consent sync”.
Enter the schema name, schema purpose, legal basis, and data fields including an identifying field (customerId).
Click on the created schema and go to the Integration tab. Click to set up a new integration.
Enter the name of your integration and choose the vendor. If you don’t have vendors already created, click . Select API access options to read/write data and choose the data fields.
When you’ve finished the creation process you should see your integration in the list. You will have to use the API Key of the integration to connect your Privacy Manager GDPR application and PreferenceLink schema. To do that, copy the API key, access your Privacy Manager configuration, and go to the Admin tab. Enable PreferenceLink Sync and paste the API Key value in the PreferenceLink Vendor Key field. You should choose the timeout time and republish your configuration.