LJ erroneously hijacks affiliate links?
Thursday, March 4th, 2010 01:43 pmIt appears that LJ added in some code which redirected links to certain e-commerce domains to other domains (although this script seems to have stopped?) (This company seems to be the one involved. Possibly this program? Also mentioned here. And explained by a user of the program here. )
http://community.livejournal.com/no_lj_ads/87066.html
http://atara.livejournal.com/631445.html
http://vichan.livejournal.com/392527.html
Not being a coder or familiar with affiliate marketing, I don't really understand the technical aspects of it, but it's not really clear what LJ really meant to do. Does anyone know what the actual intention of this code probably was? And if so, how could they muck it up so much?
It seems that, whatever the intention of this code was, that it may have caused LJ users to lose money.
http://community.livejournal.com/no_lj_ads/87066.html
http://atara.livejournal.com/631445.html
http://vichan.livejournal.com/392527.html
Not being a coder or familiar with affiliate marketing, I don't really understand the technical aspects of it, but it's not really clear what LJ really meant to do. Does anyone know what the actual intention of this code probably was? And if so, how could they muck it up so much?
It seems that, whatever the intention of this code was, that it may have caused LJ users to lose money.
no subject
Date: 2010-03-05 04:23 am (UTC)* Know people directly in Support/whatnot, and talk to them about it, and they all go off and do investigation and find stuff, and then it gets passed up the chain.
or
* Have the ability to sleuth something to the root of the cause (or at least a perceived root), write up an articulate post about it, and spread the word, complain on the
Now, this isn't always the case by any means--if an issue is obvious or easily recognized as something outside the usual pattern or related to something that was talked about in a code push, Support will definitely catch on a lot faster!
But if the issue is something fewer people are going to complain about, especially if it's similar to things malware writers do, it's hard to figure out the root of it. That's what this was. I saw a report about the affiliate link getting changed weeks ago, and that was the stock answer given (also in part because it originally came in in Italian I imagine).
I don't know if Support is as bad as it was then, but it's certainly no walk in the park even if it's better than absolute rock bottom, and they keep losing category admins to busy life schedules, etc.
no subject
Date: 2010-03-05 06:18 am (UTC)Oh, that it was malware? (the stock answer)
Well, I guess they really can't do anything about that, except hiring staff to help out. It makes me wonder how companies that do use 100% hired staff deal with the issue. (Unless the workload has gotten much worse than it was in the past?)
no subject
Date: 2010-03-05 08:52 am (UTC)So of course the Support people wouldn't have known to look out for possible funky things happening to affiliate links. That puts any mysterious affiliate yoinkage happening into the realm of Mysterious Glitches, and those are a lot more work to track down and figure out, and since Support is overworked, there is not a lot of time to do that. And, well, affiliate links being wrong is kind of...not the highest user support priority? I mean, I think trying to figure out other technical glitches that are affecting people's use of the site probably attracts more effort. If not a lot of people are reporting it (and I don't think there were--else it would have come out a lot sooner), then it's harder to bump it up the priority list.
no subject
Date: 2010-03-05 08:56 am (UTC)The whole testing thing seems really ridiculous. To have the links not even going to the right place... Totally defeats the whole "secret" nature of the program. Probably no one would have figured it out for awhile if it weren't for that.
I suppose not too many people really use/care about affiliate links, but I'm surprised that more people didn't notice links being borked, so perhaps there were other technical things that triggered the problem.
no subject
Date: 2010-03-07 12:22 am (UTC)