> E-mail marketers will no longer be able to get any information from images—they will see a single request from Google, which will then be used to send the image out to all Gmail users. Unless you click on a link, marketers will have no idea the e-mail has been seen. Absurdly wrong, marketers already use a unique image URL for each email recipient, and Google has no way to know that all of those point to the same im…
> Absurdly wrong, marketers already use a unique image URL for each email recipient, and Google has no way to know that all of those point to the same image. wrong. you can of course do simple image processing and identify similar images. if the marketers only change the name(url) of the file and not the content one-bit, you can trivially compare the hash of the file... even if the marketers change content, assuming…
Gmail blows up e-mail marketing by caching all images on Google servers
311–320 of 322 posts
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#312Earlier quoted context omitted.
Unless they've somehow overlooked something, surely their terms of service will?
The terms of service are an agreement with their users, not with third parties who are emailing their users.
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#313Earlier quoted context omitted.
Mmm, it sounds like Google might deduplicate the images....
I thought that at first too, but to deduplicate, they still need to first issue a request for each, download, and compare. So the requests have already been made, and the marketer received their information.
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#314Earlier quoted context omitted.
With google's machine learning brain trust, I think they could still do a pretty good job deduping. Maybe not perfect, but I'd bet on them to win an arms race. Edit: ah, codeflo and EGreg are right. I was just thinking about the task of determining that the images serve the same role in each message (which I'm sure google could do a good job of). But (as they point out) in the "Dear " case they'll still have to show…
> But (as they point out) in the "Dear " case they'll still have to show the right image to the right user. They could do a "This sender appears to be attempting to track you. We have disabled images as a precaution. Click here to load." Scary enough to the average user it'd probably kill the the technique very quickly.
A particular example of crying wolf that comes to mind is the yellow box that says, "HEY! THIS SENDER ISN'T WHO THEY SAY THEY ARE!", which usually means that someone just forwards their .edu address to Gmail.
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#315> E-mail marketers will no longer be able to get any information from images—they will see a single request from Google, which will then be used to send the image out to all Gmail users. Unless you click on a link, marketers will have no idea the e-mail has been seen. Absurdly wrong, marketers already use a unique image URL for each email recipient, and Google has no way to know that all of those point to the same im…
Google gets huge benefits from it but I think in the end this helps advertisers as well as still being able to track via the image url and a unique url/id. Good deals usually help both parties with some give and take. Pros: - Since all images flow through google, phishing and other malware attacks could be subverted. - Images will be hosted faster in many cases (possibly less cost to run newsletters). - Less connecti…
Also, google already has this data so why is that a con?
There is no national security reason.
Bottom line: Christmas came early for spammers this year.
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#316Earlier quoted context omitted.
I don't understand how that helps. If I send an email to user_x@gmail.com with an embedded image at http://example.com/my_spam_images/image_for_user_x.jpg and google makes a request to that, I know the mail has been delivered and the user in question exists and is seeing my ads, because a request for image_for_user_x.jpg showed up in my logs. Now, when user_y also receives my spam and I get a request for image_for_us…
"I know the mail has been delivered and the user in question exists and is seeing my ads" No, you just know that the email was delivered to the user's inbox. You don't know if the user looked at it or just trashed it.
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#317Earlier quoted context omitted.
Google's an advertising company. Selling eyeballs -- or information on how to get more eyeballs -- is what they do.
> Selling eyeballs -- or information on how to get more eyeballs -- is what they do. Selling eyeballs: yes. Selling information: oh good lord no, so very, very no. That information is never ever leaving Google's servers.
Imo it's enough to be a bad thing. We can't rely on good will of companies to fight incentives and money in the name of privacy of their users.
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#318Earlier quoted context omitted.
> Selling eyeballs -- or information on how to get more eyeballs -- is what they do. Selling eyeballs: yes. Selling information: oh good lord no, so very, very no. That information is never ever leaving Google's servers.
If it leaves or doesn't leave Google servers we can't really know but the facts are: -Google has this information -They are marketing company with incentives to monetize it Imo it's enough to be a bad thing. We can't rely on good will of companies to fight incentives and money in the name of privacy of their users.
Even the evilest of companies isn't going to sell off its competitive edge, that's just idiotic.
Also you are wrong, Google is not a marketing company. Google is a middle man company. Google matches marketers to consumers. THAT is Google's business. Google is paid to be a match maker, nothing more.
Re: Gmail blows up e-mail marketing by caching all images on Google servers
#319Re: Gmail blows up e-mail marketing by caching all images on Google servers
#320Earlier quoted context omitted.
AND it could create a dis-incentive to load up an email with unique images since as soon as you send the email out all of those gmail addresses are coming right back at your server to request the images.
We manage opt-in mailing lists for customers of restaurant chains, and for well timed, well-targeted campaigns they get open rates in the 30%-40% range with the majority of opens within 15-30 minutes of the send anyway. It takes more resources for us to handle the outbound mail load than to handle the inbound image requests, as for the image requests the url's contains enough info to do a trivial regexp based rewrite…