---
title: "Update Identity Resolution Settings."
method: PUT
path: "/v1/ControlPlane/Stores/{storeId}/IdentityResolutionSettings"
tags: ["IdentityResolutionSettings"]
---

# Update Identity Resolution Settings.

`PUT /v1/ControlPlane/Stores/{storeId}/IdentityResolutionSettings`

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

## Headers

- `If-Match` string

## Request body

- IdentityResolutionSettingsCore — Identity Resolution settings help determine if a new profile should be created, or if the incoming conversation should be added to an existing profile. These settings resolve how profiles are looked up and which profiles should merge together.
  - `identifierConfigs` IdentifierConfig[] — List of identifier types and their resolution settings.
    - `idType` string, required — Name of the identifier type. Usual values are email, phone, external_id etc.
    - `matchingAlgo` 'exact' | 'fuzzy' — The algorithm to use for matching identifier values. - `exact`, exact string match. - `fuzzy`, low precision match allowing for some variations.
    - `matchingThreshold` integer — The `fuzzy` matching threshold percentage.
    - `limit` integer — Maximum number of historical values to retain.
    - `limitPolicy` 'fifo' | 'lifo' — Removal policy to apply when the number of values exceeds the limit and is based on the timestamp of the request when the identifier was added. - `fifo`: First In First Out, removes the oldest values first. - `lifo`: Last In First Out, removes the most recent values first.
    - `enforceUnique` boolean — When enabled, more than one profile may not share the same identifier value. Adding a shared identifier to a second profile may trigger a merge. Disabling creates a compound identifier where merges are only triggered if two or more identifiers satisfy a matching rule.
    - `normalization` 'phone' | 'email' | 'trim' | 'none' — Normalization to apply to the identifier value before storing and matching. - `phone`: Normalize phone numbers to E.164 format. - `email`: Normalize email addresses by coverting to lowercase and removing spaces. - `trim`: Removes spaces from both ends of the string. - `none`: No normalization. **Important Note for Phone Number Normalization:** When using the `phone` normalization option, please adhere to the following guidelines to ensure proper formatting: - All US numbers must be at least valid 10 digit phone numbers with area code. They may also include or omit the "+1" prefix. - Non-US numbers must include a 1-3 digit country code (a "+" prefix is optional). Non-US national formats are not supported and will be interpreted as US numbers.
  - `matchingRules` string[] — Priority list of identifiers to locate profiles to apply new data to, or for determining if two existing profiles should merge. 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.

## Response `202`

Identity Resolution Settings accepted for processing.

- object
  - `message` string
  - `statusUrl` string — URI to check operation status.

## Other responses

- `400` — Bad Request
- `404` — Not Found
- `429` — This error indicates that you have sent too many requests to the API. You should retry according to the `Retry-After` response header.
- `500` — Internal Server Error
- `503` — Service Unavailable

---

[API](https://skmtc.net/twilio/apis/memory-v1.md) · [All operations](https://skmtc.net/twilio/apis/memory-v1/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/twilio/memory-v1/versions/1cfcc8fb9f19/schema)