Please download the new version of WordBay via your admin dashboard or the link on the site sidebar. This update is critical if you have geotargetting switched OFF! There were two major areas of fixes:
RSS-related “fixes”
After continued discussions about the possibility of WordBay somehow not generating RSS feeds properly and possibly accounting for a reduction in clicks on the part of some users, I sat down on Sunday and took another in-depth look at the RSS feed parameters and the results produced by them. I do want to point out once again that the RSS feed is NOT properly (or at all!) documented by eBay, thus all scripts using the eBay RSS feed have effectively reverse-engineered the feed to one extent or another to determine the function of the different parameters. After painstaking work I now have a detailed list of many of the parameters and what they do. I had never actually written them out like that before and you will not find this list anywhere on the net to my knowledge - my “competitors” are probably keeping it to themselves, but I plan to publish these in a subsequent post. But what I wanted to know, and some users too, was is there anything about the RSS url generated by WordBay which could cause “rover” (affiliate) links to not be generated or tracked properly?
The upshot of my investigation was as follows. Comparing the feed url (the “rss.api” one) produced by the EPN feed generator, with the feed url produced by WordBay, and remembering that each parameter affects the results of the RSS search in some way there are the following difference:
Category 1 (differences in parameters with known function)
- some 6 parameters supported by the EPN generator that are not supported by WordBay, e.g. “Search description as well as title”, “Auction only/Bin only” etc. (I just never got round to including these) and thus are omitted
- some 6 parameters supported by WordBay but not by the feed gen, e.g. “Min/max price”, “Min no. of bids”. These I originally reverse-engineered from the eBay Advanced Search page and appear to work as advertised. They are probably omitted from the feed gen for simplicity’s sake.
I believe neither of the above category of parameter can have any effect whatsoever on click tracking.
Also, however, there were:
Category 2 (differences in parameters of unknown function)
- 2 or 3 parameters (catref, from and saaff) that are present in both, but whose function is unknown (like I say, no docs). saaff appears to specify the affiliate network, i.e. it is always set to afepn in the feed, and I though, hey-ho, what if this is not set in WB, THAT could affect tracking! However, a brief check confirmed this has long been present in WB - false alarm.
- 2 parameters present in the feed gen URL that were NOT present in WordBay’s URL and whose significance is undocumented, together with the meaning of the the values assigned to them. These I added, with the values supplied by the feed gen (which do not appear to vary).
- 5 parameters present in the WB URL (reverse-engineered from Advanced Search) but not present in the feed gen URL which are undocumented and which I thus deemed unnecessary and dropped.
In this second category of parameters of unknown function I can be less sure that one of them does not have anything to do with tracking. However, I think it unlikely that the changes I made will change anything: a) we still have no firm evidence that invalid (untrackable) links are being produced through the feed in WordBay and b) it is likely that provided the campaign ID, i.e. the afepn parameter (and probably saaff) are specified, rover links are being produced correctly.
In addition, I took this new version of the plugin and refreshed a listings test page a total of 30 times - 10 times each for US, UK and DE eBay sites, and did not get anything but valid “rover” links every time. I also tried this (though somewhat fewer times) with v1.22 and got the same result.
I also created a test campaign and tried to get some clicks tracked (yes, clicking my own links - so ban me) but these were not tracked at all, probably because I was logged in to eBay or something, so this proves nothing really.
But if there is any chance that this will make any difference I am glad I took the time to investigate this and clean up the code in WB. Keep me posted. At the moment I still tend to be of the opinion that EPN’s tracking is up the spout. I have tried to be as transparent as possible regarding the WB code, whereas we have no insight whatsoever into the workings of EPN and QCP…
Geo-targetting-related fix
Oh man! Hangs head in shame! It turns out that geotargetting has been fixed permanently ON for all users ever since it was introduced way back when, and all for the want of a single “=” in the code. That’s quite a biggie, and does explain some vague complaints from way back when that it was behaving oddly. So SORRY!! In my defence, it is very hard to test and debug geotargetting as obviously I cannot hop over to another country to do so, and also I live in a non-eBay country, but I am surprised this was not picked up sooner.
In my opinion this is not a major disaster - the IP database IS fairly accurate on the whole, perhaps you might have lost a very small percentage of visitors who were wrongly targetted, and on the other side perhaps you had some Norwegian visitors who might have bought from US eBay (say!) but I don’t think there are too many of those.
Anyway, it’s fixed now.
I have also added (from 1.22 actually, but cleaned it up a bit) a strong suggestion in the admin backend for people to subscribe to the feed for this blog as these kinds of critical updates are happening frequently, yet there are people out there still using some absolutely ancient versions of WordBay, which can’t be good!
Let’s stay in touch, I have a feeling the RSS click-tracking saga is not over yet…
Posted on March 2nd, 2010 by markowe
Filed under: Uncategorized | 9 Comments »