Reachora App Tracking for ESC

This is currently being negotiated with Conference Compass, but should be usable for other apps as well.

Data Format

The data package is one request per view, JSON-encoded, which holds the following payload:

{
    "event_timestamp": <when the event occurred, ISO8601-encoded>,
    "app_install_id":  <unique identifier for the user's phone>,
    "client_uid":      <user id that we can connect with a website ESC user>,
    "view_id":         <identifier for the particular view>
}

The event_timestamp field is optional – if it’s missing, we’ll use the timestamp of when the event arrived (assuming that it’s arriving live).

The client_uid can also be missing or set to null if there’s currently no registered user.

The view_id can be any identifier, but we’ll assume it’s one of the following:

• presentation_<numericId>
• session_<numericId>
• subsession_<numericId>
• classifier:sessiontopic_<topicName>
• Or, anything that looks like a speaker name (hopefully could be a speaker id at a later time)

Endpoint

The URL to POST event payloads to would be:

https://in.reachora.io/app_events/<clientId>/resource_views

For conference compass in particular, the client id would be esc-cc, so:

https://in.reachora.io/app_events/esc-cc/resource_views

Alternatively, esc-cc-app-test can be used for sending test data.

Batch Sending

To batch up several events, use the “batch” endpoint:

https://in.reachora.io/app_events/esc-cc/batch_resource_views

The events are expected in a JSON list with the same contents as described above:

[
    {"view_id": "abc1", ...},
    {"view_id": "xyz2", ...},
    ...
]