Standard output¶
The following tables are standard output of Amperity. These tables (and the attributes within them) are always available to the Segment Editor:
Predicted Affinity (when predictive modeling is enabled for your tenant)
Predicted CLV Attributes (when predictive modeling is enabled for your tenant)
This topic collects all of the attributes that are available in standard output into a single topic. It is organized alphabetically by table, and then within each table attribues it is organized alphabetically by attribute name.
Note
It is not uncommon for certain tables—Customer Attributes and Customer 360, in particular—to contain additional attributes that are custom to your tenant. The Merged Customers table is visible when working in certain areas of the Campaigns page and is the underlying source of truth for attributes in the Customer 360 table.
Tip
This topic isn’t designed to be read from end-to-end. You can if you want to, but it’s more useful as a reference that you can browse when you need it. Use your browser’s search function, type the name of an attribute you want to learn more about, and then find that attribute on the page.
Campaign Recipients¶
Campaign recipient attributes provide a record of campaigns that were sent from Amperity. Each campaign is associated with the segment that was used to build the audience (including control groups, treatment groups, and sub-audiences), the campaign launch date, and any destination to which the campaign was sent.
The following attributes are available from the Campaign Recipients table.
Attributes |
Description |
---|---|
Campaign ID |
The unique ID for a campaign. |
Campaign Name |
The name of the campaign. |
Campaign Type |
A campaign is a message or offer that is sent to a specific group of customers or recipients. A campaign may be one of the following types:
A one-time campaign represents a specific campaign message that is configured to be sent only once. A recurring campaign is sent automatically based on an updated/refreshed audience that a customer wants to receive in their outbound destination or a state change, such as an accepted return, a change to a loyalty program, or an alert based on credit card status, with a predefined campaign message and cadence to a list of recipients. |
Database ID |
The unique ID for the database. |
Database Name |
The name of the database. |
Dataset Version |
A unique ID for the dataset used with this set of campaign recipients. |
Delivery Datetime |
The date and time at which the associated campaign ID was delivered to the destination. |
Destination ID |
The unique ID for a destination. |
Destination Name |
The name of the destination to which the associated campaign ID was sent. |
Is Control |
A flag that indicates if the Treatment ID represents a control group. |
Launch Datetime |
The date and time at which the associated campaign ID was sent from Amperity to its downstream workflow. |
Segment ID |
The unique ID for the segment that generated the list of recipients for the associated campaign ID. |
Segment Name |
The name of the segment used with the associated campaign ID. |
Treatment ID |
The ID for the treatment group to which the associated campaign was sent. |
Treatment Name |
The name of the treatment group to which the associated campaign was sent. One or more treatment groups, along with a control group, are used to measure the quality of a campaign. |
Workflow ID |
The unique ID for the workflow that managed the associated campaign. |
Customer 360¶
Customer 360 attributes present a unified view of your customers across all points of engagement, including attributes that cross systems.
The following attributes are available from the Customer 360 table.
Attributes |
Description |
---|---|
Given Name |
The first name that is associated with a customer. |
Surname |
The last name that is associated with a customer. |
The email address that is associated with a customer. A customer may have more than one email address. |
|
Phone |
The phone number that is associated with a customer. A customer may have more than one phone number. |
Address |
The address that is associated with the location of a customer, such as “123 Main Street”. |
City |
The city that is associated with the location of a customer. |
State |
The state or province that is associated with the location of a customer. |
Postal |
The zip code or postal code that is associated with the location of a customer. |
Birthdate |
The date of birth that is associated with a customer. |
Gender |
The gender that is associated with a customer. |
Customer Attributes¶
The Customer Attributes table contains a series of columns that identify attributes about individuals, such as if that individual can be contacted, if a marketable email address, physical address, or phone number is available, if they are an employee, reseller, or if the individual represents a test account, along with identifying each individuals’s revenue relationship with a brand.
Note
The Customer Attributes table is built (and often customized) for your tenant. It is not part of standard output until after it has been added to your tenant, but is included here because it is often used closely with standard output to support a variety of complex use cases, such as churn prevention campaigns.
The Customer Attributes table contains the following columns:
Column Name |
Data type |
Description |
---|---|---|
Amperity ID |
String |
The unique identifier that is assigned to clusters of customer records that all represent the same individual. The Amperity ID does not replace primary and foreign keys, but exists alongside them within unified profiles. Note The Amperity ID is a universally unique identifier (UUID) that is represented by 36 characters spread across five groups separated by hyphens: 8-4-4-4-12. For example: 123e4567-e89b-12d3-a456-426614174000
|
Churn Trigger |
String |
The predicted churn status for a customer. Possible values:
Tip Use these values as part of your churn prevention campaigns. |
Churn Trigger Start Datetime |
Datetime |
The date and time at which the predicted Churn Trigger status begins. |
Contactable Address |
Boolean |
A flag that indicates if a customer can be contacted by a physical mailing address. |
Contactable Email |
Boolean |
A flag that indicates if a customer can be contacted by an email address. |
Contactable Global |
Boolean |
A flag that indicates if a customer can be contacted by phone number, email address, or physical mailing address. |
Contactable Paid Social |
Boolean |
A flag that indicates if a customer has personally identifiable information (PII) that could be used to contact them using paid social media channels. |
Contactable Phone |
Boolean |
A flag that indicates if a customer can be contacted by phone. |
Contactable SMS |
boolean |
A flag that indicates if a customer can be contacted by SMS. |
Customer Classifications |
String |
A string that contains all of the classifications for a customer. For example: “is_reseller, is_outlier” or “is_test_account”. A value of “ “ (an empty space) indicates that all classifications are false. |
Customer Type |
String |
The type of user: “customer” or “prospect”. A customer has a historical revenue relationship with a brand. A prospect does not have a revenue relationship with a brand. |
Historical Prospect Lifecycle Status |
String |
A prospect is a potential customer to whom you may want to conduct marketing activity. The status for a customer who is a “prospect”. |
Historical Purchaser Lifecycle Status |
String |
The status for a customer, based on their history and recency of interactions a brand. Possible values: “new”, “active”, “lapsed”, “dormant”, and “prospect”. Customer states are defined as “active”, “lapsed”, “dormant”, and “prospect”. Purchase behaviors are assigned across a 5 year window. A customer who has purchased within the previous 365 days (1 year) is assigned to “active” and within the previous 730 days (2 years) is assigned to “lapsed”. A customer who has not purchased within 2 years is assigned to “dormant”. |
Is Business |
Boolean |
A flag that indicates if a customer is a known or likely business. |
Is Employee |
Boolean |
A flag that indicates if a customer is or has been an employee of the brand at any time. |
Is Gift Giver |
Boolean |
A flag that indicates if a customer has purchased items as gifts. |
Is No PII Amperity ID |
Boolean |
A flag that indicates of the customer does not have personally identifiable information (PII) for name (given name, surname, full name), address (street address, city, state, postal code), email address, or phone number. |
Is Outlier |
Boolean |
A flag that indicates if the customer has abnormally high purchase behaviors in comparison to other purchasers. |
Is Primary Buyer Household |
Boolean |
A flag that indicates if a customer is the individual within a household who represents the highest lifetime revenue for that household. Note This attribute requires the Merged Households table. |
Is Prospect |
Boolean |
A flag that indicates if a customer does not have a purchase history with a brand. |
Is Purchaser |
Boolean |
A flag that indicates if the customer has a purchase history with a brand. |
Is Reseller |
Boolean |
A flag that indicates if the customer is a known or likely reseller of a product. Tip A reseller should be defined as an early repeat purchaser with a high lifetime order frequency. Use the following fields from the Transaction Attributes table to define a reseller:
|
Is Test Account |
Boolean |
A flag that indicates if the customer is a known test account for a brand. |
Marketable Address |
Boolean |
A flag that indicates if a customer has a marketable physical mailing address and has given permission to be contacted. |
Marketable Email |
Boolean |
A flag that indicates if a customer has a marketable email mailing address and has given permission to be contacted. |
Marketable Global |
Boolean |
A flag that indicates if a customer has a marketable phone number, email address, SMS number, or physical mailing address and has given permission to be contacted. |
Marketable Phone |
Boolean |
A flag that indicates if a customer has a marketable phone number and has given permission to be contacted. |
Marketable SMS |
Boolean |
A flag that indicates if a customer has a marketable SMS number and has given permission to be contacted. |
Merged Customers¶
Merged customer attributes represent your unique customers across all of the data sources that you provided to Amperity. These attributes group customer profile data—names, email addresses, phone numbers, physical addresses—based on how it was discovered from across all of the data sources that were provided to your tenant.
The following attributes are available from the Merged Customers table.
Attributes |
Description |
---|---|
Address |
The address that is associated with the location of a customer, such as “123 Main Street”. |
Address2 |
Additional address information, such as an apartment number or a post office box, that is associated with the location of a customer, such as “Apt #9”. |
Birthdate |
The date of birth that is associated with a customer. |
City |
The city that is associated with the location of a customer. |
Company |
The company, typically an employer or small business, that is associated with a customer. |
Country |
The country that is associated with the location of a customer. |
The email address that is associated with a customer. A customer may have more than one email address. |
|
Full Name |
A combination of given name (first name) and surname (last name) for a customer. May include a middle name or initial. |
Gender |
The gender that is associated with a customer. |
Generational Suffix |
The suffix that identifies to which family generation a customer record belongs. For example: Jr., Sr. II, and III. |
Given Name |
The first name that is associated with a customer. |
Loyalty ID |
The identifier for a loyalty program that is associated with a customer. |
Phone |
The phone number that is associated with a customer. A customer may have more than one phone number. |
Postal |
The zip code or postal code that is associated with the location of a customer. |
State |
The state or province that is associated with the location of a customer. |
Surname |
The last name that is associated with a customer. |
Title |
The title that precedes a full name that is associated with a customer, such as “Mr.”, “Mrs”, and “Dr”. |
Predicted Affinity¶
Product affinity attributes associate your customers to recommended audience sizes and rankings by products.
The following attributes are available from the Predicted Affinity table.
Attributes |
Description |
---|---|
Audience Size Large |
A flag that indicates the recommended audience size. When this value is “true” the recommended audience size is large. A large audience is predicted to include ~90% of future purchasers, while also including a high number of non-purchasers. |
Audience Size Medium |
A flag that indicates the recommended audience size. When this value is “true” the recommended audience size is medium. A medium audience is predicted to include ~70% of future purchasers, though it may also include a moderate number of non-purchasers. |
Audience Size Small |
A flag that indicates the recommended audience size. When this value is “true” the recommended audience size is small. A small audience is predicted to include ~50% of future purchasers, while including the fewest non-purchasers. Use a small audience size to help prevent wasted spend and reduce opt-outs. |
Product Attribute |
The field against which product affinity is measured. For example: a category, a class, or a brand. |
Ranking |
A ranking of customers by their score for this product. A rank that is less than or equal to X will provide the top N customers with an affinity for this product. |
Score |
The strength of a customers’s affinity for this product, shown as an uncalibrated probability. Tip This score is used internally by Amperity and does not directly correlate to ranking and/or audience size. Sort results by ranking, and then compare to audience sizes. Higher rankings within smaller audience sizes correlate with stronger affinity. |
Predicted CLV Attributes¶
Customer lifetime value (CLV) attributes use historical customer behavior to predict customer lifetime value during the next calendar year, including by historical customer status and historical lifetime value tier.
The following attributes are available from the Predicted CLV Attributes table.
Attributes |
Description |
---|---|
Predicted Average Order Revenue Next 365d |
The predicted average order revenue over the next 365 days. |
Predicted CLV Next 365d |
The total predicted customer spend over the next 365 days. |
Predicted Customer Lifecycle Status |
A probabilistic grouping of a customer’s likelihood to purchase again. Groupings include the following tiers:
|
Predicted Customer Lifetime Value Tier |
A percentile grouping of customers by pCLV. Groupings include:
|
Predicted Order Frequency Next 365d |
The predicted number of orders over the next 365 days. |
Predicted Probability of Transaction Next 365d |
The probability a customer will purchase again in the next 365 days. |
Transaction Attributes Extended¶
Transaction attributes are a set of extended attributes that are based on inputs from known orders and items, including first and second orders broken down by brands, channels, stores, totals, dates and times.
Transaction attributes provide the days in-between transaction events and time period rollups across prices, numbers of items within individual orders, average order values, order frequencies, and RFM scores.
Extended transaction attributes are presented as a single table (with many columns), including an Amperity ID, and fit into the following categories:
Customer flags¶
Each record has a set of flags that indicate if a customer has purchased, the number of brand interactions, the number of brand channels, and if that customer is an early repeat purchaser.
Attributes |
Description |
---|---|
Early Repeat Purchaser |
Indicates if a customer made a repeat purchase within the previous 30 days. |
Multi Purchase Brand |
Indicates if a customer has interacted with more than one brand. |
Multi Purchase Channel |
Indicates if a customer has interacted with more than one channel. |
One and Done |
Indicates if a customer has made only one purchase. Important Amperity resolves one-and-done for the data provided to it. For example, if data is provided that spans 2015-2020, a purchase in 2014 will not be in the results. |
Customer orders¶
Each record contains a subset of order data from a customers first, second, and latest order. Each set of attributes is prefixed by first, second, or latest, depending on the order data that is being summarized.
Attributes |
Description |
---|---|
<x> Order Datetime |
The datetime on which the order was made. Available attributes:
|
<x> Order ID |
The ID of the order. Available attributes:
|
<x> Order Purchase Brand |
The brand of the order made by the customer. Available attributes:
|
<x> Order Purchase Channel |
The channel in which the customer’s order was made. Available attributes:
|
<x> Order Revenue |
The total revenue for orders at each interval. Available attributes:
|
<x> Store ID |
The ID of the store where the customer made their order. This value may be NULL if the associated channel is not retail or some equivalent. Available attributes:
|
<x> total items |
The total number of items in the order. Available attributes:
|
Date differences¶
Each record contains three attributes that specify the number of days between certain events.
Attributes |
Description |
---|---|
Days Since Latest Order |
Days since latest order measures the number of days that have elapsed since a customer has placed an order. |
First to Latest Order Days |
First-to-latest order days is the number of days that have elapsed between the date of the first order and the date of the latest order. |
First to Second Order Days |
First-to-second order days is the number of days that have elapsed between the date of the first order and the date of the second order. |
Time period rollups¶
Each record contains time period rollups of the customer’s transaction history. The time periods used are lifetime, L12M (the 12 months of transaction history starting 12 months ago), LY12M (the 12 months of transaction history starting 24 months ago), and L30D (the last 30 days).
Attributes |
Description |
---|---|
<x> Average Item Price |
The average item price during the time period. Available attributes:
|
<x> Average Num Items |
The average number of items during the time period. Available attributes:
|
<x> Average Order Value |
The Average Order Value during the time period. Available attributes:
|
<x> Order Frequency |
The count of distinct order IDs that are associated with the customer during the time period. Available attributes:
|
<x> Order Revenue |
The total revenue for orders in the time period. Available attributes:
|
<x> Preferred Purchase Brand |
The brand with the greatest number of orders during the time period. Available attributes:
|
<x> Preferred Purchase Channel |
The channel with the greatest number of orders during the time period. Available attributes:
|
<x> Preferred Store ID |
The store ID with the greatest number of orders during the time period. Available attributes:
|
<x> Purchase Brands |
The count of the distinct brands a customer interacted with during the time period. Available attributes:
|
<x> Purchase Channels |
The count of the distinct channels (online, in store, etc.) that the customer interacted with during during the time period. Available attributes:
|
<x> Stores |
The count of the distinct stores that the customer interacted with during the time period. Available attributes:
|
<x> Total Items |
The total number of items purchased by the customer during the time period. Available attributes:
|
RFM¶
Amperity calculates RFM scores against transactions that occurred within the last 12 months.
Each of the recency (R), frequency (F), and monetary (M) scores are represented by a number between 0 and 9. The final RFM score is a concatenation of the individual scores: recency first, then frequency, monetary last. The final RFM score is a number between 0 and 999.
Note
RFM uses approximate calculations to optimize the performance of the Transaction Attributes table.
Attributes |
Description |
---|---|
L12M RFM Score |
The RFM score for the customer based on transactions that occurred within the last 12 months. The RFM score is represented as an integer between “0” and “999” and is concatenated using the individual recency, frequency, and monetary scores or is NULL if the customer has zero purchases within the last 12 months. |
L12M Recency |
The recency score for customer transactions that occurred within the last 12 months. The recency score is represented as an integer between “0” and “9”. Each integer represents 10%:
|
L12M Frequency |
The frequency score for customer transactions that occurred within the last 12 months. The frequency score is represented as an integer between “0” and “9”. Each integer represents 10%:
|
L12M Monetary |
The monetary score for customer transactions that occurred within the last 12 months. The monetary score is represented as an integer between “0” and “9”. Each integer represents 10%:
|
Unified Itemized Transactions¶
Item attributes provide a history of the interactions your customers have had with your products—returns, cancellations, costs, discounts, quantities, prices—sorted by customer orders for individual items, and then associated to the transactions made by your unique customers.
The following attributes are available from the Unified Itemized Transaction table.
Note
Your product catalog is joined to this table in your Customer 360 database. You should expect to find the attributes for your product catalog within this table.
Product catalog attributes describe all of the products, categories, and sub-categories that exist within your brand.
Common product attributes include Product Category, Product Description, Product ID, and Product Subcategory; however, product catalogs are often tenant-specific and you should expect to see additional product attributes that are unique to your tenant.
Attributes |
Description |
---|---|
Customer ID |
A custom semantic tag that is applied to interaction records to identify a field that is used in downstream processes to associate interaction records to the Amperity ID. |
Is Cancellation |
A flag that indicates if the item was canceled. |
Is Return |
A flag that indicates if the item was returned. |
Item Cost |
Item cost is the cost to produce all units of an item. |
Item Discount Amount |
Item discount amount is the discount amount that is applied to all units that are associated with a single item within a single transaction. |
Item Discount Percent |
Item discount percent is the percentage discount that is applied to all units that are associated with a single item within a single transaction. |
Item List Price |
Item list price is the manufacturer’s suggested retail price (MSRP) for all units of this item. The manufacturer’s suggested retail price (MSRP) is the price before shipping costs, taxes, and/or discounts have been applied. MSRP is sometimes referred to as the base price. |
Item Profit |
Item profit represents the amount of profit that is earned when all units of an item are sold. |
Item Quantity |
Item quantity is the total number of items in an order. When an item has been returned or an order has been canceled, item quantity is the total number of items that were returned and/or canceled. |
Item Revenue |
The total revenue for all units of an item, after discounts are applied. When an item has been returned or the order has been canceled, the total revenue for all items that were returned and/or canceled. |
Item Subtotal |
An item subtotal is the amount for an item, before discounts are applied. |
Order Datetime |
Order datetime is the date (and time) on which an order was placed. |
Order ID |
An order ID is the unique identifier for the order and links together all of the items that were part of the same transaction. When an item has been returned or when an order has been canceled, the order ID is the unique identifier for the original order, including the returned or canceled items. |
Product ID |
The unique identifier for a product. A stock keeping unit (SKU) is an identifier that captures all of the unique details of any individual product, including specific attributes that differentiate by color, size, material, and so on. For example, a shirt with the same color and material, but with three different sizes would be represented by three unique SKUs and would also be represented by three unique product IDs. |
Unit Cost |
Unit cost is the cost to produce a single unit of one item. |
Unit Discount Amount |
Unit discount amount is the discount amount that is applied to a single unit of one item. |
Unit List Price |
Unit list price is the manufacturer’s suggested retail price (MSRP) for a single unit of an item. The manufacturer’s suggested retail price (MSRP) is the price before shipping costs, taxes, and/or discounts have been applied. MSRP is sometimes referred to as the base price. |
Unit Profit |
Unit profit represents the amount of profit that is earned when a single unit of an item is sold. |
Unit Revenue |
The total revenue for a single unit of an item. When an item has been returned or the order has been canceled, the total revenue for a single unit of an item that was returned and/or canceled. |
Unit Subtotal |
A unit subtotal is the amount for a single unit of one item, before discounts have been applied. |
Unified Transactions¶
Orders attributes provide a history of the transactions your customers have made with your brand—channel (store, online, etc.), currency, dates and times, costs, discounts, quantities—sorted by each transaction made by your unique customers.
The following attributes are available from the Unified Transactions table.
Attributes |
Description |
---|---|
Currency |
Currency represents the type of currency that was used to pay for an item. For example: dollar. |
Customer ID |
A custom semantic tag that is applied to interaction records to identify a field that is used in downstream processes to associate interaction records to the Amperity ID. |
Digital Channel |
The digital channel through which a transaction was made. For example: Facebook, Google Ads, email, etc. |
Order canceled Quantity |
The total number of items in the original transaction that were canceled. |
Order canceled Revenue |
The total amount of revenue for all canceled items in the transaction. |
Order Cost |
Order cost represents the total cost of goods sold (COGS) for a single transaction, minus returns, cancellations, and discounts. Cost of goods sold (COGS) are the direct costs of producing goods that are sold by a brand, including the costs of materials and labor to produce the item, but excluding indirect expenses like distribution or sales. |
Order Datetime |
Order datetime is the date (and time) on which an order was placed. |
Order Discount Amount |
Order discount amount is the total discount amount that is applied to the entire order. |
Order Discount Percent |
Order discount percent is the percentage discount that is applied to the order value for the entire transaction, in addition to any item or unit-specific discount percentages. |
Order ID |
An order ID is the unique identifier for the order and links together all of the items that were part of the same transaction. When an item has been returned or when an order has been canceled, the order ID is the unique identifier for the original order, including the returned or canceled items. |
Order List Price |
Order list price is the total value for a transaction, as defined by the manufacturer’s suggested retail price (MSRP) for all units of this item. The manufacturer’s suggested retail price (MSRP) is the price before shipping costs, taxes, and/or discounts have been applied. MSRP is sometimes referred to as the base price. |
Order Profit |
Order profit is the amount of profit that is earned from a single transaction. |
Order Quantity |
Order quantity is the total number of individual items associated with the transaction. |
Order Returned Quantity |
Order returned quantity is the total number of items in the original transaction that were returned. |
Order Returned Revenue |
Order returned revenue total amount of revenue for all returned items in a transaction. |
Order Revenue |
The total amount of revenue for all items in a transaction after discounts are applied, ignoring returns and/or cancellations. |
Order Shipping Amount |
The order shipping amount is the total cost of shipping all items in the same transaction. |
Order Subtotal |
An order subtotal is the amount for an order, before discounts are applied. |
Order Tax Amount |
An order tax amount is the total amount of taxes that are associated with an entire order. |
Payment Method |
A payment method is how a customer chose to pay for the items they have purchased. For example: credit card, gift card, or cash. |
Purchase Brand |
The brand for which a transaction was made. Note This attribute should only used when more than one brand is present in your tenant. |
Purchase Channel |
A purchase channel is the channel from which a transaction was made. For example: in-store or online. |
Store ID |
A store ID is a unique identifier that is identified with the location of a store. |
Sum Item Discount Amount |
The sum of discount amounts is the total of all discount amounts that were applied to each item within a transaction. |
Sum Item Revenue |
The sum of itemized revenue for the original order, not including returns and/or cancellations. |