Sometimes, like when your bot switches between automation and a live agent, a single representation of your bot isn’t enough. The new Persona API, now in open beta, allows developers to introduce “personas” into their Messenger experiences, making it easy to switch the in-thread user icon and display name for your bot on the fly. The persona icon and name are fully customizable by you. This enables many common uses of the Messenger Platform, such as customer support, where a bot may want to visually show that the person is now chatting with a live agent. A bot may only invoke one persona at a time.
Check out the Persona API docs for full usage details.
Many of you have told us you want an easier way to integrate the customer chat plugin into WordPress sites, and in this release we’re delivering. The official customer chat WordPress plugin is now available on wordpress.org, making it simple allow visitors to chat with your Messenger bot on your WordPress site.
Before now, bots that used message tags to send messages outside the 24+1 standard messaging window were only allowed to send generic templates. After a review, we’ve lifted this restriction as of this release, so now you can send any template or just text in a tagged message. We hope this opens up new possibilities for how you send non-promotional messages via tags. Please note that all messages must continue to adhere to the specific use cases allowed for each tag and follow all relevant Messenger Platform policies.
In addition to updating the ways you can use tags, we’ve added a BUSINESS_PRODUCTIVITY tag. For full details on the allowed use cases for this tag, visit the Message Tags documentation.
In February, we changed the permission to send non-promotional content as subscription messages from an app-level to a Page-level permission. Subscription messages enable a business or developer the ability to send such messages outside of the 24+1 policy. Please remember that if your bot was granted permission at the app level, you must request and be approved for the new Page-level permission by December 31, 2018. This applies to all Pages, and we encourage you to migrate to the Page-level permission as soon as possible to avoid any disruption to your ability to send subscription messages.
For more information on how to migrate from app-level to Page-level subscription messaging permission, see Transitioning from App-level to Page-level Subscription Messaging.
Question? Comments? We’re always looking for new ideas on how we can give you everything you need to build great experiences on Messenger that people love, so let us know!
P.S. Don’t forget to join the Messenger Platform Developer Community group for answers to common questions and to chat with other developers.
How Our Focus on Privacy Impacts Developers
Today, we’re sharing some of the changes we’ve made to our privacy program over the past year and examples of the new ways we’re operating to ensure we protect people’s privacy. At Facebook we are committed to building a safer, more sustainable platform to strengthen trust with people and continue to drive long-term value for our developers. Simply put, protecting the privacy of the people who use our products is a responsibility we share with all developers on our platform.
We’ve made changes to put privacy at the core of everything we do. The new Platform Terms and Developer Policies are a starting point to ensure businesses and developers clearly understand their responsibility to safeguard data and respect people’s privacy when using our platform and tools.
We’ve also continued to refine and streamline our App Review process which will ensure consistency for all developers. This includes changes that help developers build business solutions and tools as well as have additional control over the data permissions they request and the ability to remove them when no longer needed.
Finally, we introduced Data Use Checkup, a new annual workflow to drive accountability for all Facebook platform developers. With Data Use Checkup, developers are required to review the permissions they have access to and commit that their API access and data use comply with the Facebook Platform Terms and Developer Policies in order to keep their API access.
In addition to simplifying and clarifying developer responsibilities, we’re also proactively taking action against companies and individuals who abuse our platform. Earlier this month, we filed a lawsuit against two companies that used scraping to engage in an international data harvesting operation, and a few weeks ago we took action against two companies operating fake engagement services.
These improvements are intended to help create a better privacy foundation for developers and we encourage all developers to build experiences using a privacy-first approach, with principles such as data minimization as their guide.
As a reminder, developers will be required to complete Data Use Checkup within the next several months in order to maintain API access. If you have yet to go through Data Use Checkup, you’ll be receiving a Developer Alert triggering an email to your app’s administrators and notification in your App Dashboard, notifying you to complete the process.
To prepare for the process, make sure you’ve updated contact details and app administrator designation for each app within your organization. You can also learn more on the new Platform Initiatives Hub.
We know user privacy is just as important to our developer community as it is to us. Thank you for continuing to partner with us as we build a safer, more sustainable platform.
Preparing for Apple’s App Store Data Disclosure Requirements
To support our developer and advertising partners with the upcoming iOS 14 App Store data disclosure requirements, we have consolidated previously released public information that explains Facebook’s data collection practices for the Facebook SDK to make it easier for you as you fill out the App Store Connect questionnaire when it’s released.
To provide functionality within the Facebook SDK, we may receive and process certain contact, location, identifier, and device information associated with Facebook users and their use of your application. The information we receive depends on what SDK features 3rd party applications use and we have structured the document below according to these features.
App Ads, Facebook Analytics, & App Events
Facebook App Events allow you to measure the performance of your app using Facebook Analytics, measure conversions associated with Facebook ads, and build audiences to acquire new users as well as re-engage existing users. There are a number of different ways your app can use app events to keep track of when people take specific actions such as installing your app or completing a purchase.
With Facebook SDK, there are app events that are automatically logged (app installs, app launches, and in-app purchases) and collected for Facebook Analytics unless you disable automatic event logging. Developers determine what events to send to Facebook from a list of standard events, or via a custom event.
- email address, name, phone number, physical address (city, state or province, zip or postal code and country), gender, and date of birth.
There are two scenarios for applications that use Facebook Login via the Facebook SDK: Authenticated Sign Up or Sign In, and User Data Access via Permissions. For authentication, a unique, app-specific identifier tied to a user’s Facebook Account enables the user to sign in to your app. For Data Access, a user must explicitly grant your app permission to access data.
Note: Since Facebook Login is part of the Facebook SDK, we may collect other information referenced here when you use Facebook Login, depending on your settings.
We may also receive and process the following information if your app is integrated with the Facebook SDK:
- Device identifiers;
- Device attributes, such as device model and screen dimensions, CPU core, storage size, SDK version, OS and app versions, and app package name; and
- Networking information, such as the name of the mobile operator or ISP, language, time zone, and IP address.
Audience Network SDK
We may receive and process the following information when you use the Audience Network SDK to integrate Audience Network ads in your app:
- Device identifiers;
- Device attributes, such as device model and screen dimensions, operating system, mediation platform and SDK versions; and
- Ad performance information, such as impressions, clicks, placement, and viewability.
Messenger API to support Instagram
Today, we are announcing updates to the Messenger API to support Instagram messaging, giving businesses new tools to manage their customer communications on Instagram at scale. The new API features enable businesses to integrate Instagram messaging with their preferred business applications and workflows; helping drive more meaningful conversations, increase customer satisfaction and grow sales. The updated API is currently in beta with a limited number of developer partners and businesses.
Instagram is a place for emerging culture and trend creation and discovering new brands is a valuable part of this experience. Messaging plays a central role in helping people connect with brands in personal ways through story replies, direct messages, and mentions. Over the last year, total daily conversations between people and businesses on Messenger and Instagram grew over 40 percent. For businesses, the opportunity to drive sales and improve customer satisfaction by having meaningful interactions with people on Instagram messaging is huge.
“Instagram is a platform for community building, and we’ve long approached it as a way for us to connect with our customers in a place where they are already spending a lot of their time. With the newly launched Messenger API support for Instagram, we are now able to increase efficiency, drive even stronger user engagement, and easily maintain a two-way dialogue with our followers. This technology has helped us create a new pipeline for best-in-class service and allows for a direct line of communication that’s fast and easy for both customers and our internal team.” – Michael Kors Marketing
Works with your tools and workflows
Businesses want to use a single platform to respond to messages on multiple channels. The Messenger API now allows businesses to manage messages initiated by people throughout their Instagram presence, including Profile, Shops, and Stories. It will be possible for businesses to use information from core business systems right alongside Instagram messaging, enabling more personal conversations that drive better business outcomes. For example, businesses integrating with a CRM system can give agents a holistic view of customer loyalty. Furthermore, existing investments in people, tools, and workflows to manage other communication channels can be leveraged and extended to support customers on Instagram. This update will also bring Facebook Shops messaging features to the Messenger API so businesses can create more engaging and connected customer experiences.
To get started, businesses can easily work with developers to integrate Instagram messaging with their existing tools and systems.
Increases responsiveness and customer satisfaction
Customers value responsiveness when they have questions or need help from businesses. For the first time on Instagram, we’re introducing new features that will allow businesses to respond immediately to common inquiries using automation, while ensuring people are seamlessly connected to live support for more complex inquiries. One of our alpha partners, Clarabridge, reported their client brands had improved their response rate by up to 55% since being able to manage Instagram DMs through their platform.
The updates to the Messenger API are part of our overall effort to make it easier for businesses to reach their customers across our family of apps.
Messenger API support for Instagram is currently in beta with a focus on providing high quality, personalized messaging experiences on Instagram while increasing business efficiency. Adidas, Amaro, Glossier, H&M, MagazineLuiza, Michael Kors, Nars, Sephora and TechStyle Fashion Group and other consumer brands are already participating in the beta program. We are excited about early results some businesses saw during alpha testing, including higher response rates, reduced resolution times, and deeper customer insights as a result of integrations. We’re also testing with a limited number of developer partners; and are delighted at the initial response.
“On average, brands have saved at least four hours per agent per week by streamlining social community management within the Khoros platform, plus shortened response rates during business hours — which is crucial to meet as customers who message brands on social media expect a quick reply.” – Khoros