Supported mapping configurations

Destinations built with Destination SDK support specific identity namespace and attribute mapping configurations, based on the destination type.

This article describes all the supported mapping configurations that you can use when configuring your destination.

When building your destination, configure your schema and identity namespaces according to one of the mapping configurations described in this page.

Supported mappings for streaming destinations streaming-mappings

Real-time (streaming) destinations built with Destination SDK support the mapping configurations described in the table below.

The configuration example below allows customers to use both mappings in the table above.

"schemaConfig":{
   "profileRequired":true,
   "segmentRequired":true,
   "identityRequired":true
},
"identityNamespaces":{
   "Customer_contact":{
      "acceptsAttributes":false,
      "acceptsCustomNamespaces":true,
      "acceptedGlobalNamespaces":{
         "Email":{

         },
         "Phone":{

         }
      }
   }
},

Map XDM attributes to custom attributes streaming-xdm-to-custom

Users can map attributes from their source XDM profile to custom attributes on your destination’s side.

Users must manually enter the name of the target custom attribute when selecting the target field mapping.

The resulting UI experience is shown in the image below.

Map identity namespaces to partner identity namespaces streaming-identity-to-identity

Users can map custom or global identity namespaces from Platform to identity namespaces that you defined.

The resulting UI experience is shown in the image below.

Supported mappings for file-based destinations batch-mappings

File-based destinations built with Destination SDK support the mapping configurations described in the table below. See the next sections for detailed mapping examples.

The configuration example below allows customers to use all the mappings from the table above.

"schemaConfig":{
   "profileRequired":true,
   "segmentRequired":true,
   "identityRequired":true
},
"identityNamespaces":{
   "Customer_contact":{
      "acceptsAttributes":false,
      "acceptsCustomNamespaces":true,
      "acceptedGlobalNamespaces":{
         "Email":{
         },
         "Phone":{
         }
      }
   }
},

Map XDM attributes to custom attributes batch-xdm-to-custom

Users can map attributes from their source XDM profile to custom attributes on your destination’s side.

For file-based destinations, the target field is automatically populated with a default attribute of the same name as the source field.

The resulting UI experience is shown in the image below.

Users can leave the default name in place or enter a custom attribute name in the target field selection screen.

Map identity namespaces to custom attributes batch-identity-to-custom

Users can map custom or global identity namespaces from Platform to custom attributes on your destination’s side.

When selecting an identity namespace as a source field, the target field is automatically populated with an equivalent identity namespace. To replace the target field with a custom attribute, users must enter a custom attribute name in the target field selection screen.

The resulting UI experience is shown in the image below.

Map identity namespaces to partner identity namespaces batch-identity-to-identity

Users can map custom or global identity namespaces from Platform to equivalent identity namespaces.

When selecting an identity namespace as a source field, the target field is automatically populated with an equivalent identity namespace.

The resulting UI experience is shown in the image below.

Next steps next-steps

After reading this article, you should have a better understanding of what mappings are supported by destinations built with Destination SDK.

To learn more about the other destination components, see the following articles: