kl_ tables filling database without any further use

[justpeeet]

We integrated the new 4.x version of the Klaviyo module. So far the 4.0.2 fixed some issues of the 4.0.1 but one issue we found after a week:

kl_sync and kl_events are constantly filling up. We had a sale this week and kl_sync is 3GB after one week and kl_events 1GB. Thats ridiculous. There should be a cron deleting all synced or moved event data.

[klaviyojad]

@justpeeet thank you for bringing this to our attention. We are aware that the table size can become unwieldy despite having the Cleanup Cron job removing rows marked as SYNCED from the kl_sync table.

We are working to develop an update to what we save to the payload column to not include the Description fields for the products of the Add to cart events. Hopefully you could see that this would remedy the table sizes. If you have other ideas on how to mitigate this problem happy to hear them as well.

[justpeeet]

Removing the description is a good point. Why do you transfer categories and and url as well. If I compare the data needed for Facebook, google or any other tracking topic usually the SKU, name, qty and price is enough. For everything else you there should be a product feed to compare / match data like images, description and so on

[cykolln]

Descriptions have been removed with version 4.0.4 - going to close this issue