> ## Documentation Index
> Fetch the complete documentation index at: https://docs.appcharge.com/llms.txt
> Use this file to discover all available pages before exploring further.

# About Session Metadata

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](./checkout/checkout-session/create-checkout-session).
2. Appcharge stores the sessionMetadata in the Player Checkout Session.
3. The sessionMetadata is returned to the publisher in the [Grant Award Callback](./checkout/orders/player-order-reporting-webhook) and in player session-related [Order Events](./events/v2/order/order_created)

**Web Store Solution Flow**

1. The sessionMetadata is included in the response to the [Authenticate Player Callback](./webstore/player-authentication/authenticate-player-callback)
2. Appcharge stores the sessionMetadata in the Player Session.
3. The sessionMetadata can be overridden by the response from the [Personalize Web Store Callback ](/../../api-reference/webstore/personalization/personalize-webstore-callback)
4. The sessionMetadata is returned to the publisher in the [Grant Award Callback](./checkout/orders/player-order-reporting-webhook) and in other player session-related events.

..