[question]: IncludePlayerIds has been marked obsolete in v2.0

[zythra]

How can we help?

IncludePlayerIds has been marked obsolete with no direction on what to use instead. This is the only way we target our users. What is the alternative? We don't use the ExternalUserId property and we don't use segments.

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[kesheshyan]

Hey @zythra, Thank you for the question and thank you for using our library. You can continue to user include_player_ids for now, but could you please describe how exactly do you use this for targeting users - we are trying to understand your use-case better. With the new User Model update we introduce aliases that we recommended to use for targeting individual users.

[zythra]

We store playerId's in our system and use filtering on our end to determine who we want to send to. We have an in house built system for our marketing team that they can use to target players based on many attributes that are unique to us and our business. We then use IncludePlayerIds to target those users. It's the only mechanism we use to target our users, we use nothing else. Losing this will be a big deal for us. I'm not familiar with aliases.

[VladyslavYesypov]

@kesheshyan hi, are there any docs on the new User Model?

[emawby]

@VladyslavYesypov The readme of this repo is updated for the User Model API

[zythra]

@emawby Hi, you've closed this but what's the resolution?

[emawby]

@zythra You can continue to use IncludePlayerIds since it sounds like you have already built out tooling around player ids. As mentioned above you could aliases instead (it used to just be externalUserId but now you can have multiple).

[zythra]

@emawby Thanks for the response. Will the obsolete attribute we removed?