Author: unifiedsocial (page 6 of 8)

What’s the social calculus of comments? (And why should you care?)

We recently had the opportunity to present at the DataWeek Disqus Summit. Here’s a recap of our presentation, led by awe.sm’s Fred McIntyre and Disqus’ Ro Gupta.

The term “social media analytics” is thrown around frequently, but publishers and marketers still struggle to find meaningful, actionable insights into how social media drives actual business results. Fortunately, awe.sm can help.

For an example of the kind of useful findings that performance analytics can reveal, we analyzed commenting and sharing data collected by Disqus, which powers commenting on over 2.5 million websites, and awe.sm. Our findings revealed a huge opportunity for content publishers and their community managers.

The publisher funnel

image

Marketers are familiar with the concept of a sales funnel, but it applies to content publishers, too. Think of visits at the top of the funnel, pageviews the next level down, then engagement (comments) and amplification (organic sharing).

Filling the top of the funnel by acquiring traffic and increasing pageviews is a discipline unto itself. But we were interested in whether page engagement and amplification at the bottom of the funnel can help broaden the funnel’s top. Also, how are commenting and sharing behavior related to one another?

Both Sides of the Table Comment Section

When a website uses awe.sm’s earned-media measurement, we track every individual share of its content by site visitors: not just where it’s shared, but how many clicks it drives back to the site, and what on-site events take place after that. As we announced back in July, among the specific goals we can track is Disqus-powered commenting — i.e., which comments came from visitors driven by each Tweet, Pin, or Like?

image

One website that benefits from this visibility is Both Sides of the Table, the blog of venture capitalist (and awe.sm board member) Mark Suster. Mark gave us permission to explore the sharing and commenting on recent posts to see what we could learn, and the results didn’t disappoint.

Let’s scrutinize a single conversation.

In the beginning was the Tweet…

A few weeks back, Mark published this Tweet to over 125,000 followers:

image

The Tweet brought 777 clicks to his post, and resulted in 3978 pageviews (!), 5 new social followers, 13 comments on the original post or elsewhere on his blog, and 8 re-shares — social posts made by individuals who either clicked share buttons on the blog, or copied a page’s tracking link out of the address bar and pasted it into their own social workflow.

Here’s one of the shares, to a LinkedIn group for doing business in British Columbia:

image

This LinkedIn post drove 122 clicks back to Mark’s blog, 156 pageviews, an additional Twitter follower, and this Disqus comment:

image

… which led to another LinkedIn post. That post drove 5 more clicks and additional pageviews.

If you’re keeping score at home, that’s a Tweet to a blog post, which led to viewing another blog post, which led to comments and a LinkedIn post, which sent more pageviews and comments on the blog, which led to another LinkedIn post…

image

…and remember, this is just a single conversation path.

For more highly-trafficked blog posts, it’s easy to amass thousands of nodes, four or more generations deep. The quantity of available data, potentially the relationship between every comment, every social share, and every pageview, is — wait for it… — awesome.

Consider that these conversations already were taking place, without being attributed or adequately understood, and it’s possible to grasp what’s possible for the first time by using a closed-loop system to connect all the social dots.

This level of visibility makes it possible to identify which conversations drive visits and pageviews, which social posts create value, and, ultimately, the ROI of each share.

What can we learn?

When we analyzed social posts, pageviews, comments, and organic sharing across a larger data set, we found two striking conclusions:

  • Commenters — visitors who leave at least one Disqus comment on a site’s content — are 23% more likely to share site content to a social network than non-commenters.
  • Those commenters’ social posts receive 80% more clicks per post than shares of this same content by non-commenters.

In our view, it’s not surprising that people who engage with content in its comment section aremore likely to share the content on social networks, too. Having something to say about a given article is a good predictor for your inclination to share it with others.

It’s somewhat more surprising that these commenters are also more effective sharers. We’ll leave exploring the explanations for this (do people who comment also have more social followers?; do they write more compelling Tweets?…) for another time.

Regardless, these figures quantify the relationship between engagement and amplification, and raise a huge opportunity for publishers and community managers.

