This page includes information about the standard data elements provided by CDP out-of-the-box. For any data element specifically configured for your tenant, see your tenant-specific documentation.
Global Audience Content
An audience can be broken up into segments, variants, or both. The term global audience includes everyone in your audience, irrespective of whether they belong to a segment, variant, or both. The following section explains the content elements, which you can apply to the global audience:
Customer Attributes
Customer Attributes content elements are a superset of what the table in the Audience section describes.
The following table lists the Customer Attributes content elements that do not exist in the Audience section. The default value for most attributes is Unknown.
| Name | Description |
|---|---|
| Address1 | The Address1 of your customer’s winning address. The default value is Unknown. By default, CDP promotes the addresses that are DPV, certified, recent, opted-in to receive mail, and more complete. |
| Address2 | The Address2 of your customer’s winning address. The default value is Unknown. By default, CDP promotes the addresses that are DPV, certified, recent, opted-in to receive mail, and more complete. |
| Email address | The winning email address of the master customer after CDP’s Identity Resolution Engine de-duplicates child customer profiles. |
| Email hash | A SHA-256 hash of the winning email address of the master customer after CDP’s Identity Resolution Engine de-duplicates child customer profiles. |
| First name | The winning first name of the master customer after CDP’s Identity Resolution Engine de-duplicates child customer profiles. |
| Last name | The winning last name of the master customer after CDP’s Identity Resolution Engine de-duplicates child customer profiles. |
| Middle name | The winning middle name of the master customer after CDP’s Identity Resolution Engine de-duplicates child customer profiles. |
| Mobile phone | The winning mobile phone number of the master customer after CDP’s Identity Resolution Engine de-duplicates child customer profiles. |
| Primary Phone | The winning phone number of the master customer after CDP’s Identity Resolution Engine de-duplicates child customer profiles. The default value is Unknown. |
| Salutation | Salutation deduced by CDP’s Identity Resolution Engine. |
| Secondary phone | The winning secondary phone number of the master customer after CDP’s Identity Resolution Engine de-duplicates child customer profiles. |
| Title | The title to use for your customers as provided by your standard customer feed. The default value is Unknown. |
| Zip Code suffix | The zip code extension of your customer’s winning address. The default value is Unknown. By default, CDP promotes the addresses that are DPV, certified, recent, opted-in to receive mail, and more complete. |
Content Models
Content models allow you to output details such as attributes or metadata from sources other than the customer-level attributes.
Important
While you perform a search operation, ensure that you first navigate to the specific category and then specify the search term. If you try to search at the top level of the Content tab, the system does not display the desired results.
Machine Learning Content Models
These content models output details are constructed from CDP’s machine learning models. The content models are:
- Machine Learning Segments: For 1:1 machine learning models where each customer receives only one score per model. For example, Likelihood models such as likelihood to convert, engage, buy, and Clustering models such as behavior and product clusters. This content model outputs details about the ML segment, which can be a decile score for likelihood models, or a descriptive cluster name like ‘Discounters’ or ‘Swimwear’.
- User to Product Recommendations: Outputs a list of all products recommended to the customer by CDP.
Product-Oriented Content Models
These content models output details about products linked to customers.
The content models are:
Last Products Purchased: Outputs a list of all products purchased by the customer on the last transaction date only.
For example, Customer ID 12345 makes the following purchases on the given dates:
Transaction Date Product 1 Product 2 Product 3 January 1st A B C January 10th M N N/A January 15th X Y N/A A CDP user may use the model expecting to capture all products from all the three transactions as depicted in the preceding table. However, the model captures the products purchased on the last transaction date only, that is, January 15th.
If you require the model to capture products from all the transactions, contact Support to enable the transaction details content model.
- Last Products Browsed: Outputs a list of all products browsed by the customer.
- Last Abandoned Products: Outputs a list of all products that were added to the cart by the customer after their most recent transaction.
- User to Product Recommendations: Outputs a list of all products recommended to the customer by CDP.
- Favorite Products: Outputs a list of top N most commonly purchased products, ranked by quantity and followed by revenue. The default value of N is 10. You can update the value in the CDP user interface. These products are purchased two or more times in the past X months or days. Here, X is the timeframe that you can select.
- Subscription: Outputs the top N subscriptions and shares the user-defined field values for subscription, product, and subscription-product mapping attributes. The default value of N is 10. You can update the value.
Organization-Oriented Content Models
These content models output details about organizations or stores linked to the customers.
The content models are :
- Closest Store Details: Outputs the physical organization or retail store that is located closest to the customer geographically (calculated by comparing the center of the store’s zip code and the customer’s primary addresses zip code).
- Primary Store Details: Outputs the physical organization or retail store that the customer has transacted at most often (ordered by transaction count).
Customer-Oriented Content Models
These content models output details of abstractions above or below the master customer. For example, a household is above a master customer since a household encompasses multiple master customers. Child customers are below a master customer since multiple child customers or source customer records are de-duplicated by CDP to construct a master customer. Those content models are :
- Household Details: For customers that have householding turned on, this outputs the household that the customer belongs to.
- Cross-Brand Customer Details: For customers that utilize master customer groups, this outputs details about the master customer group that the customer belongs to.
- Child Customer Details: Outputs a list of all child customers that were de-duplicated to construct the master customer.
Calculated Content Models
These content models are calculated at the time of campaign execution and allow for more dynamic content options. The content models are :
- Campaign Details: Outputs details about the CDP campaign for every output record.
- Echo: Outputs the exact same text (string) for every output record. The user inputs a header name for the column and some text that is repeated (echoed) for every output record.
- Event count in a time frame - Browse Product/Product Category: Outputs the total number of event occurrences in the refinement conditions and a specific time frame.
- Event count in a time frame - Email Actions: Outputs the total number of event occurrences, such as
emailClick,emailOpen, andemailSent, in the refinement conditions and a specific time frame. - Revenue in a time frame: Outputs the total amount spent by a customer in the refinement conditions and a specific time frame. You can use refinements like Line Type and Line Subtype. The possible value for Line Type is
Purchase. Possible values for Line Subtype areDemand,Canceled,Shipped, andReturned. - Transaction count in a time frame: Outputs the total number of orders by a customer in the refinement conditions and a specific time frame. You can use refinements like Line Type and Line Subtype. The possible value for Line Type is
Purchase. Possible values for Line Subtype areDemand,Canceled,Shipped, andReturned.
Content Models for Promotions
For customs that utilize CDP’s coupon distribution features and coupon history, these are the content models that allow you to include coupons in your output content:
- Distribute new coupons: Link or assign new and previously undistributed coupons to your audience from the available coupons data store, then distribute them to your audience.
- Redistribute existing coupons: Distribute coupons that are already assigned or linked to individuals and stored within CDP’s coupon history. You can use this to remind individuals about previously communicated but still unexpired and unredeemed coupons, or distribute loyalty rewards for the first time.
Segment & Variant Specific Content
Segments and Variants can only utilize a subset of the content available for the global audience. For a segment and/or variant you can include in the content:
Echo: Outputs the exact same text or string for every output record in the variant or segment. The input is a header name for the column and text that is repeated or echoed for every output record in the variant or segment.
For more information on echo content, see Setting up the echo content using the default method and Setting up the echo content using the custom method.
Dynamic functions for output content
The Echo content model supports dynamic values to enhance automation of campaigns. To use this feature, you must add in-built and pre-fixed dynamic functions in the Echo content values. When you add these dynamic functions, CDP executes them at the time of campaign execution.
Supported dynamic functions
The following table lists the currently supported dynamic functions:
| Function | Syntax | Description |
|---|---|---|
| DATE | DATE(inputValue) | Returns the date value in a specific format based on inputValue. |
| DATEADD | DATEADD(inputValue, UnitToAdd, ValueToAdd) | Adds the number of units to The supported units are minutes, hours, days, weeks, and months. The value to add can be any integer value. A negative value performs the subtraction operation to the input. |
The following are some example use cases of dynamic functions:
- For customers who qualify for a reward with an expiration of 30 days, you can use a dynamic function to dynamically update the expiration date in the campaign output.
- For customers who sign up for a program with a validity of 1 year, you can use a dynamic function to dynamically update the expiration date in the campaign output.
Supported aliases
The following table lists the currently supported aliases:
| Alias | Description |
|---|---|
| CURRENTTIMESTAMP | Place this as inputValue to use the current timestamp as the input at the time of campaign execution. It also includes the date and time parts. For example, 2023-08-07 15:05:29. |
| CURRENTDATE | Place this as inputValue to use the current date as the input at campaign execution. It only includes the date part and the time as midnight. For example, 2023-08-07 00:00:00. |
Syntax for dynamic functions
Use the following syntax for dynamic functions:
=Functionname(functionargument/s)
When using dynamic functions:
- Follow the dynamic function syntax. For example,
=DATEADD(CURRENTDATE,HOURS,5). - Do not add any space in the function. Otherwise, this feature does not work.
- Do not add any single or double quotes in the function argument. Otherwise, CDP interprets the Echo content value as a static value instead of a dynamic function.
The following are some example values where the dynamic function syntax is used inappropriately:
| Value | Reason of failure |
|---|---|
=TestFun(AnyArg) | TestFun is not a supported dynamic function. |
=DATEADD(CURRENTDATE) | The argument for the DATEADD function is invalid. |
DATE(CURRENTDATE) | The prefix = is missing. |
The following are the default configurations for DateTime and Timezone for dynamic functions:
- DateTime format:
yyyy-MM-dd HH:mm:ss - Time Zone:
UTC
If you need to change these configurations for your tenant, contact Acquia Support to request the new time format or time zone, and refer to the List of standard content elements in the Support ticket.
The following is the sample value:
{
"TIME_FORMAT": "yyyy-MM-dd HH:mm:ss",
"TIME_ZONE": "America/Los_Angeles"
}
Next steps
Once you have selected your content, you can progress forward to pick a destination: Choosing a destination.