Attachment: This is recorded now
goals-now.JPG

Attachment: This was recorded in former versions
goals-then.JPG

This bug might be because of race conditions that the trackGoal requests arrives beforer the trackPageView request. Can you please try, removing the trackPageView call, and see if the revenue is always correctly tracked?

In any case this is bug of course, just trying to confirm

Peter, can you confirm this is duped/fixed by the patch in #2168?

ignore comment:2

I suspect the problem is the request is being truncated by the web server or php (eg suhosin).

The new tracking requests are much longer and in the case of trackGoal(), revenue happens to be last parameter in the request (while idgoal is the first).

(In [4231]) refs #2195 - move revenue parameter closer to start of request (in event request string is truncated)

Thanks Anthon, I'll apply your patch and in later test stages try to switch to POST the tracking request. Reporting here when tests passed!

[4231] isn't a fix per se. If your server has limits on the length of the URL requested, query parameters, or client headers, then data may still be truncated. So, you should still take a look at your system config.

• Apache's LimitRequestLine directive (default 8K)
• IIS <requestLimits> (default maxUrl 4K, default maxQueryString 2K)
• lighttpd (total of 64K for client headers)
• nginx (total of 4K or 8K for the client header)
• Suhosin's suhosin.get.max_value_length setting (default 512 bytes)

Assuming the bug comes with a URL exceeding limits, the proper fix to this issue would be to POST the data when there is too much of it, similar to what GA recently released in their JS (probably via Iframe or other mechanisms for cross domain POSTing)