Lotame integration

If you intend to utilize the Data Collection API aspects of Lotame and add predicted profiles as demographic variables please follow this guide for implementation.

Abstract

This integrations happens on the publisher side and requires our master script to be loaded to websites. Both inline or TAG-managers delivery are working perfectly. The master script typically looks like:

Semi-obfuscation

Semi-obfuscation is a compromise between plain demographics and AudienceData default obfuscated key-values (e.g. ap_a:1, ab_b:3). Here are a few examples:

gndr - Gender

m - male

f_150 - female, affinity 150

yrs - Age

1824 - from 18 to 24

30max_150 - <30, affinity 150

50min_200 - >50, affinity 200

You can request vocabulary from your account manager.

Testing

Integration is performed by the development team on publisher side, therefore we ensured that integration can be tested on non-production environment.

On our end we implemented the following debug helper to verify the implementation. You can fill the cache with fake data by entering page with our script present with parameter ?__sak_fakeads=1,3,5,random5 like http://example.com/?__sak_fakeads=1,3,5,random5. It will put key-values with ids 1, 3, 5 and random 5 from vocabulary. You can modify these parameters. Test scenario would be following:

Add addAudienceProjectDataToLotame function and its invocation to Lotame snippet