# Session & Cameras

To authenticate your game and track player metrics at runtime, Frameplay requires an active Session and an in-game Camera.

# Frameplay Session

A session establishes a runtime connection to the Frameplay servers, which is required for loading advertisements.

A session does not need to be stopped, this is handled automatically on application quit.

# Session Parameters

When starting a session some information is required. This links the runtime session to your game on the Frameplay Platform and determines the type of advertisements that will be served.

  • Frameplay Data Asset (Required): This is a reference to the Frameplay Data Asset. This is a crucial part linking the session with the Frameplay Dashboard and authenticating your Game ID and API Key.

  • Player Data (Optional): The player Age, Sex, Gamer ID or Tag and Language can be sourced from a client API or a custom login. This data allows for targeted advertisements.

More information on what data we collect and why.

We limit the frequency that advertisements from the same campaign can be displayed in a single session. This balances advertiser and game player interests, to provide a variety ads within game environments.

# Registered Cameras

We track an in-game camera to determine if the player has seen an advertisement.

Cameras can be registered and deregistered when required. The camera representing the players view should always be registered at runtime.

Read more about Session & Camera implementation in your preferred game engine: Unity, Unreal, Or Lumberyard.

Last Updated: 6/11/2020, 2:14:39 AM