Topic-icon Points system not working on google+ share

Active Subscriptions:

None
5 years 9 months ago #64299 by eashery
Hi,

On blabber.buzz, when we open a single k2 item, it has social share links(check screenshot attached). We have altauserpoints system which assign some points to users on the basis of social buttons selected. I can see those rules also in Jom-social.

Problem is Google+ has two rules "Google +1 Create" and "Google +1 Remove" but none of them work with G+Share button. Let me know which particular rule is associated with G+ Share button and if I need to create a new, where do I need to add a hook.

File Attachment:
The topic has been locked.
Support Specialist
5 years 9 months ago #64318 by alzander
Unfortunately, the Google +1 or Share tracking feature seems to have been removed by Google. Their documentation still shows that the ability is there to use a 'callback' when a user shares content. That callback calls some JFBConnect Javascript which then is used to reward points.

However, just because their documentation shows it as possible, doesn't mean it actually works :( There are multiple posts in the Google Developers area of this functionality not working. It hasn't in some time (since around the end of 2017). We have left the functionality in because a) it used to work and b) we're hoping Google fixes it. They haven't made any announcements that the ability to track when a user shares (or +1's) something has been removed, so we've been going on the hope that it will come back.

Google isn't putting a lot of development effort into Google sharing features, which is a shame, because it means things can break for some time before it's either fixed or removed entirely.. and we're never sure which way it's going to go.

For reference, here's some other developers discussing the callback functionality not working:
plus.google.com/100777000102386183098/posts/KriFEJHRNnh
plus.google.com/110831685157127838096/posts/WC8NXMtpcaL

Sorry I don't have a more definitive answer for you, but I hope the above explains what's going on.

Thanks,
Alex
The topic has been locked.