Teavaro supports server-side GTM integration for its IDR and analytics tracking and provides custom templates for seamless integration.
The Info Ident Track API is used to retrieve and create profiles without setting a UMDID cookie or storing UMID in browser or app, but instead using device, app and customer identifiers as detailed below and sending relevant information including UMID and device identifiers for example to Floodlight and any other required systems via server-side call.
For mobile apps Teavaro provides a template, which uses …
-
Firebase App instance ID, IDFV/IDFA and GAID as profile lookup identifiers.
-
Login / customer ID as customer profile lookup identifiers, which facilitate profile merging and switching as per data pipeline defined IDR rules.
Identifiers would be handled in the following priority across operating systems:
-
iOS:
-
Customer ID - available when logged in.
-
IDFA - available on ATT consent.
-
IDFV - available for all app installs.
-
Firebase App Instance ID - available for all app installs.
-
-
Android:
-
Customer ID - available when logged in.
-
GAID - available on advertising consent.
-
Firebase App Instance ID - available for all app installs.
-