You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, we have added a new dropdown within "Update Contact" for Consent status (Opt in/ Opt out).
But if we are using Split by Contact variable- Consent status- Opt in (has the phrase/ any of the words), the flow isn't working as expected. This is one edge case which we might have missed.
The text was updated successfully, but these errors were encountered:
Since we don't store the consent status in contact fields, split by contact field node won't work.
You can use split by custom expression node for this purpose.
You can checkout this flow for reference. @KrishnaDwibhashi2
If Consent status--> Opt-in is selected Vs Settings--->Opt in is done- Aren't they saved under the same thing? If not, can you explain where Consent status answer is stored?
The approach you shared (split by custom expression) it will be confusing (or not so easy) for users to use. Is there a way for us to ease that by adding ability to use Split by Contact variable- Consent status- Opt in (has the phrase/ any of the words)?
We are storing that in optin_status so inside split by custom expression node we are splitting on basis of @contact.optin_status
It is true for opted in user and false for opted out
Recently, we have added a new dropdown within "Update Contact" for Consent status (Opt in/ Opt out).
But if we are using Split by Contact variable- Consent status- Opt in (has the phrase/ any of the words), the flow isn't working as expected. This is one edge case which we might have missed.
The text was updated successfully, but these errors were encountered: