Pinpointe Release Notes — August 2026

In the New UI, the import worker has been rebuilt for better performance. Large imports — particularly those tagging contacts to one or more lists — now complete in roughly half the time they previously took. Progress also updates more frequently during the import so you can track where things stand. This update also resolves several edge cases where suppression rules were not being applied correctly during imports, including domain-level bans and entries in global suppression lists.

Reference: PINPOINTE-4642

In the New UI, you can now select a queue label for a campaign at the time you schedule it — no need to apply it separately after the fact. This helps keep your Email Message Queue organized from the moment a campaign is queued. The option appears during the scheduling step and also works via the API for customers who schedule sends programmatically.

Reference: PINPOINTE-4475

When saving an HTML email in the editor, the system incorrectly parsed the curly-bracket characters in the text version. This could corrupt the text version of an email and, in some accounts, cause Journeys to become locked. The underlying issue has been resolved.

Reference: PINPOINTE-4648

If a campaign was originally created from a template that has since been deleted, attempting to edit that campaign would leave the builder stuck indefinitely on a loading screen. Those campaigns now open normally so you can continue to view and edit them.

Reference: PINPOINTE-4652

Emails that use image maps — where different clickable areas of a single image each link to a different URL — were not having those links properly encoded or tracked. This meant no click data was being recorded for image map links, and link tracking domains were not being applied. Both issues are now resolved.

Reference: PINPOINTE-4397

In several areas of the New UI — including database names, list names, segment names, contact fields, and the Activity Log — special characters such as ampersands, quotation marks, and emojis were appearing as raw encoded text rather than the actual characters. These now display correctly wherever they appear.

Reference: PINPOINTE-4613

When creating a custom field with an unsupported name in the New UI, the wizard previously allowed you to proceed through all steps before showing an error at the very end. Validation now runs on the first step, so you'll see a clear message immediately if the name needs to be adjusted. Custom field names may contain letters, numbers, spaces, dashes, and underscores.

Reference: PINPOINTE-4659