Recently, I purchased a ticket to a concert on Eventbrite. Here is the order confirmation page:
I was not pleased to find the following message on the order confirmation page:
By purchasing a ticket, you will also receive weekly email blasts from Ruby Skye about upcoming events, guest lists and more.
The reason why this message irked me is because it was never shown at any point prior in the purchase flow. The user was never properly warned that a purchase would result in this added consequence of having their email added to a mailing list. Sure, at the end of the day, it’s not a huge deal and I can eventually get out of it with a simple unsubscribe. But that’s a waste of the user’s time — not to mention that this technique of acquiring emails is dishonest and not customer centric.
Seems like everywhere you look these days, users are given an opportunity to share something via Facebook, Twitter, Google+, LinkedIn, Digg, StumbleUpon, and the list goes on an on. While it may be a bit overboard to offer sharing via so many different channels, offering sharing across Facebook and Twitter can be quite beneficial to a product.
One area where sharing would be a logical fit would be across content sites such as espn.com. On their mobile site, they have a video module that typically had 3 videos that can be selected to be viewed.
After clicking through, you are usually shown an ad and then the video.
When the video concludes, you are taken to a video center page that shows you what video you just watched and asks you if you want to watch any more videos.
At this point, this would be a GREAT opportunity for ESPN to offer the user the ability to share the video via Facebook or Twitter. This is no different than ESPN asking users to share articles via social channels. Except such a medium (video) may even have a more effective conversion rate of bringing new users back to the site.
Here’s a prompt from Adobe that asks me to update the Flash Player on my MacBook Pro:
In general, I’m used to an application informing me that a new version is available and I should download the update just because. What I like about this prompt is that I am reminded as to what exactly this software is used for and how it can benefit me. I’m sure such a technique has a significant positive impact on update conversion.
Recently, I noticed an interesting text message alert from Facebook. The primary purpose of the text was to inform me that I had a pending friend request. In addition, the text issued a warning that since I hadn’t responded via text to Facebook recently, then I will stop getting text alerts.
Fair enough. It’s a reasonable explanation to turn off text alerts if the user is not interacting with the feature. But what was interesting for me was just how long would Facebook be willing to keep sending such text warnings before pulling the plug.
A couple of weeks came and went with no text alerts from Facebook. Amazingly, 25 days after the text above, I received another text from Facebook! This time, the warning was that since it had been 111 days since receiving my last text, Facebook may stop sending me text alerts.
So to make a long story short, Facebook is willing to wait at least 111 days before ceasing text messages. I find this to be an extremely long time. Especially since Facebook already gave me a warning at the 86 day point. Ideally, the algorithm that determines how long to continue sending texts to the user should not only be based on how many days it has been since last interaction, but also how many warnings the user decided to ignore.