Facebook Share Counts disappeared? We got your back! Facebook changed up their Share Count API today. The best WordPress social sharing plugin Easy Social Share Buttons for WordPress is fully prepared for that. The updated version 6.2. was released April 18th, 2019 and you can do an automatic update or manual.
You can find more information about the methods you can update Easy Social Share Buttons for WordPress here
Available Counter Update Methods
With the latest update of Facebook API you will now be able to use 2 different API endpoints for reading data. Find out which of the which is the best for you.
- API Endpoint #1 – this is public accessible endpoint for reading Facebook share counter. It does not require any further setup actions and it is active by default in Easy Social Share Buttons for WordPress. This API endpoint is also the one the is active in the client side counter update. As this is a public update method, the number of requests you can send per hour is limited. The other limitation you will have is that this endpoint will return only the number of shares that URL has (read further to see the difference).
- API Endpoint #2 – this is private accessible endpoint for reading the Facebook share counter. To be able to use it you need to create an access token key (find instructions here for creating an application based Facebook access token). This method of updating share counters provide a far more calls that you can send to Facebook for reading the share counter and most important it provides a more detailed information. With this Facebook share counter update endpoint you will receive not only the number of shares for the URL but also getting the number of comments and reactions on the shared information. Here comes the main difference in the share value, which in endpoint method 2 will show a bigger value (because of received additional data).
To change the share counter update method, you need to visit in plugin settings Social Sharing -> Share Counters Setup -> Single Button Counter menu. But do not forget that if you decide to switch to API endpoint #2, you should generate and include an application based token (without that token the data will not appear). At this time you does not need to verify the application created for the website and it can run properly even in development mode.