Messaging, remote config, and rules
Messaging
Section titled “Messaging”Use Configure → Messaging to edit the app’s templates and notification workflows. Check the selected language, subject, sender, required variables, and rendered content. Email source can use supported MJML, HTML, or text formats; use the template editor’s preview before a send.
Template changes do not implement the receiving app’s navigation or notification permission flow. Test the destination link or action on the actual platform. For Support replies, read the conversation and review any AI draft before sending it.
Remote config
Section titled “Remote config”Use Configs for values the app knows how to read. Decide the key, type, meaning, and behavior for missing/invalid values before using it. A dashboard edit does not automatically create a new app feature.
Keep credentials out of remote config. Verify the app receives the change through its normal SDK flow; do not add polling to every screen.
Rules evaluate supplied input to decide supported behavior. Define which input is available and test matching, non-matching, missing, and malformed cases. Keep rules understandable to the next person operating the app.
Rule webhook actions are advanced conditional callbacks. For ordinary event delivery, use an outbound webhook destination.
In-app surfaces
Section titled “In-app surfaces”Use Surfaces for app messages and Campaigns when targeting or scheduling should be controlled remotely. Check localization, accessibility, dismissal, frequency, and actions. A message should have one clear purpose and a useful next action.
For a feedback form that collects structured answers, use a Survey and an existing campaign placement.