---
title: Session Participation Payload
slug: docs/session-participation-payload
createdAt: 2025-01-16T01:31:09.127Z
---

## Overview

When a person participates with a session an SNS message is published to a Jomablue-owned topic and the value of the SNS ‘message’ will have the following structure. This is published every time a Person's attendance in a session is calculated and has a change.&#x20;

This does not include 'session' resource, but the person-to-session-participation (ie, session attendance)

:::hint{type="info"}
It's common for Session names to change - we recommend using ID's over matching Strings/Session Names
:::



### Attributes

A description of each attribute in the Session Participation payload can be found below:



- `resource_type`   string
  Must be ‘session\_participation’.
- `generated_at`   timestamp
  Timestamp in the following format: 2025-07-02T19:15:12.511Z.
- `context`  **object**
  - `event_id`   string
    A unique identifier. Alphanumeric (upper and lower case), hyphens, forward slash and underscores. No whitespace.
  - `event_name`   string
    Alphanumeric (upper and lower case), special characters and whitespace.
  - `event_metadata`   object
    Keys must only contain alphanumeric (upper and lower case), hyphens, forward slash and underscores. No whitespace.
    Values can contain Alphanumeric (upper and lower case), special characters and whitespace.
  - `person_first_name` string
    Alphanumeric (upper and lower case), special characters and whitespace.
  - `person_last_name` string
    Alphanumeric (upper and lower case), special characters and whitespace.
  - `person_email` string
    A correctly formatted email address. May contain an empty value.
  - `person_phone` string
    Alphanumeric (upper and lower case), special characters and whitespace. May contain an empty value.
  - `person_company`  string
    Alphanumeric (upper and lower case), special characters and whitespace. May contain an empty value.
  - `person_id` string
    A unique identifier. Alphanumeric (upper and lower case), hyphens, forward slash and underscores. No whitespace.
  - `person_organisation_uid` string
    A unique identifier provided from external systems to Jomablue (eg: A Salesforce Lead/Contact ID). Alphanumeric (upper and lower case), hyphens, forward slash and underscores.&#x20;
  - `session_id` string
    A unique identifier. Alphanumeric (upper and lower case), hyphens, forward slash and underscores. No whitespace.&#x20;
  - `session_name` string
    Alphanumeric (upper and lower case), special characters and whitespace. May change through an event.&#x20;
  - `session_organisaion_uid` string
    A unique identifier provided from external systems to Jomablue (eg: A Salesforce campaign ID). Alphanumeric (upper and lower case), hyphens, forward slash and underscores.&#x20;
- `identifiers`  **object**
  - `id`   string
    A unique identifier. Alphanumeric (upper and lower case), hyphens, forward slash and underscores. No whitespace. Never empty.
- `data` object
  - `attended` boolean
    Indicating if a person has attended the session or not.&#x20;
  - `updated_at` timestamp
    Timestamp in the following format: 2025-07-02T19:15:12.511Z. Will match created\_at if not updates have been applied.&#x20;
  - `created_at` timestamp
    Timestamp in the following format: 2025-07-02T19:15:12.511Z

***

### Sample Payload

A sample of an session\_participation payload is below.&#x20;

:::CodeblockTabs
session\_participation

```json
{
  "resource_type": "session_participation",
  "generated_at": "2025-01-28T04:27:07.322076Z",
  "context": {
    "event_id": "acme/event/123",
    "event_name": "Sonic Conference 2025",
    "event_metadata": {
      "text": "anything",
      "selector": "option2",
      "predefined": "predefinedValue"
    },
    "person_first_name": "Catherine",
    "person_last_name": "Lebsack",
    "person_email": "catherine.lebsack@example.com",
    "person_phone": "+61491570006",
    "person_company": "Barrows, Heaney and Watsica",
    "person_id": "acme/event_person/123",
    "person_organisation_uid": "4ab9ecb4-91cd-34ba-928e-b6d929b81a1c",
    "session_id": "acme/session/123",
    "session_name": "Session of discovery",
    "session_organisation_uid": "ecb44ab9-91cd-34ba-928e-b81a1cb6d929"
  },
  "identifiers": {
    "id": "acme/session_participation/123"
  },
  "data": {
    "attended": true,
    "updated_at": "2025-01-28T04:27:07.322076Z",
    "created_at": "2025-01-28T04:27:07.322076Z"
  }
}

```
:::



***

### Inferred Sessions Considerations

This section describes Inferred Sessions and considerations around processing this data.&#x20;

Inferred Sessions is an optional feature of Jomablue that allows Jomablue to infer someones attendance of a Session based on the data we have available for a person along with parameters set by the Event Organiser.&#x20;

Traditionally (and if inferred sessions is not used), session attendance is obtained by scanning their badge on entry into the room.&#x20;

This presents two challenges which inferred sessions solves:&#x20;

1. Back to back sessions. When people stay in the room between sessions, the data point of the second session and beyond is never captured.&#x20;
2. Entering a session and changing their mind. If a person enters a session then changes their mind within 5mins, the traditional approach would consider them as attended and therefor receive things like post-event surveys for that session.&#x20;

Inferred Sessions is an algorithm that addresses the two above points based on the data of that person and their interaction across the entire event. Additionally it offers:&#x20;

- A more streamlined onsite experience, attendees don't get the feeling of 'tracking' with so many points of data capture
- Ability for event organisers to define what 'attended' is to them. This is measured as a percentage over time to ensure that 15minute sessions and 60minute sessions can apply the same attended logic.&#x20;

Therefore as data is collect for each individual throughout the day, their attendance is calculated for each individual session. This means that 'attendance' data is not necessarily tied to the physical action of them entering the room - but a calculated output after that fact.&#x20;

:::hint{type="info"}
Attendance Data when Inferred Sessions is used, is usually calculated after the person enters the session room. Generally it's processed towards the end of the session or the end of back to back sessions unless other data is received sooner.&#x20;
:::



If inferred Sessions is not used, the attendance is based only on entry to the session and does not require calculation. These are generally published to SNS immediately.&#x20;

##

## Considerations

1. We publish 'attendance' messages the moment we have enough data to calculate that and mark the person as attended (but that could be minutes or hours after they enter the session)
2. An event organiser has flexibility to change the definition of 'attended'. If that happens, we will re-calculate the entire event and publish the changes. This means that we may publish messages where the person is marked as <u>not</u> attended (after they were published as attended).&#x20;
3. Offline Mode may be used in events with poor connectivity, this may further delay the processing of session attendance.&#x20;



