In mid-February, Facebook will be introducing a change to their API that will impact Experiences. As part of Facebook s commitment to user privacy, we will only be able to request and display user data (username, avatar, etc.) on user posts or comments made on your owned pages. This will prevent user information shared on your page from being shared with anyone else.
Currently, Experiences uses a Spredfast token to request all Facebook content. This means that once this change goes into effect, user posts and comments to Facebook pages that get sourced in Experiences will show up without user data. We will represent this data-less content as the username Facebook User with a dummy avatar and a user ID of 0. This is how it will be represented in the API and within moderation and visualizations.
The good news is that there is a solution. If you have already authenticated your own pages into Experiences for either higher fidelity Facebook sourcing or Facebook consent, then we will begin using your page token to request content. If you haven t authenticated your own page yet, we recommend doing that now. Once you authenticate, it means we will be able to return the content from your own pages with your user data. For instructions on how to set this up, check out this help document or reach out to our Support team.
Please note that for the next few months, we may not be able to guarantee that you will see your user data 100% of the time while we work toward completing this new Experiences infrastructure solution that will ensure privacy and control over your own page and user data. Please reach out to us if you have any questions about this.
