Pass safe Messenger metadata and tags

Attach routing context without leaking secrets or unbounded customer data.

Steps

  1. Choose a small allowlisted set of user and conversation metadata your support team actually uses.
  2. Set metadata and tags before starting or sending a conversation through the Messenger SDK.
  3. Verify that values appear in the support context and do not control privileged actions by themselves.
  4. Remove stale fields when the user signs out or the business context changes.

Important notes

  • Never pass passwords, tokens, payment data, private message bodies, or provider payloads as Messenger metadata.

If you still need help

Search this Help Center using the exact feature or visible error. If the issue continues, use Call TidyAnswer support from the Help Center navigation. Include any public reference and the approximate timestamp, but never include passwords, access tokens, provider credentials, or raw webhook payloads.