Now that we know that conversations drive amplification, and now that it’s possible to identify which conversations and participants are most influential at driving amplification, you’re equipped with a powerful tool for optimizing conversations, nurturing influencers, and increasing traffic and pageviews.

What you do with this knowledge is up to you, but collecting it should be your top priority.

*Originally published on awe.sm blog

Introducing awe.sm’s integration with Gumroad

One of awe.sm’s most powerful features is the ability to track your social sharing through to conversions on your site or in your app. Now, it’s time for your Neo “Whoa” moment: Social ROI!

This is particularly useful if you’re tracking how social networks drive purchases. You can assign a quantified amount to each Tweet and posts. However, if you’re using a 3rd-party storefront to process your sale, there has been no way to associate purchases there back to your shared awe.sm links.

Until now.

awe.sm has teamed up with Gumroad. Starting today, you can seamlessly track purchases that begin with clicks on awe.sm links and end in a Gumroad storefront.

Let’s try it out: check out the Tweet below. When my followers click the awe.sm link and buy that sweet Steve Aoki shirt — do this! — it triggers an awe.sm conversion, so that I can attribute every purchase directly back to that Tweet. Social marketers, rejoice!

Check out this tutorial on how to set up your awe.sm and Gumroad accounts.

If you have any further questions, feel free to contact us.

*Originally published on the awe.sm blog. 

It’s an awesome time to be awe.sm

Social is big, and getting bigger…

Last year, there were 1.4 billion social network users; by the end of this year, 60% of Internet users are expected to be on Facebook alone, which represents an increase of nearly 20% this year.

image

This growth rate and the size of this opportunity are staggering: within four years, brands’ social marketing spending will pass $11 billion per year$14 billion will be spent in social commerce, and 50% of e-commerce will be referred by social and mobile posts. In the face of year-over-year declines in traditional media advertising, it isn’t an exaggeration to describe social as the future of advertising.

…but it needs to be measured

What’s possibly most amazing about this growth is that it comes even though companies’ social investments have basically been blind gambles. According to a recent survey, 47% of marketers do not monitor social communities at all. Of those who do, 40% only measure superficial metrics such as “likes” and comment volume; and fewer than 25% measure the ROI of their campaigns.

image

Demand clearly exists for measurement and accountability in this space, and the market has responded — there is growth in the category of sales and measurement tools. But awe.sm is the only technology that measures social performance, and performance — customers acquired, visitors converted, dollars and cents — is the only measure that matters.

Brands and agencies are next

awe.sm has spent the past four years developing extensible and powerful technology for measuring the outcomes of every single social post. Since the company took its first round of funding, we rolled out a toolkit of powerful developer APIs, and developed innovative reporting tools used by some of the industry’s most interesting social-enabled software.

These developments make it possible to visualize the success of earned media — that is, how does sharing lead to business? Now, it’s time to bring this visibility to owned media — the work brands and agencies do to start conversations and spread the word on social networks.

In coming weeks, awe.sm will be rolling out a tool to view, on one screen, the entire social funnel: how many retweets, likes, and engagements did each social post receive?; how many clicks back to a site does each drive?; and what business impact — in registrations, pageviews, and transactions — resulted?

Let’s do this

I will be applying my two decades of experience in the media industry to introduce this technology to the brands and agencies on the leading edge of innovative social marketing. Meanwhile, our talented — and expanding — team continues to innovate and improve our powerful performance measurement tools. The ultimate goal is no less than revolutionizing social marketing by bringing full visibility and performance optimization to every social action.

This is ambitious, exhilarating, and … totally awe.sm.

*Originally published on the awe.sm blog. 

Introducing the new unifiedsocial.com 2.0

Introducing the new unifiedsocial.com 2.0 Today we’re proud to introduce a brand new website and two new blogs designed to help you learn more about what we’re up to: » blog.unifiedsocial.com Follow us on Tumblr, Twitter or Facebook to get updates about the research we’re doing, the products we’re building and all the social media marketing & advertising tips and tricks we’ve learned along the way.  » hack.unifiedsocial.com Our space to showcase the open-source design & engineering projects we’re working on. We’ve been busy shipping, and now it’s time to write some docs and talk a bit more about things like Caboose, Spellbinder and other projects we use every day. Stay tuned for updates and announcements.

