Hide store access for Android in-app hub visits using the app_visit deep-link attribute

When a game hub must prevent Android users entering from the game client from reaching any external store or payment path, pass a custom player attribute in the login deep link and use that signal to hide store-related navigation.

Recommended approach

Use the app_visit player attribute to indicate that the session originated from the Android app.

https://<game_hub>/go/login?player_id=<player_id>&redirect_path=/daily-rewards&attributes.app_visit=true

For non-Android or normal web/iOS entry points, keep the existing link without the attribute:

https://<game_hub>/go/login?player_id=<player_id>&redirect_path=/daily-rewards

What this enables

• Users entering from the Android app can be shown a storeless version of the hub.

• Users entering organically on the web or from iOS/PC can continue to see the full hub, including store access where appropriate.

• The same user can have different behavior depending on how they signed in: if they arrive via the app with the flag, store-related items are hidden; if they later sign in normally without the flag, the normal experience can be shown.

Platform detection notes

The platform can be determined from several sources, in this order:

• The platform passed in player.Verify

• The client user agent

• Request headers

However, to determine whether the user specifically came from the app, passing an explicit attribute on the authorization link is the preferred approach.

Implementation notes

• Create or use the custom player attribute app_visit.

• Append &attributes.app_visit=true to Android in-app deep links.

• Hide every path that could indirectly lead to the store, not just the primary store button. This includes secondary entry points such as loyalty or profile-related panels.

• After changing visibility rules, refresh or invalidate cache as needed so hidden sections disappear immediately.

Compliance reminder

If this change is being made for Google Play payments compliance, verify that there are no remaining indirect paths from the Android in-app hub experience to any external purchase flow before submitting for review.