IdentityResolutionSettings

Update Identity Resolution Settings.

Update the identity resolution settings for this memory store, which determine how Customer Memory will use identifiers for searching, merging, and resolving profiles.

put/v1/ControlPlane/Stores/{storeId}/IdentityResolutionSettings

Headers

If-Matchstring

Example:"eyJpZCI6ImFuX2lkIiwidiI6MX0"

Allows for optimistic concurrency control by making the request conditional. Server will only act if the resource's current Entity Tag (ETag) matches the one provided, preventing accidental overwrites.

Request body

matchingRulesstring[] required

Priority list of identifiers to locate profiles to apply new data to, or for determining if two existing profiles should merge.

Individual rules are evaluated with OR logic between them, meaning that satisfying any single rule will trigger a match. Each rule is a single identifier type; compound rules are not supported.

Rules are evaluated in order.

If no rule matches against existing profiles, a new profile will be created.
If a rule matches to a single existing profile, the profile will be updated.
If a rule matches to multiple existing profiles, those existing profiles will be merged.

Example request

{
  "identifierConfigs": [
    {
      "idType": "email",
      "limitPolicy": "fifo",
      "enforceUnique": true,
      "normalization": "email"
    }
  ],
  "matchingRules": [
    "email",
    "whatsapp",
    "phone"
  ]
}

Response

Identity Resolution Settings accepted for processing.

messagestring

statusUrlstring

URI to check operation status.

Example response

{
  "message": "Identity Resolution Settings accepted for processing."
}

Changes

Changed in 1 of the 8 revisions of this API.71

Aug 11, 2026v1b0ed05460bbf71See the full diff
- ▲
  the request property identifierConfigs became required
  request-property-became-required
- ▲
  the request property matchingRules became required
  request-property-became-required
- ▲
  the code response property's max was increased from 99999.00 to 999999.00 for the response status 400
  response-property-max-increased
- ▲
  the code response property's max was increased from 99999.00 to 999999.00 for the response status 404
  response-property-max-increased
- ▲
  the code response property's max was increased from 99999.00 to 999999.00 for the response status 429
  response-property-max-increased
- ▲
  the code response property's max was increased from 99999.00 to 999999.00 for the response status 500
  response-property-max-increased
- ▲
  the code response property's max was increased from 99999.00 to 999999.00 for the response status 503
  response-property-max-increased
- ○
  added the non-success response with the status 412
  response-non-success-status-added
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Of the 8 revisions, 1 has no diff computed.

Full history