What is this Google URL - html

I've recently written a script that monitors all web traffic on my site, pages visited and http referees etc. the only thing is this URL pops up quite a lot:
http://www.google.com/aclk?sa=L&ai=CpEvvFIUuU-HsL-KLsQeToYAQ0p6OgwTSx7TDZZCY14MBCAAQAVDi_eSK-v____8BYMmG_4fwo-wSyAEBqgQfT9AXzXKHZOapkrGJKMmlEyCHmzHyLx_B7YlQXndIb7oFEwjb7J2xiai9AhVkTjIKHdpMAFPKBQCAB6LT4CuQBwM&ei=FIUuU9uSLOScyQHamYGYBQ&sig=AOD64_22JDmj354Hn
But when I goto it it is just blank. Any idea what it might be?

As per this post : http://clicky.com/forums/?id=6591
It seems to be something google uses to track clicks on ads, with aclk bieng short of ad click.
And it returns a blank page as the link throws a bad request error, when accessed directly. Which essentially means no page has been loaded. (check console).

This is a result of obfuscation techniques called "Secure Search" implemented by Google a couple of years ago to prevent traffic analysis tools from gathering Keyword/User data due to privacy concerns.
It is caused by the user being logged in with their Google account when they click through to your website, therefore the URL is unique to each user session and this is why it returns a blank page.
In Google Analytics this results in (not provided) keyword data accounting for around 80% to 90% of all referrals.
More info here:
http://searchenginewatch.com/article/2296351/Goodbye-Keyword-Data-Google-Moves-Entirely-to-Secure-Search

Related

Google apps script cannot get url parameter from page on new Google site

My current site (Golf League) uses several scripts to allow players to schedule whether they are playing, display various results pages etc. It seems as though the New Google Sites implementation does not allow a parameter to be passed in the page url and get picked up by an embedded Google Web App (published from my script)
This link shows an example https://sites.google.com/site/kitchenergaffers/home/general-gaffers-information/publish/directory-of-results?display=directory
There is my webapp (built from a GAS) that does a doGet(e). The "display" parameter tells this script which page to format and display which it gets by extracting the e.queryString. I use a similar approach for players scheduling their absences. Another url parameter identifies the player who may be changing their availability.
It seems as though this ability is not going to be supported in the New Google Sites, so I am looking for an alternative (and free) web building facility where I can launch GAS web apps and access the page url parameters the same (or similar) way. Wordpress, Wix etc may be candidates, but it is difficult to tell from their introductory info whether it can be done. If someone has already found a site facility and methodology I would appreciate the guidance.
Just in case anyone finds this in a search, I have found a workaround.
What I had missed is that a script can be the target of a URL and will execute in a browser on its own. It does not need a "hosting" page. So to achieve what I need to do, instead of sending the link with the Google sites page, I can send a link with the script directly and it will happily execute in its own browser environment. In some cases, I may need to add a bit of text to the html returned by the script to replace that which was on the Sites page
So this link (below) achieves what I needed. Be aware that the links displayed by the script, are currently still to the original sites page.
https://script.google.com/macros/s/AKfycbxichdoGrHbImuudkJbuhhD00GpHvVvc-Ph_BTpSI4863pMevVx/exec?display=directory

HTTP 403 on images loaded from googleusercontent.com

First off, I don't think my problem is related to these questions: question 1, or question 2.
Because I'm not using authentication anywhere, or any library either (I don't need to).
I'm simply loading some publicly-available album art images in my web application:
// urlList is an array than contains URLs like the examples given below
<img *ngFor="let url of urlList" src="url">
Example URLs:
Glass Mansion, Summertime, Side Effects
99% of the time, it works. But sometimes I get 403 errors on the console for those exact same URLs.
I know they're not related to authentication, because, well. These URLs are publicly accessible.
Debugging this has been difficult, because a few page refreshes later, it magically works again. There's nothing out of the ordinary in logs either (except the GET 403 errors).
What in the world is happening?
I'm using Angular v7.2.15. Browser: Google Chrome
Add referrerpolicy="no-referrer" attribute
<img src="your-google-link-here" referrerpolicy="no-referrer"/>
Within several Google API's (like the gmail API for example), Google uses HTTP403 and/or HTTP429 in order to ratelimit certain requests over certain time periods. I do not know what method you are using, if you are using some sort of API etc, nor do I know how busy or large your webapp is. But rate limiting or fair use compliance could be coming into play.
Gmail API Rate Limit Info Source - https://developers.google.com/gmail/api/v1/reference/quota

