These points above are indeed good examples regarding "forcing bad practices":

If I have 3 free API calls after the API call, after the 3rd freebie, I can return it and call again for 1 core + 3 more that can branch off again. This is inefficient for BC, yet beneficial for end-users (thus, forcing bad practices since it costs and gives more if we avoid the pre and post hooks).

If a workaround to save API costs would be more work for the user, and costs more for BC, that's a lose-lose. If such a "hole" exists, shouldn't it be repriced for that consideration to make it the win-win you folks want it to be?

Thank you very much 🙂

Hi @Omar-Alzayed When apps have millions of users, browsing all users can have poor performance.
If you have a smaller number of users, it can be useful.
There is a way to create a segment so you can browse all your users.

Go to App > Design > Segmentation > Segments
Create NEW SEGMENT
656b32ad-94e5-4314-a79a-f7a8cf201536-image.png

There's a couple different ways you can return ALL users. The one I like is to use the criteria A/B Testing ID 0-99 which will return all your users.

28d945d5-1fb5-4606-b8be-c220291a763e-image.png
9a146d95-9e93-4944-a695-68844bb4fd53-image.png

Looks something like this:
e37eea64-557d-4eca-91d0-2dff0699479e-image.png

Segments are automatically run nightly at around 3am but you can press REFRESH SEGMENTS to run it immediately.

Note that the refresh will take time to complete according to your user count, you may wish to do this during low player traffic.

In the case of this particular segment, I believe the Refresh will need to run TWICE to capture all your users. (I think the AB code needs to be initialized in the first pass, and then it can be read in the second pass, capturing all of your users.)

Please take care not to launch the second Refresh before the first one completes. (If you have 10,000+ players then wait about 30 minutes or so)

c4785150-2e0a-489d-8a47-d330c7c09d80-image.png

Once you have players in the Segment, you can browse by Segments. Go to
User > User Browser

Choose BROWSE, then check the box to browse within a segment. Choose the segment.
fd6b9af5-b4b1-47d1-bc05-d43180e8e621-image.png

Reminder, once you have millions of users, this can be very slow. But you can create more refined Segments to filter to just the interesting users, such as Has Bought Something, Is at Least Level 10, and so on.

Segments allow compound conditions so you can really filter to exactly who you want.

Segments can also be used to target Sales and Promotions to specific player groups. For example you could create a $0.99 one-time, loss leader promo that is available to only those players who have not bought anything in your game yet. It's a very powerful system.

Could you let me know if this helped you?
Thanks
John

We'll look into it @Omar-Alzayed ...

Paul.

@Paul-Winterhalder said in A few suggestions I have so far:

. Would it be fair to say that those user's entities would have to have their ACL set to other: 1 so it's readable?

Yes, that would be the case.