• Resolved Hans Schuijff

    (@hanswitteprins)


    I’ve noticed that the results of the shared count are not consistent and noticed some for me strange results.

    I find if f.i. strange to have a http count on a new blog post that is fairly new and has never existed in a http version. And I expect the same result when I repeatedly refresh the shared counts in the editor.

    Instead each time I use the counts refresh button in the editor it changes the count in an way I can’t explain yet. ofcourse there can be some activity between refreshes, but a social share count is not likely to go down in the short time it takes to refresh again. Especially for a post that has not that much activity in the first place.

    I investigated if it is the plugin that is causing this, or the sharedcounts.com api and found that it is probably the sharedcounts.com api. So I wonder how reliable the sharedcounts.com information is.

    Testing the api call in postman, it at first seemed alright there (each refresh gave me the same result), what made me think the plugin was corrupting the data in some way, but after restarting postman the numbers where different than the previous time, so now I’m thinking that postman gets the repeated results from some sort of cache instead. So now I restart postman between each get.

    I tested with this url:

    https://api.sharedcount.com/v1.0/?apikey={key}&url=https://dewitteprins.nl/moet-ik-mijn-kind-laten-vaccineren/

    Some of the results (only the Facebook part):

    "Facebook": {
            "comment_plugin_count": 0,
            "total_count": 2,
            "og_object": null,
            "comment_count": 0,
            "share_count": 1,
            "reaction_count": 1
        },
    "Facebook": {
            "comment_plugin_count": 0,
            "total_count": 32,
            "og_object": null,
            "comment_count": 0,
            "share_count": 22,
            "reaction_count": 10
        },
    "Facebook": {
            "comment_plugin_count": 0,
            "total_count": 8,
            "og_object": null,
            "comment_count": 0,
            "share_count": 7,
            "reaction_count": 1
        },

    Perhaps not that critical since it is just a way to show some social proof, but I was expecting to have the numbers make some sense anyway and at least show a consistent result.

    Is this a know phenomenon? Anyone tested this and found up and downward varying outcomes on the same url like this?

    Thanks, Hans

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Bill Erickson

    (@billerickson)

    I recommend you forward this question to Shared Count. Despite the similar name, Jared and I (who built the Shared Counts plugin) aren’t associated with the Shared Count service. We built the plugin to leverage their API.

    Thread Starter Hans Schuijff

    (@hanswitteprins)

    I understand, Bill, but since you choose to use this service I thought those results would also be of interest for the plugin and other users. I imagine you choose this api because you expect it to give accurate social share info.

    I have passed the question through to sharedcounts.com too and am hoping to get some response there. Since I think it’s an api problem I will close this issue here.

    thanks,
    Hans

    Thread Starter Hans Schuijff

    (@hanswitteprins)

    sharedcounts.com replied, and points to Facebook for the problem:

    Facebook had rolled out an update on how the counts are shared which causes the differences on the counts for every API call. From our observation, this affects URLs with relatively low counts.

    This update was actually rolled out on June 2021. We are working on this and hopefully we can get more accurate calls as soon as possible.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Varying results (up and down) in repeated shared counts Refresh’ is closed to new replies.