Application Interface Framework (AIF) has a standardized and pre-enabled SFTP connector. You can use the SFTP connector to introduce new CSV files into CDP and add new attributes into the existing data entities such as Customer, Transaction, Transaction Item, Product, Product Category, and Event. The pre-enabled SFTP connector works seamlessly with your daily refresh cycle and eliminates the need for a separate scheduling. You can use pass-through values with a preset placeholder structure in the data model that makes the custom attributes available for immediate use.

Features

The following are the features of the custom attributes SFTP integration:

• Data parsing: Helps customers to parse data into predefined custom attribute fields using the CSV file drop method.

• File processing: Processes comma-delimited CSV files with correctly named columns when the files are placed in the CustomAttributes folder of a customer’s SFTP instance. 

  • You cannot modify custom attributes' names as they are fixed and serve as placeholders in the data model. You must note the placeholder attributes that are mapped to your source system fields.

    
• Data handling: Creates new records in CDP from data added through the CustomAttribute connector. To update the existing records, contact the Acquia CDP team and request them to adjust the system configuration.
  • If the cdp.source.system.id parameter is set in the CustomAttribute connector, the UUID and email are not required. 
  • If the cdp.source.system.id parameter is not set, include UUID or email for Identity Resolution to deduplicate new customer records with the existing ones in CDP.

• Data integration:  

  • Updates the existing records if they are available in the Transaction, Transaction Item, Product, and Product Category databases in CDP.

  • Creates new Event records from the event database. 

  • Creates new records or updates the existing records in the customer database in CDP based on the parameter set in the CustomAttribute connector.

    • If the cdp.source.system.id parameter is set and matches the Standard Feed connector's source system, CDP updates the existing customer records with the same Source Customer Number. If the Source Customer Number in the Custom Attribute Customer file has no match, CDP creates new records. To set the parameter, contact the Acquia CDP team. 

    • If the cdp.source.system.id parameter is not set, CDP creates new customer records in the customer database. 

• Identity resolution: Uses an exact match Identity Resolution rule by email or UUID to link new customer custom attribute records to the existing customers in the default setup. If these rules are missing, contact the Acquia CDP team for alternate options.

• Auto-mapping: Maps data to Customer, Transaction, Transaction Item, Product, Product Category, and Event entities.

• Auto-schedule: Requires no manual intervention. Ingests file concurrently before the specified times requested to start the orchestration. On completion, the data is available across all applications, and the file can be viewed in the integration management.

• Customer attribute promotion logic to customer summary entities: Last Not Null. The most recent non-null value in the file updates the master customer record.

Custom Attributes SFTP integration

Application Interface Framework (AIF) has a standardized and pre-enabled SFTP connector. You can use the SFTP connector to introduce new CSV files into CDP and add new attributes into the existing data entities such as Customer, Transaction, Transaction Item, Product, Product Category, and Event. The pre-enabled SFTP connector works seamlessly with your daily refresh cycle and eliminates the need for a separate scheduling. You can use pass-through values with a preset placeholder structure in the data model that makes the custom attributes available for immediate use.

Features

The following are the features of the custom attributes SFTP integration:

• Data parsing: Helps customers to parse data into predefined custom attribute fields using the CSV file drop method.

• File processing: Processes comma-delimited CSV files with correctly named columns when the files are placed in the CustomAttributes folder of a customer’s SFTP instance. 

  • You cannot modify custom attributes' names as they are fixed and serve as placeholders in the data model. You must note the placeholder attributes that are mapped to your source system fields.

    
• Data handling: Creates new records in CDP from data added through the CustomAttribute connector. To update the existing records, contact the Acquia CDP team and request them to adjust the system configuration.
  • If the cdp.source.system.id parameter is set in the CustomAttribute connector, the UUID and email are not required. 
  • If the cdp.source.system.id parameter is not set, include UUID or email for Identity Resolution to deduplicate new customer records with the existing ones in CDP.

• Data integration:  

  • Updates the existing records if they are available in the Transaction, Transaction Item, Product, and Product Category databases in CDP.

  • Creates new Event records from the event database. 

  • Creates new records or updates the existing records in the customer database in CDP based on the parameter set in the CustomAttribute connector.

    • If the cdp.source.system.id parameter is set and matches the Standard Feed connector's source system, CDP updates the existing customer records with the same Source Customer Number. If the Source Customer Number in the Custom Attribute Customer file has no match, CDP creates new records. To set the parameter, contact the Acquia CDP team. 

    • If the cdp.source.system.id parameter is not set, CDP creates new customer records in the customer database. 

• Identity resolution: Uses an exact match Identity Resolution rule by email or UUID to link new customer custom attribute records to the existing customers in the default setup. If these rules are missing, contact the Acquia CDP team for alternate options.

• Auto-mapping: Maps data to Customer, Transaction, Transaction Item, Product, Product Category, and Event entities.

• Auto-schedule: Requires no manual intervention. Ingests file concurrently before the specified times requested to start the orchestration. On completion, the data is available across all applications, and the file can be viewed in the integration management.

• Customer attribute promotion logic to customer summary entities: Last Not Null. The most recent non-null value in the file updates the master customer record.