Google Maps API Blocked for certain server

Google Maps API static maps is blocking my website's maps.. The site is on a load balancer, so the map is only blocked on one of the servers and seems to be only blocked when viewing the map that was sent in an Email. The users see a red X with a thottle image representing overused.
If I view the map in a browser using the Javascript V3 version of the same map on the same device, it is fine. Or if I end up on another server (load balancer), then it is fine. It is just a specific server viewing an email with the map in the email.
http://maps.google.com/maps/api/staticmap? (example - doesn't work outside of the code)
My question is to try and understand what is happening. When viewing an email with the Static map, it is the end user (receiver of the email) that is downloading the Map. There is no way any of them reached a 2,500 view limit in a day. All the emails come from one server, but when viewing I do not think this is a factor since it is only when I am on a specific web server that I get the problem.
Can anyone explain what is happening?
BTW, I have contacted Google Business Premier group and have not received a response yet. I need a work-around while I figure out what and if they want to charge me.
I'd make sure that you're not embedding the image itself in the email, but instead are including an tag that loads the map directly from Google. If your email blasting program is downloading the image and embedding it in the email you could easily go over that limit based on how many images and emails you send.
It would be worth looking at the HTML source of the email and making sure that you're loading the map directly from Google. If you are, any over quota problems you've run into might be limited to your current IP address. Checking the email from a different IP (simulating one of your end users) should be a much better test.

Inject ads to Google Chrome Extension

I am developing a google chrome extension, and planning to inject ads using the allowed feature. I have checked in front of "Ads Behavior" that says "This extension injects ads into some third-party websites."
My question is, how and where do I mention the source of ad? Say, if I want do display google adsense, how do I set it up??
I searched it throughout the day today, but didn't get any information anywhere.
Thanks,
James
Injecting ads is not that simple.
The first problem you will face is to find an ad network that allows extensions to inject advertisements in pages. AdSense doesn't allow this behavior.
The second (and maybe more complicated) problem is to inject the ads. In a chrome extension you can use script injection to add the advertisements to the pages. The real problem is where to put the advertisements. They should be placed in a smart manner; ensure they don't conflict with the page layout/functionality; they shouldn't be everywhere and on every page, otherwise your users will promptly uninstall the extension; you absolutely shouldn't just replace existing ads if you don't want your extension to be flagged as malware.
I haven't yet added ads to my extension because of these and others problems, and I am striving to get some money from it since it has cost me a considerable amount of time to create it, and I have received very, very few donations considering the over 150.000 users.
Hope I could help.

Chrome is accessing links in webpages that were not clicked

I spent the day debugging my website, because I seem to be getting randomly logged out, but just on Chrome on Android.
After reviewing the server logs, I see requests from my Android tablets IP hitting my server for links that I never clicked on. After some experimentation I see every couple of links I click, Chrome will fetch another link at random in the page that was not clicked.
The issue is that there is an a link in the page with an href="logout" which will sign in, and Chrome calls this all on its own, disconnecting the session. I suppose if I changed the link to call a POST operation Google would not fetch it, but I can't see why Google would be fetching links that were not clicked.
This is very odd, and does not occur on Firefox, or Chrome on Windows.
Not sure if this is some sort of virus on the tablet, or some thing Google is doing to check the content of pages that it would not have access to without the session.
I have seen Google do this before, but only when there were Google ads in the page, then Google would fetch the links twice so that it could get the page content to choose the ad. This seems a huge privacy issue, as Chrome is fetching private data from the session.
So the issue is that Chrome is using a new feature "prefetching".
This is a "feature" that will have Chrome randomly fetch any linked URL from the page.
This seems like a very error prone "feature" for Chrome to enable by default. Seems like it could give the user cached or stale data, or change the server's state causing obscure difficult to debug issues. This will also use double the amount of the user's data (and server's CPU), which you would think would not be desirable to most users that pay for their data.
I confirmed this by disabling the feature in Chrome.
My solution was to switch the logout call to use a POST through a element.
See, https://www.technipages.com/google-chrome-prefetch