Follow

TROPHiT v2.8.4: Redeem by App-Specific User IDs

TROPHiT v2.8.4 has been released with a new feature: the ability to perform S2S voucher redemption based on a custom app-specific user ID, overriding the default behaviour, which is based on device advertising IDs.

Impact on existing customers who do not need the feature: none

Impact on existing customers who performed client-side integration with TROPHiT: none, as mentioned above, this feature is only enabled for S2S integrations.

Impact on existing customers who performed S2S integration and wish to start using the feature:

  • Adjust, Tune, Kochava, F.O.X customers:
    • Add the following to the event callback/postback which triggers TROPHiT:
      &trophit_userid=<user ID callback param name>
    • For example, if the param name which contains the custom user ID is my_userid, add this to the callback/postback of the appropriate event:
      &trophit_userid=my_userid
    • Do not place the actual user ID value inside the trophit_userid property.
    • During redemption, TROPHiT will resolve the custom user ID. If empty, it will not fallback to the default device IDs unless these are specifically defined as a comma-separated list, for example (Adjust):
      &trophit_userid=my_userid,idfa,gps_adid,android_id
    • For Facebook campaigns, if trophit_userid points to a any device ID param, it is ignored as the integration module strips those off

  • AppsFlyer customers:
    • Configure your TROPHiT S2S integration module to use the appropriate AppsFlyer Push API JSON property as the custom user ID. Usage example:
      tah.appsflyerUserIdProperty = "customer_user_id";
    • Do not place the actual user ID value inside appsflyerUserIdProperty.
    • During redemption, TROPHiT will resolve the custom user ID. If empty, it will not fallback to the default device IDs unless these are specifically defined as a comma-separated list, for example (PHP):
      $tah->appsflyerUserIdProperty =
          array('customer_user_id', 'idfa', 'advertising_id', 'android_id')
      ;
    • For Facebook campaigns, ifappsflyerUserIdProperty points to a any device ID property, it is ignored as the integration module strips those off

  • Customers of other trackers: note the redeemForGenericTracker method in the S2S integration module has changed and now includes a new userId parameter after the androidId parameter. When upgrading your S2S integration module, make sure you update the call to the method, by providing the userId parameter as the actual user ID (or null if not needed). During redemption, TROPHiT will resolve the custom user ID or, if empty, fallback to the default device IDs as usual.

See your integration assistant in your TROPHiT dashboard for detailed instructions per programming-language, or contact us for any further questions.

 

0 Comments

Please sign in to leave a comment.
Powered by Zendesk