Tenjin attribution attributes on players
What's new
Ten tenjin_* attributes are now part of the player attributes schema: tenjin_analytics_installation_id, tenjin_bundle_id, tenjin_platform, tenjin_developer_device_id, tenjin_advertising_id, tenjin_os_version, tenjin_os_version_release, tenjin_app_version, tenjin_build_id, and tenjin_device_model. They hold the identifiers the Tenjin SDK produces in your game client, and all of them are optional strings.
Impact
The Tenjin integration previously read these values only from the player.verify webhook response. They are now declared on the player attribute schemas, so you can write them directly when updating a player, creating an order, or authorizing a player, and read them back on player and order responses.
Changes
| Resource | Change |
|---|---|
| update_player | The ten tenjin_* attributes are accepted in the attributes request object |
| get_player | The ten tenjin_* attributes are returned in attributes |
| create_order, authorize_user | The ten tenjin_* attributes are accepted in player_info.attributes |
| get_order, update_order | The ten tenjin_* attributes are returned in player_info.attributes |
Upgrade
- No action required. Games already returning these attributes from
player.verifykeep working unchanged. - Attribution needs
tenjin_analytics_installation_id,tenjin_bundle_id, andtenjin_platformat minimum, plustenjin_developer_device_idon iOS.
需要技术支持？
联系我们的集成技术团队： [email protected]