The ability to track and create campaigns not only on purchase activity but also non-purchase activity is a key reason many merchants choose the Clutch platform.
Events are categorized for tracking and reporting. Examples of event categories are: Social, Ecommerce, Feedback, Milestone and more. Events can be used to simply track an action or desired behavior in the Clutch platform, or can be used to drive and reward customers for completing certain calls to action. Events are recorded on a customer’s card/account and will provide valuable insight into the customers engagement and interests.
Some examples of event based campaigns that a merchant may decide to use Clutch for include:
- Get 50 bonus points for Writing a Review
- Purchase discount incentive after 3 Website Visits and no purchase
- Triggered communication after 10 Cart Adds
Besides crafting specific campaigns, having event data passed to Clutch will allow merchants to perform customer segmentation based on event data, see what events correlate with specific customer milestones, as well as run campaigns like those identified above.
While we do have some standard events, any number of custom events may also be created and used.
In order for your integration to use Events, you’ll need to have some configured in the Clutch Platform for use during the development and testing process. You’ll need to work with your Clutch Integration support person to have them configured and to provide the Event ID’s to be used. The updateAccount API call is used to communicate and record an event in the Clutch platform. If the brand chooses to reward on Events, as discussed above, each event will also need a corresponding campaign rule in the Clutch Campaign Manager. Your support contact can assist with this configuration as well.
See example of configured events in the Clutch Portal:
Clutch recommends that each identified (logged in) visit be passed to Clutch.
More information on implementing events can be found in the Event section of our API docs.
