Follow

trophit_userid

This feature has been deprecated and replaced by User Segment Identity Lookup starting v3.1.0. Developers should no longer pass this parameter in the attribution data to control user identity.

 

Before v3.1.0:

 

Description:

An optional configuration setting of the redemption process (s2s integration mode only), which defines the location and priority of the user identity used for the redemption process

Simple format:

A comma-separated text, each element is a name of an entry in the attribution data used for redemption. Leading/trailing whitespaces in each element name are ignored. Examples:

  • user_id
  • pub3,player_id,idfa

"Dot-notation" format:

Each element may use dots to specify a "sub-element" name within the element, assuming the element values themselves are either JSON objects, URLs or Query Strings. Examples:

  • JSON: Consider an attribution data element event_value which contains the JSON object {"label":"label1", "source":"foo"} or its string representation "{\"label\":\"label1\", \"source\":\"foo\"}". If you want to specify that the value of the label property of the event_value element is to be considered a user identity, set trophit_userid to event_value.label
  • URL: Consider an attribution data element deeplink which contains the URL myapp://?action=store&player_id=1bfc4b124. If you want to specify that the value of thte player_id parameter of that URL is to be considered a user identity, set trophit_userid to deeplink.player_id
  • JSON-URL Combo: Consider an attribution data element event_value which contains the JSON object {"url":"myapp://?action=store&player_id=1bfc4b124", "source":"foo"} or its string representation "{\"url\":\"myapp://?action=store&player_id=1bfc4b124\", \"source\":\"foo\"}". If you want to specify that the value of the player_id parameter of the url property of the event_value element is to be considered a user identity, set trophit_userid to event_value.url.player_id

How to Configure trophit_userid:

  • For most trackers except AppsFlyer, you configure it on the callback/postback URL (you can use different settings for each postback/callback). For example:
    https://my.gameserver.com/?idfa=....&player_id=...&deeplink=...&...more attribution elements...&trophit_userid=deeplink.label,player_id
    Note
  • For AppsFlyer, you configure it within your TROPHiT integration module. Python example (check your TROPHiT dashboard for more examples):
    tah.appsflyer_user_id_property = ['event_value.userid', 'customer_user_id']

Identification process:

  • If trophit_userid is not specified, TROPHiT tries to identify each user by device identifies such as IDFA, GAID, ANDROID_ID, which is the default behavior
  • If trophit_userid is specified, TROPHiT tries to identify each user by the value of the listed element names of the attribution data, in the order they were specified
  • Once TROPHiT finds a non-empty value, it uses it as the identity of the user performing the redemption. Note TROPHiT does not fallback to device identifiers if all values are found empty. Instead, it will issue an INVALID_REQUEST error (unless the voucher is configured as anonymous)

 

0 Comments

Please sign in to leave a comment.
Powered by Zendesk