Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 8 Next »

Our customers wanted to understand how engaged a specific user is with their brand. Engagement score provides this, allowing our users to generate a score that continously changes through interactions with Journey Orchestration Rules and the passage of time. This functionality is provided through three Public Templates.

These Public Templates are:

Setting and Updating the Engagement Score
  • set engagement score will apply a fixed value to the Engagement score for a user overwriting what was in place. The value could be defaulted or set via standard parameters.

  • update engagement score will increment the existing Engagement score either up or down. The value could be defaulted or set via standard parameters. If a value does not exist the value here is set.

Reading the Engagement Score
  • read engagement score will read the current Engagement Score and add this into the Rule flow as a field that can be used by other tiles

Where a Engagement Score value is set or updated the values are set against the CXID used in the rule. As such these public templates can only be used in Rules where a Get CXID (which provides the CXID) has been used in the rule flow ahead of them.

In most cases our customers will be interested in how engaged a user is “at this point in time.” This provides the ability to turn around users who may be becoming disengaged or use the current interest to spark suitable offers. Due to this we want the engagement score to relect the current engagement level of the user to your brand.

Engagement activity that took place months or years ago should not be as significant in the Engagement Score calculation as engagement events created over the last couple of days. Recency adds value to the score. To create the right data we have added an Engagement Score decay function. This will gradually reduce the engagement scores generated by older events with the oldest events decaying the most. This decay function is automatic but should mean that those users that are more active “right now” generally have higher scores than those more active weeks, months and years ago. This does however depend on how they have been involved with your brand.

As an example of Engagement Score decay:

  • An Engagement Score event created 20 days ago would have a decay of about 12% compared to the original value added

  • An Engagement Score event created 40 days ago would have a decay of about 48% compared to the original value added

Engagement Score Public Templates

  • No labels