Today we’re proud to introduce a brand new website and two new blogs designed to help you learn more about what we’re up to:

» blog.unifiedsocial.com

Follow us on Tumblr, Twitter or Facebook to get updates about the research we’re doing, the products we’re building and all the social media marketing & advertising tips and tricks we’ve learned along the way.

» hack.unifiedsocial.com

Our space to showcase the open-source design & engineering projects we’re working on. We’ve been busy shipping, and now it’s time to write some docs and talk a bit more about things like CabooseSpellbinder and other projects we use every day. Stay tuned for updates and announcements.

Export awe.sm data to CSV

One of the design objectives guiding awe.sm’s new web tool has been reducing the amount of work you need to do on your own in a spreadsheet. Marketers already spend too much time wrestling with data, when what we want are insights.

That being said, sometimes you need the raw numbers, so we’ve got your back. In addition to awe.sm’s live Google Spreadsheet tool, starting today you can export the data from any awe.sm module directly into a CSV for slicing and dicing in a spreadsheet application.

After you’ve used our query builder and explorer to save a module displaying the data you need, export in two easy steps.

  1. Mouse over the module’s title to reveal a gear icon, and select Export:Exporting an awe.sm module, step 1
  2. In the Export dialog that appears, ensure the option for Download is selected, then click the Get CSV icon.export awe.sm to CSV, step 2

Your browser will begin downloading a CSV file. Save it to your local drive, and open it into your favorite spreadsheet app.

exporting awe.sm data to CSV, step 3

A Few Notes

  • This feature is available to every awe.sm user once you switch over to our new version. (There are so many reasons to make the switch. Try it now!)
  • INTERNET EXPLORER USERS: If you’re having trouble getting the file you’ve downloaded to open into Excel, try manually adding “.csv” to the end of its filename.
  • If you really do have a “favorite” spreadsheet application, you almost certainly need a vacation.

Happy crunching! And never forget: if you have any questions or feedback, you can find ushere.

*Originally published on the awe.sm blog

PageLever + Unified

pagelever plus unified PageLever + Unified

We are excited to announce that PageLever has been acquired by Unified, an award-winning enterprise marketing technology company. Over the past year, we’ve been impressed by Unified’s products, vision and ambition. As our founders and teams interacted in the market, we saw an exciting opportunity to join forces and realize our shared vision to push social marketing and advertising forward through easy-to-use, innovative solutions that drive powerful results.

Since its launch in January 2012, Unified has been a market leader in social advertising and measurement. Unified’s Social Operating Platform has been featured in TechCrunchInformationWeekGigaOm, and many more. At Digiday’s recent Sammy Awards, Unified was named Best Social Media Platform Innovation.

The combination of Unified and PageLever creates an end-to-end platform for social marketing insights, social audience engagement, and social advertising. The combined companies will serve over 300 customers, including leading Global 2000 enterprises and agencies. Team PageLever is excited to be immediately joining Unified’s team in its San Francisco and New York offices.

All current PageLever customers will continue to receive the same access to PageLever that they have enjoyed to date. Your experience will only get better as we integrate with Unified in the near future. In addition, PageLever customers may upgrade to the Unified Social Operating platform, which will give them access to a new suite of social advertising and amplification tools that support Twitter, LinkedIn, StumbleUpon, and YouTube, in addition to Facebook.

We couldn’t have gotten where we are today without our customers and partners. Your ideas, challenges and questions are the lifeblood of our business.

You can find more information, including the official press release and FAQ, atwww.unifiedsocial.com/pagelever.

If you have any questions, please contact pagelever@unifiedsocial.com.

- Team PageLever

Working with External Development Teams

Content originally written by Jeremiah Lee Cohick and published on the awe.sm blog

Shortly after awe.sm’s series A funding, we were eager to begin building the larger products we envisioned. There were only 3 of us writing code at the time and we needed to rapidly expand our development bandwidth. So while we looked for talented engineers to join our team full-time, we evaluated several web application development companies to help us get a head-start in parallel.

