What’s Fixed
If you use the Website Pixel with the custom identify code, a visitor’s very first page load could result in their identify call being silently dropped.
The pixel needs a session token before it can identify a visitor, and that token doesn’t exist until the first page view request gets a response back from the server. If your identify code ran before that response arrived — which is common right after the pageview snippet — the call was thrown away.
Identify calls made in that window are now held and sent automatically once the session is established. Several identify calls made before the session exists are all sent, in the order they were called.
No change is needed on your site — the pixel updates itself. The tracker version on the page moves from 1.5.2 to 1.5.3, which is a quick way to confirm the update has reached you.