The wait condition won't work in this instance, as we max it out at 30
days. There will be product improvements in the future that should help
to make tracking message and Journey IDs much easier. Another possible
solution would be to create a profile flag i.e. NPS_Value and at the end
of your Surve...
@Ikmoo another option to consider would be to create a feedback listener
event sequenced after the action. If the 3rd party action that you are
calling has the option to post feedback via a webhook endpoint, you
could look to capture this fedback as a new experience event, allowing
you to then recor...
@AmitK as @anuhya-tad mentioned it would be good to get some further
details on where the error is occurring. Are you able to send any test
profiles through execution? Some other questions that would help to
troubleshoot: In your custom action setup what type of authentication
are you using? or no a...
Hi @andreacastillom we are planning to release functionality around this
in the fall. We have a beta just kicking off. Please send me a direct
message if you would be interested in participating in the beta.
In addition to what @Sneha-Parmar mentioned with custom actions, if you
have RTCDP destinations you can use the "Update Profile" action in your
Journey to update profiles to include in a Facebook activation segment.
Then in the Facebook destination you can grab an exported audience based
on segment ...
Additional rules are being developed. For now, there is the ability to
set suppression list rules at the Message preset leave. Also many
customers today are using Segment rules and Policy rules to