Message Tags
Message tags allow messages to be marked with a particular tag. The meaning and effect of each tag depend on each specific platform. Using Conversations API, it's possible to set a MessageBird Message Tag, which will be converted to a platform-specific message tag.
The table below displays the correspondence between MessageBird Message Tags and platform-specific message tags.
Currently message tags are only supported by Facebook Messenger.
| MessageBird Message Tag | Facebook Message Tag | Platform-specific Description |
|---|---|---|
| event.update | CONFIRMED_EVENT_UPDATE | Send the user reminders or updates for an event they have registered for (e.g., RSVP'ed, purchased tickets). |
| purchase.update | POST_PURCHASE_UPDATE | Notify the user of an update on a recent purchase. |
| account.update | ACCOUNT_UPDATE | Notify the user of a non-recurring change to their application or account. |
| human_agent | HUMAN_AGENT (Closed BETA) Apply for access | Allows human agents to respond to user inquiries. Messages can be sent within 7 days after a user message. |
More details about Facebook Message Tags are available here: https://developers.facebook.com/docs/messenger-platform/send-messages/message-tags/
Here's an example of HTTP request you can perform to the Conversations API POST /v1/send endpoint using the tag account.update, which corresponds to the Facebook ACCOUNT_UPDATE message tag.
curl -X "POST" "https://conversations.messagebird.com/v1/send" \-H 'Authorization: AccessKey <access-key>' \-H 'Content-Type: application/json; charset=utf-8' \-d $'{"content": {"text": "Sample message using a tag"},"to": "107998841006481","type": "text","tag": "account.update","from": "8145h20547u54cb7bcde4d5c0bb40a35"}'
A few details about the HTTP request above:
- The field to must contain a valid Facebook recipient identifier, or an existing contact ID
- The field tag must contain one of the aforementioned MessageBird message tags. You can't use platform-specific message tags. For example, ACCOUNT_UPDATE
- The field from must contain a valid Facebook channel ID
The HTTP response looks like the following:
{"id": "7d9b3s4f2e3g44ab5cd72a31c133c5c1","status": "accepted","fallback": null}
