What’s Fixed
If you use the Website Pixel with the custom identify or property view code, visitors were sometimes never getting linked to a contact, and their property views never appeared on the lead profile.
The cause was in how the pixel sent those requests. A request that is still in flight when the visitor navigates away — clicking a link, or submitting a lead form — is cancelled along with the page, unless it is explicitly marked to survive the page. Identify and event calls were not marked that way, so any that were racing a page change were dropped. Nothing went wrong on the page, nothing appeared in the browser console, and nothing on the site indicated anything had been lost, which is why this went unreported by most of the accounts it affected. Those calls also required an extra round trip to the server before the real request was sent, which made the window for this to happen wider than it needed to be.
Form captures already sent their data in the resilient way, having hit the same problem earlier. Identify and event calls now do the same, and the extra round trip is gone from every call the pixel makes.
Bug Fixes
- Identify calls now survive the visitor navigating away, so a visitor is linked to their contact record — including the common case of identifying on lead form submit.
- Property view and property save events now survive the same way, so property views land on the lead profile.
Improvements
- Page views were not affected by this problem and were being recorded normally throughout. They now travel by the same path as everything else, which removes a round trip — a consistency and speed improvement rather than a fix.
No change is needed on your site — the pixel updates itself. The tracker version on the page moves from 1.5.1 to 1.5.2, which is a quick way to confirm the update has reached you.