Skip to main content
Use the Game Portal as a parking domain to create a compliant path from your game to your web store. The portal acts as an intermediate destination where players can land before you route them to the store. Every Game Portal requires an Appcharge web store project in the Publisher Dashboard. For this use case, the project can remain blank if you redirect players to your own external web store.

How it works

Because a parking domain is a Game Portal use case, you can optionally use standard Portal features to create pages, configure blocks, publish articles or news, and customize the design to match your game and brand. To direct players from the portal to your web store, choose one or more linking options:
  • Store page: Use the Store navigation tab to display the web store inside the portal or redirect players to a page outside the portal. Learn how to configure the Store page.
  • CTA block: Add a CTA block to a portal page to direct players from that page to your web store. Learn how to configure a CTA block.
  • Content link: Add a link to your web store inside an article or news item. Learn how to add links to portal content.

Player authentication

From the game to the portal

You can configure Pre-Authenticated Login for any Game Portal setup to seamlessly log players in when they move from your game to the portal.

From the portal to the web store

Authentication depends on the target store and linking method:
  • Appcharge web store: For Store page redirects and CTA block links, Appcharge can use Pre-Authenticated Login when the target is an Appcharge web store on the same account as the portal.
  • External web store: Appcharge doesn’t provide Pre-Authenticated Login to an external, non-Appcharge web store. You can handle authentication through your own redirect URL.
  • Content link: Appcharge doesn’t initiate Pre-Authenticated Login for links inside portal content. If a player isn’t already logged in to the web store, the link opens the store with the player logged out.