To create a SAP (CDP) Customer Activity Data Adapter

1. In MXO, choose Collect.

2. Select External Data, click Create.

3. Choose SAP (CDP) Customer Activities as the type of Data Adapter you want to add.

4. Enter a name for the Data Adapter you are adding. Using a descriptive name makes it easier for you and your team members to know when to use the Data Adapter.

5. Enter a brief description of the Data Adapter you are adding and when it should be used.

6. Enter the configuration details that define the adapter's behavior:

   Field	Description
   Select the attribute to use as a key	Select the captured data attribute you want to use as the key for looking up data in Salesforce. Captured data attributes are stored in the Customer Metadata Data Adapter.
   Test key	The existing customer key to use when testing and validating the Data Adapter configuration.
   Host	Name of the SAP regional data center to which your subscription is related.
   Business Unit	The Business Unit identifier representing the workspace for the application.
   View	The ID of the view you wish to query. You can access the viewId from the SAP Customer Data Platform console. Simply select the view you want to see and copy the ID direct from the URL.
   User	The User Key value from the SAP CDP source application.
   Secret	The Secret Key value from the SAP CDP source application.
   Identifier	Name of the customer attribute to use for identifying a customer record.
   Operand	The comparison operation to use for matching the key value for the identifier, either contains or equals. Contains allows the key to be part of the identifier and is used to search an array of identifier values.
   Purpose	The optional name of the processing purpose to use for accessing the profile data.
   Structure	The custom properties from the customer schema to include in the response. See Defining Dynamic Profile Attributes below for more details about defining the structure.

7. Click Test configuration. This tests and verifies that the new configuration details are valid.

8. Click Apply.

9. Click Save.

Defining Dynamic Profile attributes

Customer Data Platforms enable you to define the data schema that best represents your brands customer data. You can then make that schema available to MXO.

The Structure configuration setting in the data adapter is designed to provide MXO with information about the schema and its attributes. You define the schema using simple YAML syntax.

Example Data Schema

name: contract
displayName: Broadband Activity
description: the attributes expected for Broadband Contracts
properties:
  - name: Speed
    displayName: Broadband Speed
    description: the current speed of the broadband service    
    type: NUMERIC  
  - name: Monthly_Payment    
    displayName: Monthly Payment    
    description: the monthly payment amount for the contract    
    type: NUMERIC  
  - name: Contract_Name    
    displayName: Contract    
    description: the name of the broadband contract    
    type: SYMBOLIC  
  - name: Contract_Start    
    displayName: Contract Start    
    description: the date/time of the contract started    
    type: DATETIME  
  - name: Contract_End    
    displayName: Contract End    
    description: the date/time the contract terminates    
    type: DATETIME

To define your structure

Start with the heading, as shown in the example above, that defines the profile attribute structure.

name: contract
displayName: Broadband Activity
description: the attributes expected for Broadband Contracts
properties:

The properties setting is the collection (array) of properties you want to include in the activity attributes made available to MXO.

For each property, add an indented (2 spaces) list starting with a dash ( - ).

properties:
  - name: LTV    
    displayName: Lifetime Value    
    description: the customers calculated lifetime value to the brand
    type: SYMBOLIC

Provide the following settings for each property: