Adding & configuring a de-dupe shape

If the incoming payload for the de-dupe shape is received from a connection shape, you'll find that the de-dupe shape settings default to the same connection instance and endpoint. In this case, the key field allows you to navigate the schema that's associated with the endpoint, and select the required data item:

If the incoming payload for the de-dupe shape is received via manual payload, API request, or webhook, there is no associated instance/endpoint and therefore no known data schema. In this case, you should enter the required key field value manually - enter the dot notation path to the required field in your data - for example: *.customerID:

If the incoming payload for the de-dupe shape is received via manual payload, API request, or webhook, you can generate the key field value dynamically using payload, flow and metadata variables.

Any combination of payload, flow and metadata variables can be used to form cache key names. For more information please see our Dynamic variables section.