Source to CDP

Get data from the source using webhooks (triggered Blend) or an incremental block (scheduled Blend). Use a CDP Upsert block to send each object to the CDP.

Example:

Upserting objects.

an automation consisting of a Start block and a List Updated Contacts Incrementally block containing an Upsert Contact block.

CDP Upserts

Configure the Where section of the Upsert block. This section defines how to identify existing records in the CDP:

Where to upsert.

The external_id dropdown. Key is set to external_id, and Value is set to List Updated Contacts Incrementally > Item > Id.

Upsert source.

The source dropdown. Key is set to source, and Value is set to salesforce.

The Where section should have two Key/Values:

external_id: equal to the id from the source (e.g. Salesforce id)
source: name of the source platform (text, e.g. salesforce)

Configure the behavior for the creation of new objects and updates of existing objects:

Behavior for upserts.

Create New is set to yes. Update On Exist is set to yes.

Note: the CDP Upsert is smart. It will not increase the timestamp last update in the CDP when the object did not change. This avoids unnecessary webhooks being triggered by the CDP to the destination.

Add field mapping from the source to the CDP object:

Adding field mapping.

Externai Id is set to List Updated Contacts Incrementally > Item > Id. Source is set to salesforce. The fields Email, Last Name, First Name, and Phone also draw data from the List Updated Contacts Incrementally block.

Make sure to map at least following fields:

external id: the id from the source (same mapping as in the Where section)
source: name of the source platform (text, e.g. salesforce, same as in the Where section)

Custom fields

Use custom fields for data that cannot be mapped to the CDP Unified datamodel.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here