You must send one message to the user within 24 hours from the time the user opted in to being contacted by your business on Messenger. You cannot use Message Tags to send the initial message to the user. Once you have started the conversation in Messenger, you can use Message Tags to send messages more than 24 hours after a user’s last message or user-initiated contact only if your message meets one of the approved Message Tags use cases. For more details, see Message Tags in the Messenger Platform documentation.
If you intend to use
message_tags related messages after the initial 24 hour window, consider saving the
You must send one message to the user within 24 hours from the time the user opted in to being contacted by your business on Messenger.
Users can opt out of messaging at the individual thread level by selecting “Turn off messages.”. They can also mute or block your business’ messages. You must immediately respect any request to block, discontinue, or otherwise block, discontinue or otherwise opt out of messaging with your business. For more details, see How do I turn messages from a business on or off in Messenger? in the Help Center documentation.
You must send one message to the user within 24 hours from the time the user opted in to being contacted by your business on Messenger. You cannot use Message Tags to send the initial message to the user. Once the conversation with the user has started, you can send promotional messages within 24 hours of a user’s last message. Otherwise, if you’d like to send promotional updates to the user outside the 24 hour messaging window, consider using Sponsored Messages or a One-Time Notification.
The first message sent to users should familiarize users with the experience you offer in Messenger Platform. Using Quick Replies on the first message generally drives engagement. Also consider using generic templates, media temples or any other template that helps users understand the experience being offered.
All the apps will receive the messaging_optin event containing a valid
login_id, regardless of HOP configuration. This id can be used by all the apps to send messages.
The login_id is generated before the authentication flow finishes, so as soon as an app receives the login success callback, they can send a message using the generated
login_id, even if the Webhook event didn't arrive.
No, the event will only be triggered once for users that accept the permission.
Make sure to include
reset_messenger_state=1 on the login flow. This will trigger the event again for users that have a role in the app being tested only. This is only possible using the
FB.login() method or a manual login URL.
You can use a manual login URL that triggers the login flow on any browser. When the Facebook Login popup is opened, the state is reset. You can close the window before logging in and the next time the mobile flow is triggered, the
messaging_optin event should be sent.
For users to be able to test this integration before submitting for App Review, they need to have a role in the app.
For apps to be able to send messages using the received login_id, they need to have pages_messaging permission. Observe that when using the
login_id, the field in the recipient object is named "login_id" instead of "id".