When Aimerce is active, browser events are already included in the server side. Technically browser events make zero difference.

Aimerce already collects both browser and server events, deduplicates them before delivery, and sends a single clean conversion signal to Meta via Conversion API.

If browser events are also sent directly to Meta, Meta has to deduplicate the same event again, which can create unnecessary duplication risk and reduce data clarity for reporting and optimization. Also Meta’s deduplication success is around 90%-95%, so you may end up having a small percentage of event inflation.