Injecting Conversation Metadata

By default, the webapp channel does not include any specific context about the conversation (see the _metadata object documentation). In some cases, it can be useful to load the webapp (or chatbox) with pre-existing metadata.

Some common scenarios:

  • the bot is loaded in a website where the user is already known: in that case, we may be interested in injecting the user's context (name, email...) inside the conversation.

  • the user is authentified on the parent website: in that case, we may want to inject an authentication token into the user's conversation for subsequent calls.

  • the same bot is used across several websites and we want to know which website the user is currently visiting: in that case we can inject a unique website identifier into the conversation.

The injected data is available in the _metadata global variable, available in every flow. The code of the example above is:

  say "Hi {{_metadata.firstname}}"
  say QuickReply(
    "Your email address is: {{}}. Do you confirm?",
    buttons=[Button("yes"), Button("no")]

To add custom metadata in a webapp, simply add the encoded (with javascript's encodeURIComponent function) JSON string of the metadata you want to inject to the query parameters of the webapp's URL. The URL of the webapp in the example above would be:


Customizing the UI

You can change the appearance of the webapp by visiting the Appearance tab of the webapp configuration panel. This lets you have even more control over the final experience for your end users, and match your own branding even better!

Many elements are configurable:

  • Chatbot avatar, header card color and background image

  • User bubble colors

  • Hiding the CSML branding

  • Disabling the speech input

Last updated