Skip to main content
Solved

Track changes of attribute from specific state to specific state


Our business has keys, but I haven't found how they can work in CustomerIO. Maybe you know how it can work?

Keys:

We have an attribute, for example, 'current_plan.' It is a string, and the business wants to track the attribute changing from 'one_state' to 'second_state.'

Only one transition from 'one_state' to 'second_state' is interesting; other types of changes are not interesting. For example:

null → 'second_state'

'other_state' → 'second_state'

 


From my little research, I haven't found what I need. I hope you can help me with it. Thanks!

Best answer by Felix

Hey Pkosykh,

If I understand you correctly you want to change attributes in case a person will be created or another attribute changes, correct?

If so, you can create a campaign that has only the “create or update a person” element in it. There can trigger the campaing either by the event in which the attribute with the values one_state or second_state is included or use a segment.

You can then use the “create or update a person” to set the attribute to first_state or second_state. In the example below I used the attribute fruit_name.

 

Hope that helps,

Felix

 

 

 

View original
Did this topic help you find an answer to your question?

2 replies

Felix
  • Novice
  • 223 replies
  • Answer
  • July 29, 2023

Hey Pkosykh,

If I understand you correctly you want to change attributes in case a person will be created or another attribute changes, correct?

If so, you can create a campaign that has only the “create or update a person” element in it. There can trigger the campaing either by the event in which the attribute with the values one_state or second_state is included or use a segment.

You can then use the “create or update a person” to set the attribute to first_state or second_state. In the example below I used the attribute fruit_name.

 

Hope that helps,

Felix

 

 

 


  • Author
  • 1 reply
  • July 30, 2023

Thanks, Felix.

It’s look interesting. but it will be work if before attribute not_exist.

For my case

on start attribute should already exist and be equal “first_state” and if attribute change to second_state


i have plan b). 

i send event by api when my attribute change on my backend. and in customerIO i setup company what wait it specific event


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings