The Custom Attributes feature improves data model flexibility and adaptability, simplifying the creation and display of new custom attributes within the application. Customers can integrate new mapping fields using APIs or pre-mapped SFTP connectors, enhancing dynamic data management.

Features¶

Data model extension: Access up to 210 custom fields that are compatible with data types such as strings, decimals, integers, and dates. These fields integrate with default base and aggregated summary entities and are preset as blank for immediate use.
Self-service UI: Modify the display name and description of custom attributes in the Customer, Transition, TransactionItem, Events, Product, and ProductCategory tables.
Surface across module: View custom attributes in the Campaign+ and Metrics modules. CDP surfaces the custom attributes across these modules for uniform data representation and across-the-platform usage.
Integration (API): Map new source systems or enhance existing ones with custom attributes for quick adaptation to changing data requirements. Perform mapping exercises with a restricted list of entities and custom fields that are essential for both API and SFTP integrations.
Auto-population: Load any existing text into the Display Name and Description fields.

Capabilities¶

Data engineers and IT professionals can:

Add new fields to the CDP data model to upgrade source systems. This initiative adds fresh data to strategies and enhances reporting and campaign targeting.
Strive for flexibility in choosing the best integration method for business goals, using either API or SFTP to match operational requirements.
Evaluate new sources and metrics to achieve business goals. They design and deploy custom integration pipelines by selecting API or SFTP as required. This method guarantees consistent data flow to the CDP and provides deeper analytical insights.

Specifications for surfacing custom attributes¶

Attribute	Specifications
Customer(60 attributes)	c_customerstringattribute01 until c_customerstringattribute30 c_customerintergerattribute01 until c_customerintergerattribute10 c_customerdecimalattribute01 until c_customerdecimalattribute10 c_customerdateattribute01 until c_customerdateattribute10
Transaction(30 attributes)	c_transactionstringattribute01 until c_transactionstringattribute15 c_transactionintergerattribute01 until c_transactionintergerattribute05 c_transactiondecimalattribute01 until c_transactiondecimalattribute05 c_transactiondateattribute01 until c_transactiondateattribute05
TransactionItem(30 attributes)	c_transactionitemstringattribute01 until c_transactionitemstringattribute15 c_transactionitemintergerattribute01 until c_transactionitemintergerattribute05 c_transactionitemdecimalattribute01 until c_transactionitemdecimalattribute05 c_transactionitemdateattribute01 until c_transactionitemdateattribute05
Event(30 attributes)	c_eventstringattribute01 until c_eventstringattribute15 c_eventintergerattribute01 until c_eventintergerattribute05 c_eventdecimalattribute01 until c_eventdecimalattribute05 c_eventdateattribute01 until c_eventdateattribute05
Product(30 attributes)	c_productstringattribute01 until c_productstringattribute15 c_productintergerattribute01 until c_productintergerattribute05 c_productdecimalattribute01 until c_productdecimalattribute05 c_productdateattribute01 until c_producttdateattribute05
ProductCategory(30 attributes)	c_productcategorystringattribute01 until c_productcategorystringattribute15 c_productcategoryintergerattribute01 until c_productcategoryintergerattribute05 c_productcategorydecimalattribute01 until c_productcategorydecimalattribute05 c_productcategorydateattribute01 until c_productcategorydateattribute05

Application availability¶

The following entities support data types such as string, date, integer, and decimal to ensure versatile data capture and presentation:

Entity	Availability Actions	Metrics
Customer(base)	N/A	N/A
Customer Summary
String	CAMPAIGN¹, CONTENT², LOOKUP³	Dimension
Date	CAMPAIGN, CONTENT	Dimension
Decimal/Integer	CAMPAIGN, CONTENT	Measure
Transaction(base)	N/A	N/A
Transaction Summary
String	CAMPAIGN, CONTENT, LOOKUP	Dimension
Date	CAMPAIGN, CONTENT	Dimension
Decimal/Integer	CAMPAIGN, CONTENT	Measure
Transaction Item(base)	N/A	N/A
Product(base)	N/A	N/A
Product Summary
String	CAMPAIGN, CONTENT, LOOKUP	Dimension
Date	CAMPAIGN, CONTENT	Dimension
Decimal/Integer	CAMPAIGN, CONTENT	Not considered
Product Category
String	CAMPAIGN, CONTENT, LOOKUP	Not considered
Date	CAMPAIGN, CONTENT	Not considered
Decimal/Integer	CAMPAIGN, CONTENT	Not considered
Event
String	CAMPAIGN, CONTENT, LOOKUP	Not considered
Date	CAMPAIGN, CONTENT	Not considered
Decimal/Integer	CAMPAIGN, CONTENT	Not considered
¹ CAMPAIGN - A targeted marketing initiative that uses personalized communication to engage customers. ² CONTENT - An export attribute that populates on downstream channels. ³ LOOKUP - A dynamic function that displays field values.

Scope for future enhancements¶

CDP Studio Apps currently do not support the following features. These feature will be planned in future release.

Self-Service UI
- Select and modify multiple attribute types or update all attributes in the data models.
- Add new fields to the data models.
Metrics
Support for aggregate measure of custom attributes for the following entities:
- Customer Summary: data type: decimal/integer Aggregate=AVG
- Transaction Summary: data type: decimal/integer for transaction item Aggregate=SUM
- Product Summary data type: string, date, decimal/integer.
- Product category: all data types.
360 Profiles
- Support for 360 Profiles
Provisioning
- An automation script or tool to identify time zone mismatches by comparing system time to a reference or checking logs for time zone data.
- A notification feature to Jenkins to automatically send email or Slack alerts to stakeholders if a time zone issue stops the pipeline.

Sample API integration¶

Add a new system source to CDP or extend an existing source system with new attributes, once you get self-service integration access.
Complete mapping exercises using the dw tracker.
Perform the JSON mapping exercise with the CDP schema base.

CDP stores the data in the available base entity and aggregate entity.

For example, you want to push new attributes to event and customer base entities for SMS integration: c_stringAttribute01, c_dateAttribute01, c_integerAttribute01, c_decimalAttribute01.

{
    "events":[
          {
          "SourceSystemID":"Responsys",
          "c_stringAttribute01":"SMS",
          "Type":"smsClick",
          "SourceCustomerNumber":"28457933559",
          "Cookie":"",
          "c_dateAttribute01":"10092023",
          "SourceListNumber":"27169",
          "c_stringAttribute02":"253209",
          "SourceMessageNumber":"155749",
          "OperatingSystem":"UNKNOWN",
          "LinkName":"coupons",
          "c_decimalAttribute01":"3",
          "URL":"https://acquia.com"
        }
    ],
    "customers":[
        {
          "SourceSystemID":"Responsys",
          "c_stringAttribute01":"SMS",
          "SourceCustomerNumber":"28457933559",
          "c_integerAttribute01":"3172722349",
          "MobilePhone":"3172722349",
          "MobilePhoneValidity":"valid"
        }
      ]
}