Comment on page
Engagement
The Engagement product offering sits on top of Sentiance's Insights and can used to build coaching modules to increase user engagement and retention in your applications.
The Engagement platform contains the following features. All features can be implemented separately, or together with any of the other features.
A tailorable score, based on Sentiance Insights, adapted for your specific user population & use case. Focuses on the user experience, and is correlatable with other Sentiance scores for risk assessment.
- Can be tailored to focus on a specific end user’s use case, while still being correlatable to other Sentiance score.
- Can be ‘enriched’ with client data
- Can be adapted with of all Sentiance data
Take into account additional ‘chronological’ data and accumulate it once it reaches a threshold. Goal: Encourage users to keep up good behaviour.
E.g it can show a user's:
- Number of ‘good’ trips in a row.
- Maximum amount of times consecutively performed an action
- ‘Focused’ driving streaks
- ‘No speeding’ streaks
- …
A module created as a step-by-step approach for users to improve their driving behavior.
Challenges are designed to work with all the possible Sentiance data and can be tailored based on the specific use case, client, domain, etc.
Includes available in-app messages that provide feedback to the user on their driving behaviour, challenges and streaks and nudges.
Similar to communication messages and can use to build push notifications workflows in an application
Create an in-app reward system based on aggregated Sentiance data. Visualize progress to your users based on specific actions or achievements within the app, providing recognition, motivation, and a sense of progress and accomplishment.
- Badges are fully tailorable. They can be defined based on population data.
- Possible on different types of behaviour
- Driving behaviour
- In-app actions
- Can be combined with other features
Using the V4 GQL interface you can query the UserEngagement field under the User Root Query. The V4 GQL can be queried using the end user's SDK Token or by using the USER READ API Key.
You can invoke the various engagement mutations/actions (e.g
join_group , create_group) using the same V4 GQL interface. All mutations can be found here.Unlike the GQL Queries, the mutation can only be invoke using the SDK Token. And all the mutation operate on a user context level.
There is a special GQL mutation
submit_log_event which can be used to log events/actions/statues being performed by the end user on the mobile application. There is a set of events which must only be used to communicate engagement related actions (e.g communication_message_read, communication_message_dislike); apart of these events you may send any other events with its specific params.
Event Name | Params | Description |
|---|---|---|
user_setup_complete | | When a user completes registration |
profile_complete | | When a user fills all the required profile fields |
permission_granted | location
notification
motion | When a user provides LOCATION_ALWAYS permission |
communication_manually_closed | communication_id
evaluation_id | When a user manually closes a communication message |
Submitting the above events causes different workflows to be triggered in the Engagement Platform. The result of the engagement workflows could be push notifications, communication messages, etc.
The engagement platform returns scores for a user (
UserEngagementScores) and a Transport (UserEngagementTransportScores). The following scores are availabledriving_focused
dirving_no_speeding
driving_smooth
driving_overall
riding_call_while_moving
riding_harsh
riding_legal
riding_overall
Last modified 1mo ago