Appcharge supports the use of the sessionMetadata field in most of our APIs to include contextual information about a player’s session. We recommend using sessionMetadata for any additional data that is not strictly required by Appcharge to execute a flow, but which can help publishers add context, assist with debugging, or store custom attributes. The sessionMetadata entity is JSON-based and provides a flexible container for storing relevant session details. Checkout Only Solution Flow
  1. The publisher sends sessionMetadata when calling the Create Checkout Session API.
  2. Appcharge stores the sessionMetadata in the Player Checkout Session.
  3. The sessionMetadata is returned to the publisher in the Player Order Reporting Webhook and in player session-related Order Events 
Webstore Solution Flow
  1. The sessionMetadata is included in the response to the Player Authentication Webhook
  2. Appcharge stores the sessionMetadata in the Player Session.
  3. The sessionMetadata can be overridden by the response from the Personalization API
  4. The sessionMetadata is returned to the publisher in the Player Order Reporting Webhook and in other player session-related events.
..