Blog


URL shorteners are dead. Long live URL shorteners!

By Jonathan in awe.sm 

Last week, 364 days after first announcing their t.co link wrapping service, Twitter started rolling out automatic URL shortening on Twitter.com. URL shorteners existed long before Twitter and will continue to exist, but this move by Twitter means the need to shrink links will no longer be mainstream in the way it has become over the last few years.

While this may be the end of consumer-facing URL shorteners as we know them, it’s a key part of Twitter’s efforts to become more approachable to mainstream users and build a bigger, more engaged audience. Achieving those goals will make Twitter even more valuable to publishers and marketers, for whom it will be that much more important to understand how Twitter drives traffic and ultimately revenues. URL shortening has always been the wrong way to think about tracking the value created by sharing. Social media marketing can and should be driven by real performance, not proxies like followers and clicks. And this move by Twitter helps move the conversation in that direction.

Why t.co is essential to Twitter, and what it means for everyone else

There are 3 reasons that wrapping every link on Twitter in t.co is an essential part of their strategy to become a media company:

  1. Twitter needs more mainstream users engaging, not just consuming, and making them have to use a 3rd-party URL shortener to share links is unnecessary friction around the most valuable behavior in the Twitter user experience.
  2. The only way for Twitter to protect users from malicious and offensive links is to get between the click and the destination page. If lots of people are getting hacked, phished, or otherwise scammed from clicking on links in Twitter, they’ll stop clicking.
  3. The reason Twitter doesn’t talk about is that they need the data. Facebook and Google collect information on every click out from their sites, but before t.co Twitter knew nothing about where they were sending their users. Knowing not just what content is being shared but also knowing what content is being clicked is essential to Twitter’s ability to serve their marketer customers in the long-term.

So, the future for links on Twitter is clear. All links shared on Twitter will be wrapped in a 19 character t.co URL, which means there’s no more need to shorten links before sharing them. And thanks to tweet entities, the unwrapped URL will be displayed in the Tweet (see image), so people will know what they’re clicking on.

Beyond shortening: how to get actionable data from social media

With link length and branding no longer a factor, the only reason to use any kind of redirect links (which is what ‘short links’ are) on Twitter is data. And frankly, URL shorteners are fundamentally limited in how useful the data they track can be. That’s why, despite being best known for starting the vanity URL shortener craze (we’re sorry ;-) ), awe.sm has never been about making links smaller. Our goal from the start has been to help our customers understand not just what happens in social media but why it happens and how they can create more value from that knowledge.

awe.sm is designed to be more analogous to an ad-server or the way that email marketing software tracks opens and click-throughs, it’s just built for social media (hence the Twitter-friendly tracking links). The core of what sets us apart from a conventional URL shortener is that, in order to make their links as short as possible, they collapse down to always give you the same short link for a given long link (or “canonical URL” in geek speak). This means that if, for example, you wanted to see how tweeting the same thing at different times of day works, you won’t be able to know for sure what traffic was driven by which tweet because all your tweets will have the same link. Whereas, just like an ad-server tracks every impression individually and email marketing software tracks every recipient individually, awe.sm tracks every share individually. This enables our customers to find patterns of success in their sharing activity based on factors like when something is shared, how it is shared, and who shares it, not just the single dimension of what is being shared (i.e. the canonical URL).

Every data-driven marketer knows that proper attribution is the key to understanding and optimizing performance. Our approach of tracking each share action individually and tagging those actions with information about the context of the share provides the ability to understand the truly unique dynamics of social media. But any attribution is only as good as the results to which you tie it. That’s why awe.sm integrates with web analytics solutions like Google Analytics and Omniture to add a social attribution layer to your existing visit, pageview, and goal tracking and it’s why we have also recently added our own conversion tracking abilities to build the entire social funnel from clicks to pageviews to goals and even revenues.

Social data == Big Data

