Belboon/adbutler tracking

I have entered the partner ID in the configuration for adbutler and the HTML element (gif and flash swf) is showing correctly on the “thank you” page after completing an order.

Nevertheless, the tests using the “tracking manager” on the belboon website fail.

Looking at the code, I guess that the session tracking might not work, since the “&belboon=xxx,yyy” part of the GIF URL is not included (where xxx,yyy would be some code which is be sent with the banner click and which normally has to be stored in the session variables).

There rest (flash part), however, looks OK to me. Has anyone made any experiences with belboon tracking?

Thankful for any hint:
Stefan

Hello Stefan,

wich version is it about? There was a related bug entry about changed tracking code that was resolved with 4.2.0:
https://bugs.oxid-esales.com/view.php?id=1119

Regards

Hi Marco!

My shop version is 4.2.0_23610.

To sum up their instructions: They have three kinds of tracking methods. “Session”, “cookie” and “flash”. Although I am not sure about the technical details of the latter two, I think for the session tracking, one needs to store a post variable called “belboon” from request/banner click and add it to the img tracking link like this:

 <img 
src="http://www1.belboon.de/adtracking/lead/000004711.gif/oc=ORDERCODE&lead=1 
&belboon=xxxx,yyyy" border="0" width="1" height="1" alt="" />

The code identifies the belboon partner who put the ad on his page.

Since I don’t see that in code of the thank.tpl, I guess this variant is not implemented. Or am I missing something?

If you are interested (and you don’t have it already), I can send you the complete PDF documentation from belboon.

Thanks for your support!
Stefan

Hi Stefan,

looks like the bug wasn’t fixed completely, right?
Would you like to open it up again posting an appropriate comment?

Thanks

Hi Marco!

I was on vacation, but now I filed a new bug report #1591 (your link was not working and I didn’t found the ID).

But I guess it would take some time if this enhancement/fix is implemented in the next release. Therefore I also would appreciate a hint where the best place would be for storing the value in the session, so I can implement a workaround myself.

Cheers,
Stefan

Hi Stefan,

for some reason the bug was marked as private so you couldn’t see the link’s result. I requested to open up the bug again and to mark it as not private. You will note that adbutler for some reason changed the code and has to be updated in OXID eShop. You shall find a complete description for download there and will see what has been changed. Obviously, probably for lang disadvantages, something was missing while fixing. Maybe you could find the reason and help the dev guys out.

Cheers

Hi Marco!

I have seen no updates since the bug was reopened. Is there any schedule for this issue? We are almost ready for the go-live with our shop and if the resolution will take more time, I will dig into this myself to implement a workaround.

Cheers,
Stefan

Hi Stefan,

no idea when they are going to fix this bug. At the end of the day, a resolution in a manner of a fix would be delivered with the next release still in Q1 (if that helps you).

Regards

Does anyone know how to fix this bug in former versions (e.g. 4.2.)?
This is what I did so far, based on version 4.4 (which I downloaded to compare both versions):

  • Add our OXADBUTLERID in mysql table oxshops
  • Update the tracking code section in thankyou.tpl according to version 4.4
  • In views/oxview.php, function addGlobalParams(), add line
$this->_aViewData['belboon'] = $this->getBelboonParam();
  • In views/oxview.php, add complete function getBelboonParam()

Unfortunately, while “Cookie Tracking” and “Flash Tracking” work just fine, “Session Tracking” still does not seem to work…

Cheers
floko

P.S.: Maybe I should add that officially this bug is fixed with version 4.4. So for those of you willing to update, you do not have to care about such details. You just may use the latest version and you are done.

Seems to be working now, although I think I did not changed anything…?

So feel free to follow my instructions above to get your 4.2. version fixed! :smiley: