Performancing To PayPerPost: No Deal For Metrics
January 5, 2007 | By Darnell Clayton | Filed Under Blog Software, General, Technology
After previously courting each other, it looks as if the date between PayPerPost and Performancing is officially over. Ironically PayPerPost was really looking forward to purchasing the metrics package from Performancing, but after the latter’s kids started screaming over how ugly and evil PayPerPost was, the date began heading south (very fast).
(Performancing.com Blog) After much discussion, we’ve decided that the deal proposed by PayPerPost just isnt [sic] right for us or our community. It’s regrettable that we should part ways as I still feel that Dan and Ted are stand up guys breaking new ground, but in the end, the deal was just not right for them or us.
PayPerPost goes on to confirm this on their weblog, citing that the metrics deal “wasn’t what we were looking for right now.”
For users upset over the PayPerPost deal, the good news is that the metrics “will be given back to the community” according to Nick from Performancing. Although they will no longer support the project, users will be able to download, modify and edit the code to their pleasure (with some support from Nick when he is available).
PayPerPost is still actively looking to purchase a metrics suite for their operation, probably to see if their advertisers are getting their monies worth from paying bloggers to spin their way.
Whether you think of PayPerPost as an ingenious business model or the devils helper, one thing is for sure–a good reputation can make or break a deal, and it looks like the blogosphere may have had some influence over this previous affair.
(Update: Hat Tip: Darren via Problogger.net)
About the author:
Comments
One Response to “Performancing To PayPerPost: No Deal For Metrics”
















[...] I know things have been rough in the Performancing camp - especially since there was supposed to be a big sale, but that fell through, and then you had your products all spread out and branded separately (ScribeFire); you lacked the resources to maintain Performancing Metrics yourself - all understandable. [...]