As someone who has been working on the idea of making brands human by plugging them into the fabric of society, today I definitely couldn’t miss a session called “Brand As API” hosted by Peg Faimon and Glen Platt from the Armstrong Institute for Interactive Media Studies, Miami University Oxford, Ohio.
The premise is clear and simple, and extremely agreeable:
“As brands finally begin to deliver on the promise of a 1-to-1 relationship with their customers (through social media, mobile, and data-driven tools), it is critical to develop a new foundation for that relationship. This requires brands to leave the “broadcast relationship” and, instead, build a relationship sharing communication, innovation, and the very product/service itself. Insight into this relationship can be found in the structure, language, and use of APIs (Application Programming Interface). APIs provide a set of rules – a language for connecting to data and services. To remix. To build. To leverage. To extend. Many API calls provide explicit metaphors for the ways brands can connect to customers. Generally, the API relationship provides insights into the role of brands in the customers’ life. This conversation will explore these metaphors, share case studies, and work to build a language for better connecting consumers with their brands.”
You can look at the full presentation below and get the details on how they think a brand as API might work.
The main idea behind the concept of the Brand as API is that it would allow to open up the Brand, its assets and its services and allow people (consumers, businesses, developers) to do things with that Brand, from playing with the contents and the identity of the brand all the way down to designing products and services.
Peg and Glen went on discussing the key elements of an API and how they relate and map against new ways of building meaningful relationships between brand and consumers.
While this is completely agreeable and sensible, the idea of the Brand as API as crafted in this presentation still seems to rely on two assumptions:
1) The assumption that people want to do stuff with that Brand, pulling information and data assets off a Brand in order to create something custom. And while we know this is true, we also know this only applies to a very small percentage of the user base of the Brand.
2) And the mother of all assumptions: the belief that the relationships consumers have with brands are primary while we know that consumers’ most valuable relationships are with other consumers, and what brand CAN try and do is fit in those relationships in a meaningful and/or useful way, i.e. as social currency or enablers/problem solvers.
It seems that while the analogy between brands and APIs has got incredibly long legs, we are still looking at it from the wrong perspective: the brand perspective.
What if, instead of focussing on what the API allows the user to Pull we start focussing on what the API allows the user to PUSH, meaning allowing the user to ingest a controlled and owned selection of brand-relevant personal data into the brand API such as user context, passions, interests and behaviours?
What if I could feed for example my location data to the API of my mobile network operator (plugging in my mobile gps, Foursquare or Sonar data) and get the most customised international plan based on my travel habits?
And what if consumers could ‘sell’ this personal data to brands? Consumers used to pay brands for products. We are now heading towards a future where digital data abundance means brands are going to pay consumers for their personal data. Users get customised offerings while remaining in control of their personal data, brands increase their relevance by investing on live audience intelligence rather than push strategies.
This is why I believe the biggest added value of a Brand API lies not so much in the ability to provide a Brand-to-User stream of data rather in its ability to manage a bi-drectional stream of data, where the user can shape the brand around itself using the vast amounts of personal data he is in control of.
And this is why i believe the biggest and most important asset of a brand API is not the Brand Essence, rather the User Profile.
Such an API would not be shaped around the brand but around the user and his needs. And effectively it would be an Audience API rather than a Brand API. Something that could sit at the centre of the business and power any decision the business has to take, from innovation to marketing to CRM.
But the thing is, in order to be plugged into the fabric of society brands probably need both, or even more than two APIs. Like any other social product/service out there.
















connect