21–30 of 32 posts
Earlier quoted context omitted.
I have no idea (didn't find out from a quick browse through the site), but the first thing that came to mind was an image in the mail, pointing to a server that slowly trickles a response without ever finishing so it can measure how long the other end is listening.
Pretty genius idea but easy to replicate by the big boys..
Earlier quoted context omitted.
Bullshit. There's not a single major client that executes code from emails. You might be able to have some link back to your server, but even those are blocked by default.
They aren't blocked by default in all clients. Check your mom's iPhone, it loads images by default.
Earlier quoted context omitted.
Pretty genius idea but easy to replicate by the big boys..
Big boys move slowly. Plus, what isn't "easy to replicate?" aside from network effects.
The major issue with this is going to be scaling it, with large ESP's doing 50-100 million messages a day, and 20-30% of those being opened, that's a lot of processes. This solution will probably be effective, mostly because it's going to a much smaller segment.
How do they determine engagement time or whether the email was deleted?
1. In the HTML email put 2. Serve up http://myserver/invisible.gif with a process that trickles down an endless GIF image a few bytes at a time. 3. When the connection to the endless GIF dies, call that the "reading" time. 4. If a "reading" time is under some threshold call it "deleted". That's how I did it a few years ago anyway.
Earlier quoted context omitted.
I have no idea (didn't find out from a quick browse through the site), but the first thing that came to mind was an image in the mail, pointing to a server that slowly trickles a response without ever finishing so it can measure how long the other end is listening.
I guess that could work if mail clients don't have timeouts for images. I still can't imagine how they would detect deletion though.
Earlier quoted context omitted.
We have a special tracking code that figures it out over the email clients' use of HTTP and with some fancy server-side node/mongodb stuff.
Maybe a throttled node.js response on an img on a large image file? edit: Oops I see that staunch beat me to it.
Earlier quoted context omitted.
1. In the HTML email put 2. Serve up http://myserver/invisible.gif with a process that trickles down an endless GIF image a few bytes at a time. 3. When the connection to the endless GIF dies, call that the "reading" time. 4. If a "reading" time is under some threshold call it "deleted". That's how I did it a few years ago anyway.
i never load images automatically in my emails, and I bet a lot of other people do that too
How do they determine engagement time or whether the email was deleted?
1. In the HTML email put 2. Serve up http://myserver/invisible.gif with a process that trickles down an endless GIF image a few bytes at a time. 3. When the connection to the endless GIF dies, call that the "reading" time. 4. If a "reading" time is under some threshold call it "deleted". That's how I did it a few years ago anyway.
https://github.com/derwiki/redirect_tracker
Like most email metrics, it's lacking -- but this is still -a little- more information, and that goes a long way in email marketing.
This is why I block graphics, run mail in a separate browser instance etc. GTFO of my business.