What is LJ doing to my links? Part 3
Mar. 4th, 2010 05:01 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
So I was looking at some of the other LJ support requests involving outboundlink.net. I came across this support request, in which
dstroy provides a Target link that outboundlink.net was completely mangling for her.
Well, outboundlink.net seems to have been upgraded, because it worked for me when I clicked on it. Since all LJ pages now include the Javascript that does this (even your profile page! even the front page!), it went through their redirector.
I looked at the URL for an affiliate ID.
AFID=Performics_Driving%20Revenue%20Inc
Iiiiiiinteresting!
Now, view the source of this page. Or any other LJ page. Down by the bottom, you'll find the <script> tags that load and invoke the dRev.js code.
I think I have an answer for this anonymous web developer's question!
I will let you do the math on how much money outboundlink/drivingrevenue* is making off of this lack of communication on ID changing.
(Of course, there is the chance that they're keeping track of all their redirects, and paying out some percentage to their clients like LJ. Maybe.)
I could mmmmmaybe let this slide if they only added affiliate IDs to unaffiliated links. But they don't; they rip your affiliate ID off and substitute their own. To make matters worse, untangling just who is owed what in stolen affiliate-link juice will be a nightmare - they grab, and presumably save, the referring URL, but how many people clicking on links are doing them from their friends page?
I smell lawyermeat here.
[ edit: I can easily come up with narratives for this happened that are just a comedy of errors rather than malicious money-grubbing on LJ's part. But this is really making Dreamwidth look better and better; this is far from the first time LJ's pulled shortsighted bottom-line shit like this. The test Amazon link in the previous post is the first and only time I've linked to an e-commerce site here, but the whole underhandedness of this whole thing is really pissing me off. They'd better have a damn good explanation. And a damn good apology. ]
* I am now 99% certain that outboundlink.net is part of Driving Revenue's system - they're running off the same IP address, the function that activates it is called "drivingRevenue()", and now this plaintext Target affiliate ID?
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
Well, outboundlink.net seems to have been upgraded, because it worked for me when I clicked on it. Since all LJ pages now include the Javascript that does this (even your profile page! even the front page!), it went through their redirector.
I looked at the URL for an affiliate ID.
AFID=Performics_Driving%20Revenue%20Inc
Iiiiiiinteresting!
Now, view the source of this page. Or any other LJ page. Down by the bottom, you'll find the <script> tags that load and invoke the dRev.js code.
var DR_id = '1111'; // Is this a real ID or we'll be asked to change it? :)
I think I have an answer for this anonymous web developer's question!
I will let you do the math on how much money outboundlink/drivingrevenue* is making off of this lack of communication on ID changing.
(Of course, there is the chance that they're keeping track of all their redirects, and paying out some percentage to their clients like LJ. Maybe.)
I could mmmmmaybe let this slide if they only added affiliate IDs to unaffiliated links. But they don't; they rip your affiliate ID off and substitute their own. To make matters worse, untangling just who is owed what in stolen affiliate-link juice will be a nightmare - they grab, and presumably save, the referring URL, but how many people clicking on links are doing them from their friends page?
I smell lawyermeat here.
[ edit: I can easily come up with narratives for this happened that are just a comedy of errors rather than malicious money-grubbing on LJ's part. But this is really making Dreamwidth look better and better; this is far from the first time LJ's pulled shortsighted bottom-line shit like this. The test Amazon link in the previous post is the first and only time I've linked to an e-commerce site here, but the whole underhandedness of this whole thing is really pissing me off. They'd better have a damn good explanation. And a damn good apology. ]
* I am now 99% certain that outboundlink.net is part of Driving Revenue's system - they're running off the same IP address, the function that activates it is called "drivingRevenue()", and now this plaintext Target affiliate ID?
no subject
Date: 2010-03-04 10:35 pm (UTC)no subject
Date: 2010-03-05 12:23 am (UTC)I'm linking your entries on this in my journal post. Thanks again for your work!
no subject
Date: 2010-03-05 12:35 am (UTC)no subject
Date: 2010-03-05 01:30 am (UTC)Easy way for non code savvy people to fix it. Yay!
no subject
Date: 2010-03-05 01:43 am (UTC)If you do that, LJ will stop dropping this code into pages it generates for you. But log out and look at the same pages, and it'll go back to sticking it in.
The real fix, which is part of what I've been doing, is to bitch loud enough that LJ realizes they've been caught doing something that makes their users start making noises about leaving, so they take it out. *grin*
no subject
Date: 2010-03-05 01:46 am (UTC)no subject
Date: 2010-03-05 01:59 am (UTC)How long that will be, I dunno.
no subject
Date: 2010-03-05 03:41 am (UTC)It sounds like LJ is using Affiliate VB from Driving Revenue. The description is the closest thing I could find to this situation:
Specifically designed and optimized for vBulletin, our patent pending software works by dynamically finding and appending your existing outbound links with a tracking code so that you earn revenue for driving sales to our partners. The original posted link is not modified, making this completely transparent to your members. Affiliate vB easily installs directly into your AdminCP as a plugin.
Again, I am definitely no expert, but from everything I have seen, this was not an accident at all. It looks like a cover-up, and since it's hidden, this all being a "mistake" is believable. I would hope this isn't true at all because, if it is, they can remove it at any time.
Would they really do this?? I'm mistaken, right??
no subject
Date: 2010-03-05 04:02 am (UTC)And the "accident" is that (a) DR's code is sloppy, and made its presence known by altering links it shouldn't have touched at all; (b) DR's code is sloppy, and made its presence known by changing affiliate links on already-affiliated links (despite a half-assed attempt to not operate on affiliated links, and (c) DR's redirection/link-affiliating/tracking server made its presence known by going down for a while today.
If this had been better-implemented (tested the code on a wider set of links so as to not get false positives in what it decides to fiddle with, run the redirect/affiliate/track server on LJ's machines so they only go down when LJ is already down), I probably wouldn't have noticed it, and neither would have anyone else. Not for a lot longer. And they would've scavenged a lot more affiliate payoffs.
As is, incompetent implementation on the part of LJ ("Is this a real ID or we'll be asked to change it? :)") means that LJ probably got nothing out of this, but DR got a couple months of affiliate juice from everyone using LJ as a point of entry into an e-commerce site, and LJ just gets another wave of people saying "that's enough, I'm leaving for Dreamwidth".
no subject
Date: 2010-03-05 04:30 am (UTC)=^;^=
no subject
Date: 2010-03-05 03:48 pm (UTC)I like how their sales pitch uses the phrase "completely transparent" to mean the exact opposite.
transparent: characterized by visibility or accessibility of information especially concerning business practices
Yeah, that's what not they're selling, is it?
no subject
Date: 2010-03-05 04:12 pm (UTC)