Before this PR, it used to slice objectIDs or filters to fit in the API limitation, which results to missing values in the request.
In this PR, it chunks the payload into multiple if it exceeds the limit. This is possible now due to the addition of the new sendEvents method in search-insights. However, it's not released on search-insights side yet. So we need to wait for it first.
Another context: There was no mention about filter events in the GTM documentation. Now that we're about to add it, the limit of 10 for filters will likely cause issues if customers have many filters on their website (especially with filter view event.)
Before this PR, it used to slice objectIDs or filters to fit in the API limitation, which results to missing values in the request.
In this PR, it chunks the payload into multiple if it exceeds the limit. This is possible now due to the addition of the new
sendEventsmethod in search-insights. However, it's not released on search-insights side yet. So we need to wait for it first.Another context: There was no mention about filter events in the GTM documentation. Now that we're about to add it, the limit of 10 for filters will likely cause issues if customers have many filters on their website (especially with filter view event.)