FAQ Headless Destination
Frequently asked questions for you who are building your own web gaming destination!
What is a Headless Destination and why would I build one?
A “Headless Destination” means embedding the Pley Web Playable in your own website using your own authentication and UI. It is ideal if you need full control, custom design, continuously develop new functionality, and use a unique user system. Most games do not need this, and should use the Pley gamesites instead.
Do I need a login system on the website?
Yes, you must have a website-level login system to be able to build your own game distribution channel. Users must be able to log in and store their progress safely, especially when payments are involved. If you do not have the resources to build your own login system, Pley offers out-of-the-box gamesites free of charge.
How do I get analytics from games on my destination?
The Pley Web SDK pushes events into the datalayer. From there, you can send them to any analytics service you run on your website or web app.
What is a scope user, game user, & pley game user?
See the terminology list for the Headless Destination implementation here.
A scope user is a user in your website-level account system, a game user is a user in the game's server, and a pley game user is a Pley equivalent to the game's game user.
What is "adopting" a user?
Adopting a user should occur when a user has generated a game user (with game progress) as a guest, and then signs up on your destination. When that occurs, the website-level user (scope user) that signed up / signed in should be updated, setting the pley_game_user_id to the ID of the guest session. The user will expect their progress to still be there after logging in, and not to start over.
Article: The four cases of authentication for headless destinations
Updated about 20 hours ago