At this point you might be saying to yourself, “Ok, I get it. awe.sm isn’t a URL shortener, it’s a social analytics product.” But for us, analytics is just the tip of the iceberg. We fundamentally believe that the real value of social data doesn’t lie in generating reports for a human to analyze and then figure out what should be done. When you’re tracking every share action, the data are too dynamic and voluminous to make sense of in a spreadsheet — there’s no person sitting behind the AdWords algorithm looking at what gets clicked on and making the decision to serve more of those ads, and harnessing social data should be no different. Our goal with awe.sm is to provide social data as a platform on which others can build, whether that’s determining the authority of Plancast users based on how many attendances they drive, helping companies like BigDoor and OneTrueFan offer turn-key game dynamics around sharing, or enabling ecommerce platforms like Topspin and Storenvy to empower their merchants to identify and engage with their most valuable customers.

Our belief that there are more interesting uses for social data than we could possibly build ourselves is the reason that everything we do is built on top of our own powerful APIs. This approach allows us to power components of other applications, integrate with 3rd-party tools, and support effectively limitless customization to deliver sharing data in the most valuable ways to our customers’ businesses.

The ROI of social media is real and it can be measured

"To put it bluntly, if you’re focusing on fans and followers, then you’re almost certainly doing it wrong."
Nate Elliot, Forrester

The bottom line is you shouldn’t listen to anyone who tells you that you can’t track social media the way you track your other outbound marketing channels like paid search, graphical media, and email marketing. Yes, social is different. It’s a word-of-mouth superconductor driven by human dynamics that are as powerful as they are complex. But in the end, the same core methodologies of connecting the results that matter to your business with the actions that drove them can and should be applied.

If you’re interested in learning more about how awe.sm can help your business create more value from social, please drop us a line to questions@awe.sm or just click here to chat with someone from our team right here.





awe.sm @ #sxsw

By Jonathan in General 

new tee shirts
Along with apparently everyone else in startupland, awe.sm’s two Jonathans (middle and second-from right above) will be descending on Austin this weekend to mingle with the social media elite at SXSW Interactive.

If you’re there and want to learn more about what awe.sm does, how cool it would be to work with us, or to chat about ways to measure the performance of social media marketing in general (or if you just want a shirt or some stickers ;-) ), we’re @jhstrauss and @cowperthwait on Twitter and you can stalk us on Plancast here and here, respectively. Or you can always just email us at questions [at] awe.sm, which we will be checking throughout the conference.

See you in Austin!





Welcome Bennett!

By jeremiahlee in General 

Bennett Hiles grew up in Los Angeles only blocks from awe.sm co-founder Jonathan Strauss, but their paths didn’t cross until Bennett responded to a job post on TechCrunch in 2010 that went a little something like this:

Wanted, the Most Interesting Programmer in the World:

  • Someone who doesn’t need to use pointers; his* code just knows where to look.
  • Someone who doesn’t call APIs, they call him*.
  • Someone who once wrote a slow query, just to see how it felt.

*awe.sm is an equal opportunity employer, but gender-neutral pronouns make things less funny.

awe.sm Bennett is awe.sm

After getting a taste of web analytics at a previous job, Bennett felt ready to conquer the big data challenges at awe.sm. And he impressed us by being only the second candidate to pass Laurie‘s infamous whiteboard interview. Since joining in August (hey, we’ve been busy!), Bennett has been responsible for ensuring the massive amounts of data we collect get turned into speedy and reliable results for our customers. He’s done a phenomenal job so far, and his love of Mexican food ensures we do team lunch at Taqueria Cancun at least once a week (taco Wednesdays, duh!).

Outside of work, Bennett is a man of many interests. He enjoys roller and ice hockey. Though he speaks better Java than Spanish, he’s spent every Christmas waterskiing and wakeboarding in Mexico with his family. He rescues cats. He knows how to set the mood with his playlists on Rdio. And he loves a great whiskey.

Gentlemen, and especially ladies, please welcome Bennett Hiles to team awe.sm.

P.S. If you think you’re qualified to be the 2nd Most Interesting Programmer in the World ;-) , we’re still hiring!

[Photo: @photo]





Introducing VIPLi.st

By Jonathan in awe.sm 

If you’ve ever wanted to see exactly how information spreads through social channels like Twitter and Facebook, now you can with VIPLi.st, a fun visualization of the data awe.sm tracks for Plancast.

