Using Aghanim with multiple Android package names or iOS bundle IDs

Aghanim does not identify an app by its Android package name or iOS bundle ID when sending players back to the game after checkout. Instead, Aghanim stores deep links as ready-made URLs and chooses the appropriate link based on the player’s platform and browser.

How back-to-game links are configured

Configure one deep-link value for each supported platform in the dashboard:

• iOS custom URL scheme for iOS outside Safari
• iOS universal link for iOS in Safari
• Android app link for Android

The {order_id} variable is supported in these URLs.

What this means for multiple bundle IDs or package names

Back-to-game routing is driven by the deep link itself, not by the bundle ID or package name.

• If multiple app builds share the same deep-link scheme or app link, a single configured value per platform is usually sufficient.
• If different builds require different deep-link schemes or different app links, Aghanim cannot choose between them based on bundle ID or package name. The dashboard currently supports only one configured value per platform.

QR login

QR login does not require a separate deep-link configuration beyond the standard platform deep-link setup.

Implementation note for multi-store Android distributions

If you distribute the same game through multiple Android stores and use different package names so users can install multiple store builds side by side, make sure those builds can still be handled by the same configured Android deep link if you want Aghanim to return players to them through one dashboard setting.

If the builds require different Android app links or schemes, Aghanim cannot route players to a specific package name on its side.