Manage session using audience cache pattern (Aadvanced)

Stream Personalization implements session management by caching per user specific information like HLS sequence number, ad decisioning to give a few examples.

To cache this information, an audience cache pattern must be configured, acting as a unique key to keep track of user information.

To configure an audience cache pattern, follow these steps:

1. Click the Advanced tab.

2. Enter the appropriate value for each parameter:

   Parameter	Description
   Audience cache pattern	Configure the audience cache pattern, usually leveraging query parameters from the viewer request. In our example below, we assume that the viewer manifest request includes a set of query parameters: http://cdn.com/live-hls/channel1/index.m3u8?userID=1234&deviceID=android&... Values 1234 and android are accessed using the following pattern: {query.userID} and {query.deviceID}. The resulting audience cache would thus look like: 1234_android. This will serve as a key to store session information for manifest manipulation purposes.
   Signing key	Signing key used for manifest signature.

   Audience cache pattern configuration example