Skip to main content
ConstraintsMember Updated is published once per change, not once per field. ChangedFields lists every field the change touched; the rest of the payload is the customer’s full state after the change. It is not published when a customer is created or deleted, or when a call changes nothing.Member Deleted is published only when the customer is actually deleted. It is the only event a deletion publishes: no Member Updated, and no Loyalty Card Deleted for the customer’s loyalty cards, which are removed in the same step. When the mobile app is set up to send deletion requests to your staff instead of deleting straight away, the request publishes nothing; Member Deleted follows once the customer is deleted.If a Member Updated payload would exceed the message size limit, CustomProperties is sent as null, while ChangedFields can still list it.The EventId of Member Updated contains a random part, so a redelivered event carries a new EventId. Don’t use it alone for idempotent processing. Member Created, Member Signed Up and Member Deleted have a stable EventId.
Published when a customer is created, signs up, changes their profile, or is deleted. Customers are called members in the API, so payloads carry MemberId; every payload also carries CustomerId, equal to MemberId.
To keep customer data in sync in your system, subscribe to Member Created, Member Updated and Member Deleted. Member Updated carries the customer’s full profile after every change, including SelectedStoreId, with the changed fields listed in ChangedFields.

Field reference

Field definitions match the member models used by the Members endpoints. See Members in the API Reference. POST /v1/members/import and POST /v1/members/import/data-import emit Member Created for new customers and Member Updated for existing ones. On imports, CreatedAt and Timestamp take the value from the request, and Member Created always has an empty CustomProperties. Member Updated is also emitted by PUT /v1/members/{memberId}/email, /phone, /activate and /deactivate, by the mobile app’s PATCH /mobile-app/v1/members, and by customer edits in the admin portal. The deprecated PUT member endpoints emit the same events. The mobile app’s DELETE /mobile-app/v1/members and deleting a customer in the admin portal emit the same Member Deleted. Member Signed Up is emitted on every successful sign-up, including when the customer already existed. The consent events from the same sign-up are published separately and can arrive after it — see Consent Events.

Schemas

Last modified on October 7, 2026