19 October 2026 (v2.168)
Production ✅
Purse Identity v2.168 brings a few new features and updates:
As always, we fixed a few items for you.
Fields sent to custom email and SMS providers
You can now choose which profile and message fields a custom email or SMS provider receives in personalizations.
-
The recipient (
emailorphone_number) andtemplate_idare always sent. -
An empty Fields list sends only those keys. In the Purse Identity Console, Fields groups those keys into Standard fields, Message fields, and Custom fields.
-
A new provider starts with Standard fields and Message fields selected.
-
Custom fields stay unselected until you add them.
-
A provider configured before this release keeps the fields it already sent, plus any custom fields already selected.
For example, with Fields set to given_name, has_password, and custom_fields.loyalty_id, a password reset email looks like this:
{
"email": "clarence@example.com", (1)
"template_id": "password_reset", (1)
"personalizations": {
"given_name": "Max",
"has_password": true, (2)
"custom_fields": {
"loyalty_id": "123456" (3)
}
}
}| 1 | email and template_id are always present. |
| 2 | has_password appears only for the password_reset template. |
| 3 | loyalty_id appears only when that custom field is present on the profile. |
For more details, see Custom email providers and Custom SMS providers.
Social identity in pre-event webhooks
The login pre-event webhook now includes the social identity being attached to an existing profile in user.identities.
This applies when a user logs in with a new provider that matches an existing profile by email or phone number, or links a provider from the social accounts screen.
The identity has the same fields as on signup, so you can accept or reject the link based on the social account being attached.
For more details, see Social identity in pre-event webhooks.