Plancast is a great service that enables users to share and discover events with their friends. One of the main ways that social discovery happens is through Plancast’s deep integrations with Twitter, Facebook, and Google Buzz. All of this activity happening off their site is a big driver of traffic and engagement to Plancast, so they integrated with awe.sm to track how these external shares drive results.

The core integration is completely white-labeled using the awe.sm API and Plancast-branded tracking links, giving Plancast full control of the design and functionality of their sharing features. In addition to the dashboard we provide, awe.sm data also is pushed into Plancast’s Google Analytics account so they can see everything in one place.

We originally built VIPLi.st for the Strata Startup Showcase*. It uses the data we track for Plancast and combines it with their attendee data to build a map of how word of an event spreads through the social web. Enter the URL of any Plancast event to see how many sign-ups each attendee drove and through what channels, like this VIPLi.st for SXSW Interactive.

VIPLi.st is just one example of the many powerful use-cases that can be tracked with awe.sm and it was built in under a week using our APIs. For more thoughts on the potential applications of awe.sm, check out my interview with Pete Warden on ReadWriteWeb. If you’re interested in learning more about awe.sm, drop us a line at questions [at] awe.sm.

And if the challenge of turning the chaos of high volumes of sharing data into compelling products like this appeals to you, we’re hiring!

Finally, here’s a video of me telling Robert Scoble basically what you’ve just read ;-) :

* Credit to our friend @gregarious for the initial idea for VIPLi.st.





Tweet Button with Shortening for WordPress

By Jonathan in awe.sm, Marketing & Promotion, Publishing 

On Thursday, Twitter released their ‘official’ tweet button. By default, it uses Twitter’s t.co URL shortening, which means it will display an excerpt of the full link in the tweet. But some folks, like our awe.sm customers (yes, I mean that both ways :-) ), want to easily use the new official tweet button with 3rd-party tracking tools.

So, we’ve whipped up a WordPress plugin that supports awe.sm, bit.ly, tinyurl, su.pr, and digg URLs as well as some other nifty features.

Get the plugin here

Here’s the full feature list:

  • Configure the placement of the button on your posts: top; bottom; top & bottom; or manual
  • Choose the type of Twitter tweet button you want: vertical count; horizontal count; or no count
  • Optionally use awe.sm, bit.ly, tinyurl, su.pr, or digg to shorten the links shared through the tweet button (default is Twitter’s t.co)
  • Specify the via Twitter username to be included at the end of the tweet and in the recommended users to follow screen after the tweet
  • Optionally add the author of a given post to the recommended users to follow screen after the tweet (requires the author to enter their Twitter username in their WP profile)
  • Disable the button on Pages

Use 3rd-party URL shorteners, like awe.sm, and specify the via username.

Add the author of a given post to the recommended users to follow after the tweet.

Try it here:

This plugin is primarily based on the excellent BackType Tweetcount plugin and I adapted part of the post author code from the also excellent Twitter Publisher plugin.

If you have any issues or feature requests, please let us know at support+tbws [at] awe.sm.





Welcome Jeremiah!

By seldo in General 

It took Jonathan until we hired Jeremiah to write my welcome post, so it seems only fitting that I waited until we hired somebody else to finally write this post officially announcing Jeremiah to team awe.sm.

How Jeremiah and I know each other is a pretty odd story. Back in 2002, he appeared in one of Apple’s ‘switcher’ commercials. I emailed him at the time, then we kept very intermittently in touch until 2007, when I moved to California. We found we have a lot in common, and started talking (mostly via his Twitter stream) about webdev, politics, and more. We finally met in person in 2009 when I visited L.A., where he lived until last month.

Since 2002 JC has been busy writing, coding, founding his own app company — oh, and surviving a helicopter crash into San Francisco Bay (really! You can read about it on his Wikipedia page). I was always very impressed with his combination of design talent and coding skill, as well as his entrepreneurial drive, and Jonathan felt similarly when they met at BarCamp LA last year. So when the time came to hire a front-end developer for awe.sm, he was one of the first people we thought of.

