Use attribute change in a segment

@SoleneGreenly I also come across this requirement from time to time and it would be really helpful if this feature would be available directly in c.io: attribute changes kind of automatically be logged as events that can be used as event-based filters in segments (or as campaign triggers). @Jordan  is this something that is being considered at c.io?

Btw a similar question has been asked here, but does imho not provide an answer to your exact question.

Possible workarounds that I have tried:

Track additional Event

If you can, let your application also send the attribute change as event (e.g. with from/to event attributes) that’s tracked to c.io’s API. You can then use those events as filters in segments or triggers for your campaigns

Use a campaign that creates/logs events

If you want to go without developer changes needed, you can create a campaign in c.io Journeys that logs an event (as “send event” action in the workflow) when people enter a segment. The segment is created in a way that it filters for a specific value of your attribute. You can then use the events that are added to people via this campaign to create segment filters or trigger campaigns.

To give you an example: 

• let’s assume I have an attribute for user type, which can be free or premium, and I want to know changes to this attribute from one values to the other and e.g. discover when someone started premium (changed from free to premium)
• create a segment with user_type equals “premium”
• create a segment-triggered campaign for this segment (but do not process existing segement members! when activating the campaign)
• add only one “send event” action similar to my example, which can include event attributes based on current profile’s attributes to be stored along with the event according to the screenshots below.
• feel free to repeat the same for other values of the same attribute that you want to monitor, e.g. changing from “premium” back to “free” in my example (where my segment could e.g. be user type = free and at least one of this “premium started” events has been performed.
• note: this only works if attribute values are pre-defined distinct values. it will therefore not work in a case where you e.g. want to monitor users changing their email address
• note that this only creates events from the moment you turn on your campaign, no back-filling.

Hope this helps? Again, it would be much better if c.io would add this as native feature!!

Hi!

thank you for your answers. It would indeed be a great feature!
We’ll have to go with an additional event, should work fine for now.