We asked our investors and other startups for referrals. We also looked on GitHub to find contributors to the open source tools we were planning to use. After narrowing the list to three companies, we reached out and interviewed each company.

image

Our selection criteria:

  • Expertise: We had decided to use Backbone.js. The framework has few opinions on The Right Way of doing things, so we wanted a team that had opinions about using it in a large application and could justify them with their experiences.
  • Cost: We expected a rate of $100–$150 / hour and hoped to negotiate down by agreeing to a monthly minimum and a 3–6 month engagement.
  • Similar engineering ideologies: No CoffeeScript. Appreciation of Douglas Crockford‘s opinions. Use of native DOM methods over jQuery when possible. Only performant uses of LESS.
  • Size of team: We wanted a team, not a single developer. This is the “hit by a bus” factor: would we have to start over if the lead developer suddenly became unavailable? We also liked the option to have additional engineers working on self-contained features in parallel with primary development.
  • Pair programming, if any, only when necessary: In our opinion, the primary beneficiaries of pair programming are the apprentice, who’s gaining experience, and the company employing the engineers, which is creating a sustainable workforce. The benefits of pair programming to awe.sm would be minimal. That said, pair programming is useful when beginning large features, as it allows engineers to have a common understanding of integration considerations when working independently on features. We wanted a team that had this pragmatic approach.
  • Direct access to engineers who were fluent English speakers within 3 timezones of San Francisco: We wanted a company that felt like an extension of our team, not a middle manager that proxied information asynchronously. We knew that we were going to build a product with complex data handling and GUI interactions. The ability to communicate by text and video chat throughout the workday would allow us to most effectively discuss features, bugs, and details we hadn’t considered.
  • Previous customers we could interview candidly about their experiences: We were making a big investment and needed to move quickly. We wanted to know the team’s strengths and weaknesses upfront.

After the interviews and contract negotiation, awe.sm chose Quick Left. I traveled to Boulder, CO to kick off the project with them. We discussed the features, interactions, and motivations for every detail in the spec and wireframes. They broke the user stories down in Pivotal Tracker, which awe.sm also used. With the stories agreed upon, I returned to San Francisco.

We used Campfire for text chat and Skype for video chat daily. I was able to review their commits in GitHub. We prioritized stories and bugs in Pivotal Tracker weekly. Six months and 70,000 lines of JavaScript later, the new awe.sm was ready for beta testers.

I learned a few things along the way and I’d do some things differently in the future:

  • Text chat is great, but be quick to take conversations to video chat. We seem to express ourselves better with speech than text. Screen sharing is also useful.
  • Gigantic specs with every minor detail in a single document don’t get used. Break each section of the application into a separate document. Kick off each section with a video chat. The spec should contain wireframes with relevant interactions, features within the context of user flows, and any forgettable specific technical details. If developers understand why features are valuable to the user and how the user will interact with them, many of the details don’t need to be documented. You spend less time writing specs and developers can more easily find the details they need to reference. Help the team understand your goals and they’ll make smart decisions.
  • Expect fluctuations in workload when dealing with multiple parties. awe.sm was responsible for delivering additional server-side capabilities for the front-end application Quick Left was building. We also used another contractor for the visual design. Every interdependency increases the probability of lulls and spikes in workload.
  • Managing external teams takes more time than you think. Coordinating assets, testing, and dealing with unknown unknowns is a full time job.

By the time our application launched, awe.sm had hired a front-end team. Quick Left trained our engineers on Backbone.js and helped us transition to internal development. Quick Left gave us a solid technical foundation for the new product they helped launch that we’re now rapidly iterating upon. Their quality of code matched awe.sm’s own high standard and their expertise helped us make the right engineering decisions for this product.

By working with Quick Left, awe.sm was able to take the time it needed to hire the right people and launch a new product without hampering the development of its existing products. When time-to-market is important and you have the cash available, using an outside development team can be a useful strategy for startups.

 

Older posts Newer posts

© 2014

Theme by Anders NorenUp ↑