Now he’s been on the team more than 3 months already (yikes! Time flies when you’re having fun) and we couldn’t be happier. He’s built our beautiful new front-end (still in beta!), so perfectly that Jonathan once mistook the working site for the photoshop mock-up — what better compliment could a web developer receive?

Jeremiah’s blogged about his own feelings about the job and the move to San Francisco a while back, so all that remains is to say, finally: welcome on board :-)





TweetPo.st Suspending New Signups :-/

By Jonathan in TweetPo.st 

We are disappointed to announce that we have closed TweetPo.st to new users until further notice. This was a hard decision for us, but our top priority is delivering a high quality user experience for our current users and this is the only way we can do that at this point.

If you have already signed up for TweetPo.st, you will continue to be able to use it and we hope most of the issues that have cropped up in the last few weeks will soon be fixed. If you haven’t yet signed up for TweetPo.st, we really appreciate your interest and hope to open back up soon (please follow @tweet_post to be kept up-to-date on our progress).

The brief history of TweetPo.st has been a series of lessons in building products on other people’s platforms. The first version (called TweetFace until Facebook made us change it a couple weeks after release) was basically a public prototype built in a week about a year ago. It grew out of our desire to have ‘a smarter way to update Facebook from Twitter’ for our personal use and we only did it because it seemed so easy at the time. We didn’t even tell anyone about it other than our friends, but somehow people started to notice. We were happy that folks liked it and even happier that we didn’t have to worry about it while we worked on other things.

But then last fall, we began to get reports of strange behavior when new people tried to signup. When we finally had time to do some serious investigation, it turned out that Twitter had changed things in a way that made it impossible for TweetPo.st to add any more new users without us having to basically rewrite most of it, which we didn’t have the time to do then. It was wasn’t until this February that we were able to go back in and basically build a whole new TweetPo.st from the ground up using the latest APIs from Twitter and Facebook.

Based on our research and planning, we blocked out a couple weeks to implement and test the new version. But very soon into it, we realized that things weren’t going to be that easy — specifically, some of the Facebook APIs we had planned to use were broken and all of them were really slow and/or unreliable. In practical terms, this meant we had to do a whole bunch of extra work and testing to make things work correctly for our users. Unfortunately, the very issue with the Facebook APIs is their unpredictability and so at a certain point we had to make a best guess at how to deal with it and then see what happened.

The good news is that after seeing how the application has performed (or not) in the real world over the last couple months, we have a better sense of the pattern of the underlying issues. The bad news is that the long-term fixes for these issues are again going to require significantly more time than we can give right now. So, we have made some smaller fixes that should restore performance for existing users in the coming days and we have decided to close TweetPo.st to new users until we can make the long-term fixes to properly support them.

We can’t tell you how much we appreciate the patience and understanding of our current users. We recently added Tilly to our team to help with customer care across all our products starting with TweetPo.st, and she has been totally impressed with how cool you all have been. And to anyone finding this because they want to use TweetPo.st, we’re even more bummed than you that we can’t let you in yet (and we recommend Selective Tweets as a lightweight alternative in the meantime). We only want to build products people love to use and sometimes that requires us to go for more love from fewer people. We’re hard at work on a new version of awe.sm, which is going to be our main focus for the next few months. And hopefully, we’ll be able to do some more work on TweetPo.st soon after that. Thanks again for your support!





Find us IRL this week

By Jonathan in General 

It’s a busy week of conferencing for us here at Snowball HQ.

The new guy (more on that soon), Jeremiah (@jeremiahlee) and I (@jhstrauss) will be at Chirp all week, starting with the Prechirp party we’re co-sponsoring that’s happening *right now* at 550 3rd Street in SOMA. We’ll be at the conference all day tomorrow and participating in the hack day on Thursday.

Laurie (@seldo) will be at MySQL Conference all this week and will be attending StreamCamp over the weekend (and coding in between ;-) ).

If you’re going to be at any of these events and you want to talk about joining our team, using our products, or building cool tools on our APIs or you just want a sticker, please find one of us and say hi.





Welcome Laurie!!!

By Jonathan in General 

