guys, I've been struggling with a person who has attacked my Google AdWords account and he started to clicks on my websites with some proxies from all around the world, I have excluded all the countries except Iran and the point is I still getting IP addresses from every part of the world I have no idea how it possible but google count those clicks as a valid clicks and there is no invalid activity on my account.
I was wondering if anybody could show me a way at least I could stop this process.
Related
I have an app that works with multiple Oauth2 sources, google being one of them. I want to be able to get the principalID or basically OAuth2AuthenticationToken.getName to be the email address rather than the long number that google provides. This is because I want to map this ID to some app specific user information and having to find out the long num for every user is a bit of a pain. Alternatively is there an easy way to get the identifier for every user?
I have created a Google Site which links to various Google Classrooms. I would like to know who is using the site.
Is there a way of recording the Google ID in a Google Sheet, for when someone accesses the site?
Any help or even a point in the right direction would be great.
Thanks
Ok, since you are using Google Sites, you can create a user start page by following these steps, this page will ask the users to authenticate with their emails, and will allow only users from the organizational unit for which the site is allowed.
After that step, you can use Google Analytics with your Site to track the behavior of users in your Site.
I suggest starting with a quickstart of Google Analytics to get the hang of it.
And soon enough you will have it set up to suit your needs.
Our app requires Google OAuth2. When a user, with an existing Google account, authenticates with Google then we use a callback to return users to our App. This is what we want.
The issue is, for those users who do not have a Google account we ask them to create a Google account (gmail address) or connect their existing email address to Google. A user who has to follow either of these flows ends up on the "Thanks for creating a Google account page" and not back at our App.
This is supposed to work as you are expecting. There is a continue button on that page and that should bring the user back.
If that is not working, can you tell us more (about OS, client id, urls and the exact steps) or give us a link to test/reproduce? Is this on the web or on mobile app?
My Geo based Android app uses Fusion Tables accessed via oAuth to store route information for users.
For the last couple of years I sporadically get notifications from users in Asia Pacific telling them that their authentication has failed. This means that the key that is registered on the API dashboard for com.spiralsoftware.bestroutepro is not being recognized.
This does not happen for all users in that region and has not happened anywhere else in the world. I suspect that there must be a bad server somewhere that my users connect to sometimes.
Once the authentication has failed it doesn't seem to come back: they appear to be locked out of being able to load their saved routes forever.
Normally the users experiencing the problem are in Australia or New Zealand but this evening I received an email from a user in the Philippines.
I can't create another API key without deleting the existing one which means all other users will be unable to access their Fusion Tables until they upgrade the app.
The folks who are affected have paid money for the app and I don't know what to tell them.
Is there anything I can do to get these users authenticated?
I've been working with the Google Analytics API to create a page showing some specific statistics. Right now everything is working, except that after the user goes through OAuth, it is displaying statistics from their Google Account.
Instead, I always want it to display statistics from a single Google Account that I own/operate, and everyone else is just viewing the data from that account.
I haven't seen a way in the GA documentation to accomplish this. I would assume the user wouldn't have to log in, because I'm just showing them my account, but it's not the end of the world if they have to.
If you're looking to create a place where users do not have to go through OAuth, you should really look at using Google's superProxy to publicly display data.