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 definition.
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
In-app should be coming soon! Direct Mail is in development. If you have
direct mail use cases or customers looking for direct mail please send
me a direct message. Would like to validate against your requirements.
In addition to @Ryan_Morales suggestion, you could look to set a rule
within launch to perform to set a key value pair on the device, or go to
a URL path. Attach or Modify data actions might work for this. That
might be a way to trigger a feature flag. Do you have a conditional rule
that you are looking to add before you trigger the update on the client
Hey John - you will find most of the information you are looking for on
our dedicated Mobile SDK doc site: https://sdkdocs.com Most of the tags
are not deployed in Launch, but can be controlled via Launch. Typically
a trackAction or trackState call is made within the app to denote a
button press or view switch etc. With each one of these calls you can
attach additional context data. Data Elements can be created within
Launch to alias the data flowing through the mobile app for additional
So it seems like instead of "Attach Data" you want to use the "Modify
Data" action. Ahead of the ACTION you would want to put a condition on
the event. Or use the Mobile Core TrackAction event as your trigger.
Directions for integrating ReactNative can be found here:
For both iOS and Android we recommend initializing the SDK in the native