Been working on this for an hour, and this is as far as I get in Tracker Debugger:
Broken event
Error message: Deserialization of log failed: cannot parse integer from empty string at line 1 column 1701
Seems like this should be easier. Here’s the website if you want to see the code: https://www.ripcorddesign.com
Please send a raw request (look at the pic how to get it). We’ll take a look.
By the way, we have an idea how to improve these messages and plan to deliver it relatively quickly.
It appears it’s working now, thank you for your reply. Not sure what changed, maybe it needed a bit of time, or maybe someone went in and fixed it.
I’m glad that I helped :)).
If the problem occurs again, please drop a raw request, it will be easier to debug.
Cheers
@Sean We did add a more verbose version of messages in broken events. Now you will see which tracking parameter broke the tracking request.
Hi Sebastian,
I am seeing a number of those broken events for the ‘t_fs’ parameter:
Error message: Tracking parameter t_fs has invalid value. number too large to fit in target type at line 1 column …
I have checked the raw request for one of these and I have for example “t_fs”: “621801”
According to the API documentation this parameter is:
https://developers.piwik.pro/en/15.7/tracker/http_api.html
Fetch Start - one of the Page Performance Metrics. Designed for the value of PerformanceTiming.fetchStart
integer <= 65535
Example: t_fs=7
It appears then that its value is indeed larger than the maximum allowed: is this something I should worry about? Thanks.
