Enter a search term such as “mobile analytics” or browse our content using the filters above.
That’s not only a poor Scrabble score but we also couldn’t find any results matching
Check your spelling or try broadening your search.
Sorry about this, there is a problem with our search at the moment.
Please try again later.
In October, Twitter announced that it would be updating its Tweet button and removing the Tweet count.
That update is now live, catching many who were unaware of the impending change off guard.
Here's what publishers need to know about the removal.
I’ve been experimenting with data APIs for a couple of years now. I’m not a professional developer but it’s a lot of fun to get stuck in to see what cool content and tools can be produced.
Lately I’ve been experimenting with kimono which promises to turn websites into structured APIs from your browser in seconds.
It aims to removes the intimidating technical boundaries previously needed to develop your own API.
Sound interesting? I certainly think so!
In a world where device fragmentation is increasing, taking a mobile-first approach is yesterday's thinking.
There's no doubt that the smartphone has changed the way we all engage with the world around us.
We're all glued to apps on our mobiles (Flappy Bird anyone?). And website owners have seen the steady, inexorable rise in mobile traffic to their sites, which spawned the inevitable rethink about how web experiences are delivered on mobile devices (yes, I'm looking at you responsive design).
So it isn't surprising that the world is talking about making sure you take a 'mobile-first' approach. But I disagree.
Learning to code is similar to learning to drive. It opens up a world of opportunities.
From a marketer's point of view the ability to interpret, edit and write code is an incredibly useful skill to add to your toolkit.
What can you do with such abilities?
APIs (Application Programming Interfaces) are being rapidly adopted by large companies, public bodies and small tech start-ups with equal amounts of enthusiasm. But that’s not the case for small and medium enterprises (SMEs).
Tech startups and large companies have clear justifications and well-documented commercial incentives for constructing an API. Something else they share in common is the presence of a strong internal advocate, or API evangelist, who will personally back the API initiative and put dedicated time and energy into implementing their API strategy.
In small and medium companies the justification is less clear. The barriers to adopting API technology appear larger and the business benefits appear smaller.
In many cases the decision maker is the CEO of the SME who may not fully understand the potential opportunities or threats that APIs may mean for their business. This lack of understanding about API technology represents a significant commercial handicap for SMEs.
Here are five API opportunities and threats that every SME should be aware of:
The official launch of the Twitter Ads API was inevitable but still important for the marketing ecosystem. One of the world’s biggest human-fed and –curated platforms has taken a step in the right direction – using technology to help make marketers’ lives easier.
Twitter is taking a page out of the playbook of Facebook, which started its journey toward a mature advertising business with its own API in 2009. They built on this success with the launch of Facebook Exchange in 2012. As one of the original FBX partners, we have seen the data and scale available become important to many top brands.
As a self-confessed analytics geek, I was very excited when I first took a look at what the Google Analytics API can provide.
The best thing about it from my point of view is that it's about making the data more accessible to people who may not like digging around in figures.
So whether you are an analytics nut or whether you just want a simple way to see the numbers that matter to you, this post will help you understand why you should be considering the Google Analytics API.
Twitter wants to be a media company, and its efforts to become one have created a lot of collateral damage.
That's not at all surprising: when the company was positioned as a communications platform with an open API, developers flocked to take advantage of the connately-flowing river of data that Twitter produces. But many of those developers, as well as companies like LinkedIn, had to be cut off as Twitter's desire to be a media company realistically requires it to control the user experience, and how its content is displayed, in consumer channels.
When it comes to social networking, Facebook garners most of the attention. And for obvious reasons: Facebook is the largest social network in the world, accounts for the bulk of the spending on social ads, went public earlier this year in a record-breaking IPO and has had a volatile experience as a publicly-traded company.
LinkedIn is, by comparison, far less buzz-worthy. But don't let that fool you: the publicly-traded professional social network is valued at more than $10bn and its shares trade at a mind-boggling 695 times earnings -- a PE ratio five times that of Facebook shares.
A website isn't the only interface through which companies can interact with their customers and users. Thanks in some part to the success of companies that have used APIs to help build significant business value, a growing number of companies in both the B2C and B2B markets are building and launching their own APIs.
Most APIs, of course, aren't going to achieve Facebook-like success, and companies often make fundamental mistakes when developing an API strategy.
Ask any executive at a popular consumer internet company about mobile, and chances are she will tell you largely the same thing: mobile is absolutely crucial. For many companies, upstarts and established players alike, that means one thing: getting mobile apps right.
But while some of the biggest names in social seem to be moving in the right direction vis-à-vis their mobile apps, one may be moving in the wrong direction.