Introduction
In this quick tutorial, we will be discussing a common query related to setting up campaigns in Customer.io where the trigger and goal events are the same but have different event attribute values.
Problem
Consider a scenario where you want to set up a campaign with an event attribute, 'signing_complete'. In order to enter the campaign, the event’s attribute must be equal to “false”. The campaign journey begins, and the goal is for the ‘signing_complete’ value to become ‘true’. In other words - the campaign is designed to push people towards completing a process that they started some time earlier.
The question is, will the system recognize an event attribute change and count it as achieving the goal, or does a new event need to be triggered?
Solution
In Customer.io, it isn't possible to change the event attributes of a sent event. So, if you want to record an attribute change (e.g., 'signing_complete' changes from false to true), you will need to send a new event with the same name but updated attributes from your backend. Once the new event with the correct attributes is recognized by Customer.io for the customer’s profile, it will count as achieving the goal, according to your campaign's setup.
Resources
Campaign documentation