@mattab opened this Issue on June 29th 2018 Member

When using Content Tracking https://matomo.org/docs/content-tracking/ on a page with hundreds of content blocks being tracked, we find that Content Tracking can cause huge POST requests to the tracking API. Some of these requests are 50kb or 100kb in size.

Example:
too large post requests with content tracking

User has also reported that sometimes the request was too large and causing 500 errors and "Php warning: unknown, input variables exceeded 2500"

The goal of this issue would be to see if we can find a more efficient way to send the content tracking data. For example. we would not need to send all the tracking API parameters in the request each time, we could only change the parameters that change between each request.

@mattab commented on September 3rd 2018 Member

Moving into 3.7.0 as to see if we can find a simple solution to be able to enable Content Tracking on all websites even when hundreds of elements are tracked on a page.

Powered by GitHub Issue Mirror