Skip to content

Introduction

Our SDKs offer a vast amount of functionality that you can integrate into your game. You can request video and banner ads, send game events, generate invite links, interact with the user account, etc. It is not mandatory to integrate all the SDK functionality. For example, not all games require a user account. The integration scenarios below will help you decide what functionality you need to integrate.

Integration scenarios

SDK Scenarios

All scenarios have access to advertisement and in-game functionality via our SDKs. HTML5 and Unity SDKs support all the scenarios. Other SDKs might miss some functionalities.

Scenario 1: Games without user accounts

This is the easiest scenario to integrate, which allows you to monetize your game with video or banner ads. If you are new to CrazyGames, we recommend that you integrate this scenario:

  • Monetization via video or banner ads
  • Game play and loading events
  • User account integration is not required
  • The game stores data in localStorage (HTML5) or PlayerPrefs/Files (Unity). Our APS system will back it up.
  • In-game purchases aren't available in this scenario

Scenario 2: Standard Integration

If your game uses Usernames, avatars, and you want to save progress, but you don’t want the hassle of maintaining your own back-end, this scenario is for you:

  • Monetization via video or banner ads
  • Game play and loading events
  • Access and use CrazyGames user data (username & avatar) for logged-in users. See the User module docs from the appropriate SDK for more information.
  • The game stores data in localStorage (HTML5) or PlayerPrefs/File (Unity). Our APS system will back it up for each logged in user across their devices. Soon, we will integrate progress save functionality into the SDK itself, so you'll have more control over what data is synced across the devices where the user is playing.
  • Using in-game purchases with the Xsolla token received from getXsollaUserToken() function, which links the purchases to the CrazyGames user account. This functionality is supported for invited games only.

Scenario 3: Games with in-game accounts, with a custom back-end

For the games with an account system and a custom back-end where the user data is stored.

  • Monetization via video or banner ads
  • Game play and loading events
  • The appropriate user and authentication scenarios are implemented. See the User module docs from the appropriate SDK for more information.
  • We expect you to save the user progress on your back-end.
  • Games using in-game purchases should use the CrazyGames Xsolla account. You can either interact with Xsolla via getXsollaUserToken(), which links the purchases to the CrazyGames user account, or use the Xsolla keys provided by us. This functionality is supported for invited games only.

Automatic progress save

Our portal automatically saves and syncs game data for the users that are authenticated. We recommend you have a quick look at how the APS system works, to ensure that your game can fully benefit from it.

Technical support for SDK integration

Once your games reach 50k gameplays (combined), we can offer you technical support with SDK integration. You're free to integrate the SDK before you reach 50k plays, but if you do so, we can not offer you support. Note that you'll also earn revenue without SDK advertisements (see the FAQ for details). The 50k gameplay requirement allows us to give each developer individual feedback on ad placements and integration.

Quality Assurance Tool

You can use our QATool to test your SDK implementation. You can use the standalone version without creating a submission. With the QATool you can:

  • Run your game as it would on Crazygames.
  • Try out the main different resolutions that we use on the site.
  • Test all the SDK features that you implemented and get feedback about it.

Go to QA Tool