This is a bit belated, but I’m very pleased to officially announce that Laurie Voss (@seldo) has joined the Snowball team as our technical lead.

I first met Laurie when we hired him to join the Yahoo! Widgets team in early 2007. While I’m not sure he always felt the same way, I liked Laurie from the start: he’s extremely intelligent and hard-working, yet he’d be the last person to acknowledge either. And most importantly to me, he loves what he does and takes great pride in it. I know that if I can convince Laurie to get excited about something, it’s a genuinely good idea.

When I decided to start down this road, Laurie was my first choice as technical co-founder. I remember taking him to dinner and telling him the idea and being greatly relieved when he thought I might be on to something :-) . Unfortunately, U.S. immigration law prohibited Laurie, a UK citizen who was at the time on an L-1 visa with Yahoo!, from joining right away. So, after going it alone (with much help from our friends at Cloudspace) for over a year and more hoop-jumping than I care to think about right now, I can’t express how pleased I am to finally be working side-by-side with the partner I wanted.

Laurie brings to the team the technical expertise to turn our early efforts into scalable platforms, the passion for the web to help us deliver truly compelling products, and the patience to deal with me ;-) . We’re both very excited about what we’re building and how we think it will be valuable to others.

You can read Laurie’s much more eloquent account of how we got here and where we’re going on his blog. And if you find the challenges we faced in teaming up as ridiculous as we do, please support the Startup Visa movement (Laurie will be blogging a fuller account of his immigration odyssey just as soon as we ship a couple new things ;-) ). Finally, we’re also looking for a kick-ass Back-End Engineer to join our growing team. So, please spread the word.





TweetPo.st: The Next Generation

By Jonathan in Marketing & Promotion, Our Products, TweetPo.st 

* Update: We’ve suspended new signups on TweetPo.st until further notice. Full details here. *


I’m very happy to announce  we have begun private beta testing the new version of TweetPo.st. I’ll include the full back-story below, but I personally apologize for the lack of communication on TweetPo.st the last few months and for any frustration it may have caused. We’re really excited about the new version because, in addition to being able to take on new users again, we have added support for Facebook Pages, our top requested feature.

TweetPo.st is a smarter way to update Facebook from Twitter. Here are the key features of the new version:

  • Post tweets as Facebook Status Updates
  • Post links you tweet on your Facebook Wall (so your friends can watch videos and see pictures right in their News Feed)
  • Ignore @replies
  • Change @mentions to real names
  • Only post the tweets you specify to Facebook (using either inclusive or exclusive filters)
  • Track links posted to Facebook with awe.sm
  • *NEW* Supports both Facebook Profiles and Pages
  • *NEW* Manage multiple posting configurations from Twitter accounts to Facebook Profiles or Pages

While we’re eager to get as many people using the new version of TweetPo.st as soon as possible, we need to limit the number of users until we work out all the kinks. We don’t anticipate this private beta period lasting more than a couple of weeks, but feel free to email support [at] tweetpo.st if you’d like to help us test before then. Otherwise, please follow @tweet_post to be the first to know when it’s publicly available.

The Back-Story

About 4 months ago, we started seeing bug reports from users who were encountering errors signing up for TweetPo.st. It took some investigation, but we soon figured out that, due to the way we originally built the app (i.e. not using Twitter OAuth, which wasn’t available at the time), TweetPo.st had hit Twitter’s following/follower ratio limit. Without going into too much detail, this required us to completely re-architect TweetPo.st from the ground-up using Twitter’s new Streaming API.

Originally, we thought we’d get this all done in December. But, we’re a small team working on 3 products (awe.sm, TweetPo.st, and fbShare.me). So, sometimes things don’t happen as quickly as we’d like. However, we dropped the ball on communications in this case. We didn’t want to announce a revised schedule until we had one we felt we could stick to, and new things continued to come up that kept us from finishing TweetPo.st. So, instead we went radio silent, which was not the right thing to do.

We apologize for not handling the situation as well as we should. And we hope you find the new version of TweetPo.st worth the wait when we make it publicly available in the next few weeks.




« Previous page     |     Next page »