Engagement

Provides a system for attaching Engagement Scores to various interactions with website visitors, primarily through use of the Rules module or API calls.
User Interface (view only):redhen/contact/%/engagements
Configuration:admin/structure/redhen/engagement_scores | admin/config/workflow/rules/

Note: The term "Engagement Score" is used in this explanation, and in the RedHen Interface, to mean a few different things. Just like an American Football team has a "score" at the end of the game which is the sum total of all the individual "scores" they made during the game, many of which were worth different amounts of points than one another because they are different types of scores (touchdowns, field goals, etc). In RedHen Engagement, each Contact, like a Football Team, has an Engagement Score which is the sum total of a bunch of individual Engagement Scores, which are individual instances of certain types of Engagement Scores. Confused yet?

When the Engagement module is enabled, each RedHen Contact in the system is given an auto-calculated Engagement Score field. It's value will be 0 until you create some types of Engagement Scores through the Configuration interface and attach instances of those scores to Contacts in some way. An Engagement Score type consists of a text Label and a numeric Score (like saying "a Touchdown is worth 6 points"). The Score can be negative, but it must be an integer. Once you have created some Engagement Scores, you can start to attach them to your Contacts.

There are a number of reasons for creating labeled Engagement Scores with numeric values assigned rather than simply attaching a numeric value to each interaction. One is that it centralizes the value judgement, so that whoever is deciding how to rate engagements can do so abstractly and from a single place in the system. Similarly, it separates the act of judging engagement from setting up engagement tracking automation, or adding an engagement score to a Note. Best of all, it allows you to re-evaluate the value of a particular type of interaction by changing the Score at a later date, and having all past interactions reflect the new value.

Example: Let's say you want to track 3 types of engagement: forum comments; an event registrations; and newsletter signups. You have 2 types of events, and you consider one to be a higher level of engagement. So you create four Engagement Scores: "Newsletter Signup", worth 2 points; "Forum Comment", worth 5 points; "Event Registration", worth 15 points; and "Major Event Registration", worth 25. After a few months of watching the Engagement Scores on your contacts in RedHen as you track each of these types of interaction, you decide that a Newsletter Signup is worth more than 2 points: you can go in and adjust the value of this score without having to edit each engagement created by a newsletter signup.

There are 3 ways to connect Engagement Scores to your Contacts:

1. The simplest is by using Notes. When you create a Note with the Engagement module disabled, you'll see a drop-down at the bottom of the Note's edit screen to select an Engagement Score. This allows you to integrate tracking of engagement interactions that occur offline.
2. Of course, the point of Engagement tracking is to have automated scoring. Engagement is built to integrate with the Rules module, so you can use Rules to automatically attach Engagement Scores to Contacts based on any Rule-enabled action. (requires the Rules Module.)
3. If you want to get fancy, have a closer look at the API functions in the RedHen Engagement module, and code your own custom Engagement tracking automation to complement the built-in functions.