If a user is using an ad blocker, their interactions will not be autocaptured in Heap. This is because ad blockers prevent Heap from loading properly to set tracking cookies and autocapture events during the session. This is expected behavior for ad blockers, and applies to any client-side tracking libraries.
As a workaround to autocapture these events, you can use our server-side Track API, which isn’t affected by ad blockers. However, it’s only possible to send server-side events for identified users in Heap (users who are associated to a unique identifier, such as email or ID).
Note that server-side tracking is not autocaptured data, so no autocaptured properties will be associated to any custom events sent to Heap server-side. But it’s likely the best way to send mission-critical event data into Heap for all users.
For more about the benefits of server-side vs. client-side tracking, see Tracking Web Custom Events Client-side vs. Server-side.