Google Acquires Wildfire, Will Now Sell Facebook And Twitter Marketing Services

Josh Constine is a technology journalist who specializes in deep analysis of social products. He is currently a writer for TechCrunch. Previously, Constine was the Lead Writer of Inside Facebook, where he covered Facebook product changes, privacy, the Ads API, Page management, ecommerce, virtual currency, and music technology. Prior to writing for Inside Facebook, Constine graduated from Stanford University... ? Learn More

blog_image

Google has just bought social marketing software developer Wildfire, which lets brands serve marketing and ad campaigns on Facebook, Google+, Twitter, Pinterest, YouTube and LinkedIn. Wildfire has grown to 400 employees over the last four years and now serves 16,000 customers. Several sources and blogs say the sale price was around $250 million.

The acquisition will allow Google to provide advanced software and services to brands who want to run contests, sweepstakes, branded games and more on Google+. Wildfire will still operate as a marketing tool for brands on Google’s competing platforms, including Facebook, putting the search giant in a curious position where it earns money on the success of its rivals.

Google bid on buying Buddy Media but lost the deal to Salesforce. With Oracle buying other social marketing leaders Vitrue and Involver, Wildfire was the last top-tier startup in the space. Today’s deal leaves ThisMoment, another popular marketing platform, as a possible buy for old-world enterprise juggernauts like IBM or SAP.

Now it’s successfully bought one of Facebook’s biggest marketing partners. But Google hasn’t directly entered the social ad space yet. Wildfire only offers ad buying through a partnership with startup Adaptly. [Update: That's why I've just published "Wildfire Only Sells Ads Through Its Partner Adaptly, So Will Google Buy Them Too?"]

Wildfire claims there will be no disruption or immediate changes to the service it offers, which includes ad buying (via Adaptly), feed publishing, Page management, social app and contest development, analytics, social monitoring:

“We remain focused on helping brands run and measure their social engagement and ad campaigns across the entire web and across all social services — Facebook, Twitter, YouTube, Google+, Pinterest, LinkedIn and more — and to deliver rich and satisfying experiences for their consumers. To this end, Wildfire will operate as usual, and there will be no changes to our service and support for our customers.

That puts Google in an odd spot, where it will benefit if social networks such as Facebook and Twitter rise in popularity amongst brands. This hedges it against failure of Google+ as play to gain ad-targetable social data, but could heat up the on-going API battles between the top social platforms.

What if Facebook denied Wildfire API access? That could sting Google but it’s unlikely as it would send a shockwave through Facebook’s developer ecosystem. Facebook may have to grit its teeth and watch Google cash in on brands trying to infiltrate the news feed and its mobile apps. Though since it decides who gets early access to new features that can attract clients, Facebook could subtlety hurt Wildfire by favoring its competitors.

Wildfire will help handle owned marketing, such as handling Pages and other properties brands control, to complement Google’s DoubleClick AdX/Admeld paid marketing service for buying ads on search and other websites. The acquisition shows that Google understands that ads can’t do it all. Tons of brand spend is going towards managing their presences on social networks, and now it will get a slice of that pie too.

–

For more on Google’s acquisition of Wildfire, read: “Wildfire Only Sells Ads Through Its Partner Adaptly, So Will Google Buy Them Too?“

I’ll also be discussing the acquisition on stage this Friday with Facebook’s VP of ads engineering Greg Badros at TechCrunch’s Facebook Ecosystem CrunchUp in the Bay Area. There’s still a few last tickets available.


View the original article here


This post was made using the Auto Blogging Software from WebMagnates.org This line will not appear when posts are made after activating the software to full version.
-

Comments

Post a Comment

Popular posts from this blog

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more