Heavy debug.log file

Hello,

You can control int from a dedicated Logs page linked in the plugin’s right side menu.

Thank you!
Now i realized this heavy file is being generated after enabling conversion API settings. I followed your videos and also checked with FB′s tool to check that the info was being received correctly, but for some reason the log file is getting huge.
Could you please check what is happening in order to solve this situation?
Can i share privately the file through Wetransfer so yo can check? Maybe there is a bug on the plugin.
Thanks

Please test your server events. If they work fine, you’re all good. Just delete the logs and turn OFF that option.

Logs can contain data that’s not related to bugs, and in fact we should disable it by default.

How would you recommend to test if the server events are working fine? As this file only started to show up (and grow) after activating server API. On FB i checked the events and seems to be fine but maybe you could suggest your way to be 100% sure everything is working just finee. Thanks

The usual way: https://www.youtube.com/watch?v=QqAIO1ONc0I

And as I mention, the file will capture all sort of info, having it there doesn’t mean you have a problem, it means you send a lot of CAPI events.

• This reply was modified 3 years, 5 months ago by PixelYourSite.

You only store logs for CAPI events and not for the standar browser events? Is this the way your plugin works?

That debugging is strictly API related.

Thank you!

you’re welcome

Hello
Did you remove the log setting? i dont see it anymore…