Acquia CDP

Using Custom Attributes SFTP integration

This page provides information about the Custom Attributes SFTP integration process for the following scenario:

Data engineers want to streamline data management processes through SFTP integrations for daily flat file transfers. Their objective is to manage data with more flexibility and less manual tasks.

Setting up the CSV feed file

Prepare a comma-separated CSV feed file that matches the Custom Attributes parameter specification.

Example and template

The following is an example of a correctly formatted feed file. Use this as a template or a reference to validate your feed file.

Document NameData Feed Specifications Document

This document aims to define the file structure for exchanges between the client and CDP at the beginning of the project.
This implies:

  • For file drop data integration, define the file naming conventions, list all column names and types such as varchar and int, and provide descriptions.
  • For API data integration, define the entities and available variables, including name, type, and description.

You can track the agreed-upon data infrastructure at the beginning of the project and monitor how it evolves over time.


Column names in files must match the CDP schema unless Acquia Professional Services and you jointly agree on different names. 

The CDP backend maps all standard columns. Columns marked with an "X" are omitted from the file because this data is either unavailable in the your system or unnecessary for CDP. If these columns become necessary in the future, you must include them in the files or API calls using the same CDP column names.

Created Date[Date]
Created By[YourName]

Formatting guidelines

  • Ensure that the parameter values are formatted according to the Data Mapping standards of CDP.
  • Focus on how you format the date values.
  • Enclose column headers and data in double quotes for accurate file ingestion.

File naming convention

  • Name the file using this pattern: "AcquiaCustomAttribute_" followed by the target CDP entity (Customer and Transaction), date, and ".csv" extension.

    For example, name a file with customer attributes as AcquiaCustomAttribute_Customer_20240420.csv.

Data parsing considerations

Only parse data for the attributes that you intend to use. Keep unused custom attributes blank or exclude them from the feed file to avoid unintended insertion.


You cannot modify Custom Attribute names as they are fixed and serve as placeholders in the data model. Ensure that you make a note of the placeholder attributes that are mapped to your source system fields.

Setting the feed file drop

  • Place the prepared feed files in the CustomAttributes folder within your designated SFTP file drop space provided by Acquia. 
  • The dropped files are processed according to your tenant's daily workflow schedule.