About databases

Build databases against unified customer profiles built by Amperity to help your brand better understand your customers. Use Spark SQL to build any type of database that your brand requires, including customer 360-focused databases with complete customer profiles to fuel your brand’s marketing activity and quality-focused databases that help your brand’s data experts better understand each of your customer’s unique profiles.

The Customer 360 page provides:

• Visibility into the data that is behind your brand’s customer profiles and interactions along with access to the Data Explorer, from which you can explore your brand’s unified customer data

• Access to building and managing databases

• Visibility into what comprises your brand’s set of standard core tables—building blocks for all of your brand’s databases—and access to building and managing custom core tables

Customer profiles

Customer profile details are pulled from the Customer 360 table that is located in your brand’s primary customer 360 database. Customer profile details include:

• Names (first name, last name), email address, physical address, phone numbers

• Transaction details (first purchases, last purchases, total purchases, etc.)

• Other custom profile values that are unique to your company

These details can be accessed from the Profile tab on the Customer 360 page.

The Profiles tab shows the date on which the primary customer 360 database was last updated, how long it took to complete the update, and the number of customer profiles in the database.

Each customer profile is a collection of common attributes (first name, last name, email, phone, etc.), transaction attributes (first purchase, last purchase, total purchases, etc.), and other custom values that are unique to each customer’s data set. These details are summarized on the Customer 360 page under Customer Profile.

About profile attributes

Personally identifiable information (PII) is any data that could potentially identify a specific individual. PII data includes details like names, addresses, email addresses, and other profile attributes, but can also include attributes like a loyalty number, customer relationship management (CRM) system identifiers, and foreign keys in customer data.

PII profile attributes commonly available as part of the customer profile include:

Icon	Attribute Name	Description
	First Name	The first name that is associated with a customer.
	Last Name	The last name that is associated with a customer.
	Email	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.
	Zip Code	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.

Note

The profile attribute names that are shown in the profile attributes section are the same strings that were entered as friendly names when creating the Customer 360 database table in the primary customer 360 database.

These strings will default to the same as the field name if not specified as friendly names, including lower-case strings and underscores. The list of profile attributes will also depend on the SQL query that is used to create the Merged Customers table.

Refresh customer profile icons

Profile icons are shown on the Profiles tab in the Customer 360 page. Use profile icons to assign a visual element to important fields in the customer profile.

You can refresh these icons by updating the icons that are configured in the Customer 360 table for the database that is configured as the primary customer 360 database for your tenant.

Open the Customer 360 table, and then select the icon to show for the customer profile attribute from the Icon column on the Configure and save page within the Database Editor. Profile icons are applied automatically, but you may configure them when building or editing the Customer 360 table.

To apply icons to a field

1. Open the Customer 360 table in the database editor.

2. Click Next.

3. Click the icon or empty space in the Icon column to open the Select an Icon dialog box, after which you can choose an icon or search for additional icons on the Font Awesome website.

   You may use any icon in the Font Awesome library.

   Icon identifiers start with fa-, and then a unique string. For example: fa-home (for   ), fa-star (for   ), and fa-project-diagram for (  ).

   Icons are available in two styles: regular (far) and solid (fas).

   Use a style prefix in front of an icon identifier to apply that style. For example: far fa-home for a regular icon or fas fa-home for a solid icon.

4. Click Refresh Semantics to apply the a default icon to all profile attributes.

5. Click Save.

Databases

Use the Databases tab on the Customer 360 page to define any number of individual databases. Each database will have its own collection of tables and attributes. Some databases may be configured as “customer 360” databases, and then others may be configured as a “Stitch QA” database or a custom database to support any of your brand’s use cases.

Flexible merge rules

Some customer data platforms require using an inflexible merge rule across multiple fields, which results in lower quality data across your customer 360 profile. This problem is magnified when that inflexible merge rule must also be applied to multiple databases.

Amperity combines the use of flexible merge rules with a patented system that allows multiple databases to exist within the same tenant. This ensures that:

1. Merge rules are 100% configurable

2. Each field can have its own merge rule

3. Each database can have its own set of merge rules

4. Each tenant can support a variety of merge rules to meet all of the requirements for any individual use case

For example, data sources from call centers, online transactions, and email platforms may contain slightly different sets of customer profile data.

After loading this data to Amperity and assigning the Amperity ID to each of your customers, you can use flexible merge rules to support multiple customer 360 databases.

• Your operations teams can combine prioritizing the most common values for each customer with deterministic matching

• Your email marketing team can combine prioritizing customer profile values from your email platform with probabilistic matching

• Your paid media team can combine all possible values to improve match rates on platforms like Google Ads and Facebook

Ask your Amperity implementation team for recommendations and best practices for how you can configure flexible merge rules to support all of your use cases.

Database types

Databases belong to one of the following types:

• Customer 360 database

• Empty database

• Multiple customer 360 databases

• Passthrough database

• Stitch QA database

Customer 360 database

A customer 360 database contains customer profiles that are tied to all of their interactions with your company or brand. You may configure Amperity to support multiple customer 360 databases.

For example: a customer 360 database that contains all customer profiles and all interactions, and then a customer 360 database for each specific brand in your company’s brand portfolio.

Note

A customer 360 database has specific requirements on tables that must be included within that database.

Some of these tables are added as standard core tables, such as Unified Itemized Transactions, while others, such as Merged Customers, Unified Transactions, and Customer 360 must be configured within each customer 360 database.

Other use cases may require additional tables, such as for email engagement or predictive modeling.

Tables that are requred by a customer 360 database include:

• Customer 360

• Customer Attributes

• Merged Customers

• Transaction Attributes

• Unified Coalesced

• Unified Customer

• Unified Itemized Transactions

• Unified Scores

• Unified Transactions

Your brand can extend a customer 360 database to support additional use cases, such as behavioral data, clickstream, website events, email events and responses, campaign responses, and advertising performance.

Empty database

An empty database is not built from a template and does not contain any tables, as a starting point. Use an empty database to build tables to support any of your brand’s non-customer 360 use cases.

Multiple customer 360 databases

You may configure more than one database to be a customer 360 database. Each database will contain its own set of standard tables, and then each may be configured to have its own combination of standard core tables and/or domain tables that are added as passthrough tables.

Passthrough database

A passthrough database contains all stitched domain tables and all non-stitched domain tables passed through into a standalone database.

Stitch QA database

A Stitch QA database contains a series of Amperity-generated tables that can be used to validate the Amperity ID assignment to customer profiles.

Use the Stitch QA database template to quickly build a Stitch QA database for your tenant.

Database table types

Database tables belong to one of the following broad categories:

• Custom SQL

• Passthrough

• Visual templates

Custom SQL

A custom SQL table uses Spark SQL and a SELECT statement to reference any core table, domain table, or database table, including tables that represent files that were uploaded to that database.

Tip

You can use a SQL template with custom SQL tables as a starting point for certain types of tables that are required by Amperity customer 360 databases.

Select a template from the Apply template dropdown. Most templates require some configuration and all templates may be extended for your brand’s use cases.

Passthrough

A passthrough table allows a domain table to be used within the Amperity database layer. A passthrough will use a stitched domain table when it is available.

Visual templates

Use a visual template to build database tables without writing SQL. The visual template interface shows only the configurable components within a database table.

Database how-tos

Databases

• Activate database

• Add customer 360 database

• Add empty database

• Add passthrough database

• Add Stitch QA database

• Configure permissions

• Delete database

• Download schema

• Duplicate database

• Edit database

• Explore database

• Export database

• Run database

• View all databases

• View database

• View permissions

• View recent activity

• View run history

Tables

• Add core table override

• Add custom SQL table

• Add passthrough table

• Add visual template table

• Allow table in segments

• Apply table semantic tags

• Copy database table

• Delete database table

• Discard draft table

• Edit database table

• Enforce static table schemas

• Export database table

• Hide database table

• Mark columns as PII

• Configure pick-lists

• Set validation rules

Core tables

Core tables represent a normalized foundation for your brand’s data that is built from the results of the Amperity identity resolution process. Individual core tables may be used with any database your brand builds within Amperity.

There are two types of core tables:

1. Standard core tables

2. Custom core tables

Standard core tables

Standard core tables contain the results of the identity resolution process for your tenant, are maintained by Amperity, and may not be customized.

Standard core tables belong to one of the following broad categories:

Stitched domain tables	A stitched domain table is created for each domain table to which semantic tags were applied and/or in which a foreign key exists that allows Amperity to link the records in that domain table to an Amperity ID that exists in a standard core table. Stitched versions of domain tables have an added column for the Amperity ID and replace the source domain table within Amperity for all downstream use cases, but are otherwise identical to the source domain table.
Unified tables	Unified tables are generated by Stitch and consolidate your brand’s customer profile, transaction, and interaction records into a series of tables, in which rows of records are unified by the Amperity ID. The collection of unified tables that is generated within your tenant depends on the types of semantic tags that were applied to feeds and/or custom domain tables in the Sources tab.
Stitch QA tables	Stitch QA tables are generated by Stitch. Use these tables in a dedicated database to validate the quality of the identity resolution process and understand how each Amperity ID was assigned to each unique customer profile. Some Stitch QA tables are required by databases that are configured as customer 360 databases; most are only available from databases that are configured as a Stitch QA database.

Custom core tables

A custom core table is built using Spark SQL and may reference one (or more) core tables and/or domain tables. Use custom core tables to extend the normalized foundation to support additional use cases beyond what the set of standard core tables provides.

Core table how-tos

• Add custom core table

• Delete custom core table

• Edit custom core table

• Search core tables

• View core tables

• View SQL for core table

Real time tables

Real-time tables contain the data that is streamed to Amperity. Real-time tables are available alongside customer profiles in your brand’s customer 360 database. Real-time tables complement the daily batch process that is used to build and maintain complete and durable customer profiles over longer timeframes by enabling use cases that require the use of data that is updated more frequently.

This section describes tasks related to managing real-time tables in Amperity:

• Add real-time table

• Delete real-time table

• Edit real-time table name

• Update real-time data format

• Update real-time table schema

Add real-time table

A real-time table collects data that is streamed to Amperity, and then makes that streamed data available to databases and queries. Use the Real-time tables tab on the Databases page to manage real-time tables.

To add a real-time table

1. Open the Customer 360 page, and then select the Real-time tables tab.

   Click Add table.

2. In the Create real-time table dialog, do the following:

   Give the real-time table a name. Use a naming convention that associates the real-time table with its related streaming endpoint, and then identifies the type of data in the real-time table and/or the use case.

   Define the schema for the real-time table. Each field in the schema must exist in the list of fields that are streamed to Amperity by the streaming endpoint that will be associated with this table. The field names in the real-time table must match the fields that are defined for the streamed endpoint. Refer to the feed associated with the streamed endpoint to

   Note

   The schema for every real-time table contains two additional fields: received_at (the time at which data arrived at the streaming endpoint) and written_at (the time at which data was written to the real-time table).

   Choose the data format for streaming data to the real-time table: “JSON” or “XML”. If “XML” is selected a Row tag must be specified, which must identify a single row of XML data.

   

   Click Next.

3. In the Create real-time table dialog, continue:

   Select the streaming endpoint that will stream data to the real-time table. The streaming endpoint must already exist and be available from the drop-down list.

   Select the databases for which this real-time table will be available from the Queries page.

   

   Click Active.

   Important

   Real-time tables must be setto Active before they can be accessed from the Queries page.

4. Run all of the databases for which this real-time table will be available. When this step is complete, open the Queries page and verify that the real-time table is available for queries and that data in the real-time table can be returned in the results.

Delete real-time table

Use the Delete option to remove a real-time table from Amperity. This should be done carefully. Verify that both upstream and downstream processes are not relying on the real-time table before you delete it.

To delete a real-time table

1. Open the Customer 360 page, and then select the Real-time tables tab.

2. For a real-time table, open the    menu and click Delete.

3. Confirm that you want to delete the real-time table.

Edit real-time table name

Use the Edit option to rename a real-time table.

Important

You cannot change the schema or data format for a real-time table. To change the schema or data format, create a new real-time table, and then align that table to the data format and/or schema, and then associate that table with the correct streaming endpoint.

To edit a real-time table

1. Open the Customer 360 page, and then select the Real-time tables tab.

2. For a real-time table, open the    menu and click Edit.

3. Rename the table, and then click Save.

Update real-time data format

You cannot update the data format for a real-time table. Instead, create a new real-time table that defines the updated data format. You may associate this real-time table to an existing streaming endpoint or to a new streaming endpoint.

Update real-time table schema

You cannot update the schema for a real-time table. Instead, create a new real-time table that defines the updated schema. You may associate this real-time table to an existing streaming endpoint or to a new streaming endpoint.

How-tos

This section describes tasks related to building and managing databases in Amperity.

• Activate database

• Add core table override

• Add custom core table

• Add custom SQL table

• Add customer 360 database

• Add empty database

• Add passthrough database

• Add passthrough table

• Add Stitch QA database

• Add visual template table

• Allow table in segments

• Apply table semantic tags

• Choose currency symbol

• Configure permissions

• Configure pick-lists

• Copy database table

• Delete custom core table

• Delete database

• Delete database table

• Discard draft table

• Download schema

• Duplicate database

• Edit custom core table

• Edit database

• Edit database table

• Enable table versioning

• Enforce static table schemas

• Explore database

• Export database

• Export database table

• Hide database table

• Mark columns as PII

• Run database

• Search core tables

• Set validation rules

• View all databases

• View core tables

• View database

• View permissions

• View recent activity

• View run history

• View SQL for core table

Activate database

A database may be in one of the following states: active and draft:

• An active database is fully configured to use stitched output tables, is ready to be run, is ready for queries and segmentation, and may be added to a workflow.

• A draft database is in an inactive state that is not ready for segmentation. A draft database may used only for testing or experimentation. It may also be progressing toward being put into an active state.

Only databases in an Active state may be run against stitched data. Activation is a required step–“Click the Activate button.”–at the end of any process that adds or edits a database.

Add custom core table

You may add custom core tables using Spark SQL and the Custom Core Table SQL editor. Start with a SELECT statement, and then use a series of LEFT JOINs to reference core tables and/or domain tables. Use a sandbox to validate any workflows that will depend on the custom core table.

To add a custom core table

1. From the Customer 360 page, open the Core tables tab.

2. Click the Add table button. This opens the Custom Core Table SQL editor.

3. Use a SELECT statement to build the custom core table.

4. Click Validate to verify that the SQL query runs correctly, and then Next to review the settings for the custom core table.

5. Click Activate to add the custom core table.

Add databases

Amperity supports a wide variety of database types, including customer 360- and quality-focused databases your brand can build from templates, to help your brand (or brands) better understand your customers.

• Add customer 360 database

• Add empty database

• Add passthrough database

• Add Stitch QA database

Add customer 360 database

A customer 360 database is built using standard core tables that are generated by the Stitch process. These tables provide a unified view of your brand’s customer data, including customer profiles and interaction records, that is organized, merged, and linked together by the Amperity ID.

To add a customer 360 database

1. From the Customer 360 page, open the Databases tab.

2. Click Create Database.

3. Give the database a name, set the value for Template to “Customer 360”, and set the permissions that determine which users will be able to access this database, and then click Create.

   Important

   A customer 360 database requires additional configuration after the database is created.

Add empty database

Add an empty database for use cases that do not require customer 360 profiles or Stitch QA validation activities. Start with an empty database, and then add tables.

For example, after creating the empty database use the passthrough functionality to add one (or more) domain tables, and then use Spark SQL to build custom database tables against a subset of standard core tables and/or stitched domain tables to build a series of tables that support a series of non-marketing use cases.

To add an empty database

1. From the Customer 360 page, open the Databases tab.

2. Click Create Database.

3. Give the database a name, set the value for Template to “None”, and set the permissions that determine which users will be able to access this database, and then click Create.

4. Use the Database Editor to add tables to the empty database.

Add passthrough database

A passthrough database starts with all of the domain tables in your tenant, inclusive of source domain tables and stitched domain tables.

Stitched domain tables have an added column for the Amperity ID and replace the source domain table in a passthrough database, but are otherwise identical to the source domain table.

To add a passthrough database

1. From the Customer 360 page, open the Databases tab.

2. Click Create Database.

3. Give the database a name, set the value for Template to “Passthrough”, and set the permissions that determine which users will be able to access this database, and then click Create.

4. Use the Database Editor to extend the passthrough database with custom SQL tables.

Add Stitch QA database

Stitch QA is a process that monitors the quality of Stitch results. Stitch QA has two components: a database and a set of queries. The results of these queries are analyzed to help identify values that should be labeled or blocklisted and discover situations where the results of the Stitch process require tuning to match your tenant’s data set.

A Stitch QA database loaded from a template will contain a list of pre-loaded SQL queries that may be used to help validate the quality of Stitch output.

To add a Stitch QA database

1. From the Customer 360 page, open the Databases tab.

2. Click Create Database.

3. Give the database a name, set the value for Template to “Passthrough”, and set the permissions that determine which users will be able to access this database, and then click Create.

4. Use the Database Editor to extend the passthrough database with custom SQL tables.

Add tables

Use the followging types of tables to build databases to support your brand’s use cases.

• Add core table override

• Add custom SQL table

• Add passthrough table

• Add visual template table

Add core table override

A core table forms the foundation of your brand’s databases. Standard core tables are output by Stitch and provide unified data structures for all data sources to which semantic tags were applied or in which foreign keys are present that allow rows in that table to be associated with an Amperity ID.

Some use cases require a database table to have different information in a database table than what is in a core table.

To override a core table

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode, and then click Add Table.

   Important

   The table name must be the same as the original standard database table.

3. Set Build Mode to “Custom SQL”.

4. Add SQL using Spark SQL, a SELECT statement that references one (or more) standard core tables, database tables, or passed-through domain tables using a series of functions, operators, and clauses.

   Important

   The custom definition must refer to the original table, i.e. “must refer to the table that is being overridden”. In some cases, this requires using a placeholder reference. For example:

   WITH placeholder AS (
     SELECT *
     FROM override_allowed_table
     LIMIT 1
   )
   ...
   
   SELECT *
   FROM unrelated_table
   

   For example, the Unified Itemized Transactions table requires a product ID. The product_id column is created by applying the product-id semantic tag to itemized interactions records.

   However, in some cases another table contains the preferred product ID. The following example shows how to override the standard Unified Itemized Transactions table and to join more complete product ID information, such as what may be in the Unified Product Catalog table:

   SELECT
     uit.*
     ,upc.product_category AS `product_category`
     ,upc.product_description AS `product_description`
     ,upc.product_subcategory AS `product_subcategory`
   FROM
     Unified_Itemized_Transactions uit
     LEFT JOIN Unified_Product_Catalog upc
     ON uit.product_id = upc.product_id
   

5. Click Validate to verify that the SQL query runs correctly and returns the desired results. Adjust the query as necessary. When finished, click Next.

6. Verify the configuration settings for the table, including semantic tags, field descriptions, and availablility to the Segment Editor.

7. Click Save to add the table to the database.

Add custom SQL table

A SQL table is added to a database using Spark SQL and a SELECT statement that defines the table’s schema.

Tip

You can associate the Amperity ID to a unique ID in a custom SQL table. For example, “CCUST” associates a unique ID in a table to the Amperity ID:

SELECT
  CCUST.amperity_id
  ,CTX.customer_id
  ,CTX.orderid
  ,CTX.purchasedate
  ,CTX.transactiontotal
  ,CTX.pointsearned
  ,CTX.numberofitems
  ,CTX.avgitemprice
  ,CTX.productcode
  ,CTX.productcategory
  ,CTX.storeorwebid
FROM POS_Transactions AS CTX
LEFT JOIN POS_Customers AS CCUST
ON (CCUST.customer_id = CTX.customer_id)

To add a custom SQL table

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode, and then click Add Table.

3. Set Build Mode to “Custom SQL”.

   Note

   Click the Apply SQL template to select a SQL template as a starting point for the custom SQL table.

   Templates are provided for all standard tables (Customer 360, Merged Customers. Transaction Attributes, Transaction Attributes Extended, Unified Transactions, and Customer Attributes) along with additional templates for use with multibrand databases and and tables that support use cases like joining transaction attributes to the Customer 360 table, merged households, and customer lifecycle events.

4. Add SQL using Spark SQL, a SELECT statement that references one (or more) standard core tables, database tables, or passed-through domain tables using a series of functions, operators, and clauses.

5. Click Validate to verify that the SQL query runs correctly and returns the desired results. Adjust the query as necessary. When finished, click Next.

6. Verify the configuration settings for the table, including semantic tags, field descriptions, and availablility to the Segment Editor.

7. Click Save to add the table to the database.

Add passthrough table

A passthrough table adds a domain table to your database. Some domain tables are replaced by stitched domain tables, which include the Amperity ID, but otherwise are identical to the source domain table.

Important

Stitched versions of domain tables have an added column for the Amperity ID and replace the source domain table within Amperity for all downstream use cases, but are otherwise identical to the source domain table.

To add a domain table passthrough

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode, and then click Add Table.

3. Set Build Mode to “Passthrough”, and then select a table from the Source table dropdown.

4. Click Validate to verify that the SQL query runs correctly and returns the desired results. Adjust the query as necessary. When finished, click Next.

5. Verify the configuration settings for the table, including semantic tags, field descriptions, and availablility to the Segment Editor.

6. Click Save to add the table to the database.

Add visual template table

A visual template provides a user interface for specific configuration settings within a SQL table. A visual template is available for the following tables in the Databases tab within the Customer 360 page:

• Merged Customers

To add a table using a visual template

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode, and then click Add Table.

3. Set Build Mode to “Visual template”, and then select a table from the Target table dropdown.

4. Follow the directions in the visual template page for the selected table.

   Update the list of domain tables under General source priority to contain at least one domain table with fields tagged for PII semantics.

   Optional. You may define priority by semantic tag.

   When finished, click Next.

5. Click Validate to verify that the SQL query runs correctly and returns the desired results. Adjust the query as necessary. When finished, click Next.

6. Verify the configuration settings for the table, including semantic tags, field descriptions, and availablility to the Segment Editor.

7. Click Save to add the table to the database.

Allow table in segments

A database must be made visible to non-admin users of Amperity so they may access database tables from the Segments page. Visibility is required to build segments via the Segment Editor or the SQL Segment Editor. To make a database visible to non-admin users, enable the Make available in visual Segment Editor checkbox within the table editor or select the checkbox in the In VSE? column from the list of tables in a database.

What is the visual Segment Editor?

The Segment Editor is the user interface for building segments. This editor uses a series of drop-downs, picklists, conditions, and values to define an attribute profile. Refresh segment insights to see how many customers match the profile, and then activate it as a segment.

Important

Only tables that contain an Amperity ID can be made available to the Segment Editor. The Customer 360 table is made available to the Segment Editor automatically. Other tables may be made available by selecting the checkbox in the In VSE? column from the list of tables in a database.

To allow tables in segments

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode.

3. Select the checkbox in the In VSE? column to make the table available to the visual Segment Editor

4. Click Activate.

Apply table semantic tags

A semantic tag associates a table in a database with a table requirement for the database. For example: “Customer 360”, “Unified Customers”, or “Unified Scores”. Tags should be assigned by Amperity automatically as tables are built. You can see which tag is assigned to a table from the Tag column in the Database Viewer and can set the semantic tag in the table editor from the Table semantics dropdown.

Choose currency symbol

The currency symbol to show for metrics and segment insights is configurable. The following currency symbols are in the dropdown list: Australian Dollar (AUD, $), Canadian Dollar (CAD, $), United States Dollar (USD, $), Mexican Peso (MXN, ₱), British Pound (GBP, £), Euro (EUR, €), Indian Rupee (INR, ₹), and Japanese Yen (JPY, ¥).

Tip

You may configure custom currency symbols, for example South Korean Won (KRW, 원).

To choose the currency for a database

1. From the Customer 360 page, open the Databases tab.

2. Select a database and open it in Edit mode.

3. In the right-side navigation pane, under Currency, select the currency symbol to show for metrics and segment insights for this database.

   Tip

   Choose “Custom symbol” to apply a currency symbol that is not in the drop-down list.

   For example, to use South Korean Won (KRW) as the currency symbol, choose “Custom symbol”, and then enter “원” in the Custom currency symbol field.

   If you want a space to be present in-between the currency symbol and the monetary value shown, use “Custom symbol” and then add a space after the currency symbol: “원 “.

   Note

   Unicode, hex, HTML code, and HTML entity values are not supported.

4. Click Activate.

Configure permissions

Access to databases can be configured to allow only administrators, users who belong to a custom resource group, or everyone.

• Allow only admins

• Allow resource group

• Allow everyone

Allow only admins

A database that is configured for Admin only access restricts access to the database (and tables within the database) to only users who are assigned the DataGrid Administrator or DataGrid Operator policies.

To restrict access to only admins

1. From the Customer 360 page, open the Databases tab.

2. Choose a database, and then from the    menu, select Permissions. This opens the Permissions dialog.

3. Select Standard, and then choose “Admin-only”.

4. Click Save

Allow resource group

A database that is configured for Standard access may restrict access to a datbase to only users who belong to a resource group that is configured in Amperity.

To restrict access to a single resource group

1. From the Customer 360 page, open the Databases tab.

2. Choose a database, and then from the    menu, select Permissions. This opens the Permissions dialog.

3. Select Standard, and then choose a resource group.

4. Click Save

Allow everyone

Amperity includes one default resource group: “All resource groups”.

Users that are granted access to the “All resource groups” resource group are allowed to interact with all of the databases in the Customer 360 page.

A database that is configured for Standard access may allow access to everyone. When resource groups are configured in Amperity, choose the “No resource group” option from the dropdown. When resource groups are not configured, choose the the Standard radio button.

To allow everyone access to a database

1. From the Customer 360 page, open the Databases tab.

2. Choose a database, and then from the    menu, select Permissions. This opens the Permissions dialog.

3. Select Standard, and then choose “No resource group”.

4. Click Save

Configure pick-lists

A pick-list is a pre-generated list of available options for a column and is presented as a drop-down list in the visual Query Editor. A pick-list is configured when building tables in the Customer 360 page.

• Define custom values and frequencies

• Delete pick-list

• Edit pick-list

• Sort by alphabet

• Sort by alphanumeric

• Sort by most frequent

Define custom values and frequencies

A pick-list may be configured with custom values, where each item in the pick-list is specified on its own line.

Caution

Using custom values in a pick-list is uncommon. It is generally best to use automatically generated values.

To define custom values for a pick-list

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode.

3. Open a table, and then click Next to move to the second step in the table editor.

4. Select the checkbox in the Pick-list column in the row for which a picklist is to be created.

5. Click the Setup link next to the checkbox. This opens the Configure Pick-List dialog box.

6. Select a sort order.

7. Select the Custom method for the pick-list, and then enter each custom value on a new line. For example:

   Value one
   Value two
   Value three
   ...
   

8. Click Save.

Delete pick-list

A pick-list may be deleted. This will disable any selection options in the visual Query Editor.

To delete a pick-list

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode.

3. Open a table, and then click Next to move to the second step in the table editor.

4. De-select the checkbox in the Pick-list column in the row for which a picklist is to be deleted.

5. Click Save.

Edit pick-list

Many pick-lists remain static over time, but if the data inputs change, you may reconfigure the items in a pick-list.

To edit a pick-list

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode.

3. Open a table, and then click Next to move to the second step in the table editor.

4. Click the Setup link next to the checkbox. This opens the Configure Pick-List dialog box.

5. Make your changes.

6. Click Save.

Sort by alphabet

A alphabetical sort order is best for strings, such as for columns with values for cities, states, and proper names. For example:

• 1, 11, 2, and 3

• a, b, and c

To add a pick-list with an alphabetical sort order

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode.

3. Open a table, and then click Next to move to the second step in the table editor.

4. Select the checkbox in the Pick-list column in the row for which a picklist is to be created.

5. Click the Setup link next to the checkbox. This opens the Configure Pick-List dialog box.

6. Select the Alphabetical sort order.

7. Select the method with which pick-list values are applied. In nearly all situations, you should use pick-list values that are generated Automatically.

8. Click Save.

Sort by alphanumeric

A natural sort order is best for alphanumeric lists, such as for columns with scores and rankings. For example:

• 1, 2, 3, and 11

• a, b, and c

To add a pick-list with a natural sort order

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode.

3. Open a table, and then click Next to move to the second step in the table editor.

4. Select the checkbox in the Pick-list column in the row for which a picklist is to be created.

5. Click the Setup link next to the checkbox. This opens the Configure Pick-List dialog box.

6. Select the Natural sort order.

7. Select the method with which pick-list values are applied. In nearly all situations, you should use pick-list values that are generated Automatically.

8. Click Save.

Sort by most frequent

A most frequent sort order is best for columns with a smaller selection of frequently selected items, such as for columns with values for loyalty tiers, acquisition channels, or shopping preferences.

Note

Most frequent is the default sorting option for pick-lists.

To add a pick-list with a most frequent sort order

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode.

3. Open a table, and then click Next to move to the second step in the table editor.

4. Select the checkbox in the Pick-list column in the row for which a picklist is to be created.

5. Click the Setup link next to the checkbox. This opens the Configure Pick-List dialog box.

6. Select the Most Frequent sort order.

7. Select the method with which pick-list values are applied. In nearly all situations, you should use pick-list values that are generated Automatically.

8. Click Save.

Copy database table

You can create a table by copying an existing table.

To copy a table

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode.

3. Choose a table, and then from the    menu, select Copy.

4. Click Save.

Delete custom core table

Custom core tables may be deleted. Use a sandbox to validate workflows to ensure that any dependencies on the deleted custom core table are identified and fixed before promoting changes to production.

To delete a custom core table

1. From the Customer 360 page, open the Core tables tab.

2. From the list of custom core tables, open the menu for the core table you want to edit, select Delete.

3. Confirm that you want to delete the custom core table.

Delete database

A database may be deleted. This should not be done without considering the upstream and downstream effects of those changes. If the database is required by a downstream process, that process will fail. If an upstream process cannot find the database, that process will fail.

To delete a database

1. From the Customer 360 page, open the Databases tab.

2. Choose a database, and then from the    menu, select Delete.

3. Click Delete to confirm.

Delete database table

A table in a database may be deleted. This should not be done without considering the upstream and downstream effects of those changes. If the table is required by a downstream process, such as a query, the process will fail. If an upstream process cannot find the table or the schema does not match, that process will fail.

To delete a table

1. From the Customer 360 page, open the Databases tab.

2. From the menu for the database you want to view, select Edit. The Database Editor page opens.

3. Under Database Tables, from the menu for the table you want to delete, select Delete.

4. Click Delete to confirm.

Discard draft table

A table that has not been activated may be discarded. When draft tables are present in a database an alert appears at the top of the editor that is similar to “You have 1 table draft saved locally.”, along with a link to view the draft tables.

Click View drafts, and then review the listed tables. To discard a draft table, click Discard or Discard all to remove all tables in the list.

Download schema

You can download the schema for your customer 360 database. This download is configurable, but may contain all of the tables in your database. For each included table, a description of each column in that table is also provided (when that description is defined within Amperity), dependencies that may exist for each table, along with examples of the data in each column.

To download a database schema

1. From the Customer 360 page, open the Databases tab.

2. Click Explore for the database for which you want to download the schema. This opens the Data Explorer.

3. Click Download schema. This opens the Download schema dialog.

4. From the Download schema dialog, select the tables you want to include in the downloaded schema, and then click Download.

5. An XSLX file is downloaded to your local machine’s “Downloads” directory. You may open this up in any application that supports that file type.

Duplicate database

You can create a database by duplicating an existing database.

To duplicate a database

1. From the Customer 360 page, open the Databases tab.

2. Choose a database, and then from the    menu, select Duplicate.

Edit custom core table

Custom core tables may be edited. Before making changes consider the upstream and downstream effects of those changes, and then use a sandbox to validate the changes before promoting changes to production.

To edit a custom core table

1. From the Customer 360 page, open the Core tables tab.

2. From the list of custom core tables, open the menu for the core table you want to edit, select Edit. The Custom Core Table editor opens.

3. Make your changes, and then click Save.

Edit database

A database may be edited. This should not be done without considering the upstream and downstream effects of those changes. If the database is required by a downstream process, that process will fail. If an upstream process cannot find the database, that process will fail.

To edit a database

1. From the Customer 360 page, open the Databases tab.

2. Choose a database, and then from the    menu, select Edit.

3. Make your changes.

4. Click Activate.

Edit database table

Tables in a database may be edited. This should not be done without considering the upstream and downstream effects of those changes. Changes may have unintended consequences: semantics, column names, pick-lists, and so on may not be immediately available to a downstream process, which may cause that downstream process to fail. If an upstream process cannot find the table or the schema does not match, that process will fail.

To edit a table

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode.

3. Open a table and make your changes.

4. Click Save.

Enable table versioning

A version is created for all tables every time the customer 360 database is run, regardless of database run type (express, normal, or full). The amperity_version column is added to all versioned tables. The typical frequency at which the customer 360 database is run is “once per day”, but this is not always the case.

Important

The maximum number of versions is 10 and must have been created within the last 14 days.

Changes to columns within a table that is enabled for table versioning changes the schema and will cause incompatible versions to be dropped. To avoid this, add columns to the end of the table.

To enable table versioning

1. From the Database Table editor, under Advanced Settings, expand Version history.

2. Select Enable table version history.

   Note

   Version history allows queries to be made against older versions of this table. Adding or removing columns within the table will cause incompatible versions to be dropped.

   Enforce static table schemas when using table versioning. This will help avoid schema changes that cause incompatible versions to be dropped.

3. Click Save.

Enforce static table schemas

To prevent tables from being updated automatically you can enforce a static schema for the database table. When enabled, a user cannot save, activate, or run a database table when there is inconsistency between the database table’s current schema and its upstream dependency.

For example, a custom domain table with three fields is used to build a custom database table using SELECT * FROM Custom_Domain_Table. With this pattern, if the custom domain table is updated to have four fields the custom database table will also be updated.

To resolve this inconsistency, do one of the following:

1. Disable static schema enforcement for the custom database table.

2. Update the schema in the custom database table to match the updated schema in the custom domain table.

3. Update the schema in the custom domain table to match the schema required the custom database table.

To enforce a static table schema

1. From the Database Table editor, under Advanced Settings, expand Table Schema.

2. Select Enforce static schema.

   Note

   A table’s schema cannot be changed when this option is enabled.

3. Click Save.

Explore database

The Data Explorer provides a detailed way to navigate through data tables in Amperity. The Data Explorer displays each column in the data table as a row, with the column name, data type, associated semantic, and a data example. A sample of real table data is available available on another tab.

A full-screen mode for the data explorer is available from most areas within Amperity that show data tables in the database. This mode enables detailed exploration of each table, including an overview, the data table schema, examples of data, and source table details.

Tip

You can search for databases and columns in the database from the search bar in the Data Explorer. Search results are filtered automatically, grouped by database table, then by column name, and then by database property.

To open the Data Explorer

1. From the Customer 360 page, open the Databases tab.

2. Choose a database, and then click Explore.

   This opens the Data Explorer.

Export database table

The process for exporting tables is the same as exporting databases.

Explore data lineage

Data lineage is a graph visualization that shows how all of the data within your tenant connects.

You can access the data lineage view the following ways:

• On the top of the Sources page, click the Tools menu and then click Data lineage.

• On the top of the Customer 360 page, click Data lineage.

This opens the full graph and all data sources (nodes) are visible as starting nodes in the graph. Click any data source to explore how data moves from that data source into domain and database tables. Click any table to see its relationship to other tables and the sources from which rows in that table originate.

Search for data sources (nodes), by entering search criteria in to the search field at the top of the page. You can see hide tables from the graph by selecting the Show only selected notes checkbox.

Note

To reset the graph, click Reset graph on the top of the page.

Change the graph settings by clicking on the Graph Setting panel to open it on the right-side of the page. Use the layout options to change the color theme, graph direction, node width, vertical spacing, and horizontal spacing for the graph. You can reset the graph settings by clicking Reset on the Graph Settings panel. To close the panel click on the arrows at the top of the panel.

Tip

Use the view options to zoom in and out on the nodes by clicking the plus sign to zoom in and the minus sign to zoom out. You can also reset the view by clicking the box option and lock and unlock the graph by clicking the lock option.

To explore data lineage

1. From the Customer 360 page, open the Databases tab.

2. Choose a database, and then from the    menu, select Data lineage.

   This opens the Data lineage page.

Explore details

The Details view in the Data Explorer shows summary data about the table, along with information about which source tables were used to build it.

To view database details

1. From the Customer 360 page, open the Databases tab.

2. Choose a database, and then from the    menu, select Data Explorer.

   This opens the Data Explorer page.

3. Click the name of a table.

4. Click the Details tab at the top of the table.

5. When finished browsing the table details, click Close.

Explore example data

The Examples view in the Data Explorer shows actual data for a randomly selected set of rows in the data table.

Note

Users with restricted access to PII will not see data for PII-restricted columns, but will see data for all other columns.

Cardinality vs. uniqueness

Cardinality is a measure of how many unique values are present in data. A higher cardinality indicates a larger percentage of unique values, whereas a lower cardinality indicates a higher percentage of repeat values.

Uniqueness divides the number of unique values—cardinality—by the number of rows in a table.

Use cardinality and uniqueness to help guide the creation of well-behaved JOIN operations when authoring SQL queries.

• Avoid using JOIN operations when columns have lower cardinality. The high frequency of duplicate values will result in a row for every possible match.

• Columns with low uniqueness values as keys on both sides of a JOIN operation will run more slowly and is less likely to return the desired results.

• Empty fields (i.e. NULL values) are counted as duplicates, i.e. “not unique”. For example: a field with 90% completion and 90% uniqueness has different values for each of the non-empty rows.

Completion percentages

Completion is the percentage of non-NULL values within a column.

To view example data

1. From the Customer 360 page, open the Databases tab.

2. Choose a database, and then from the    menu, select Data Explorer.

   This opens the Data Explorer page.

3. Click the name of a table.

4. Click the Examples tab at the top of the table.

5. When finished browsing example data, click Close.

Explore table schema

The Schemas view in the Data Explorer displays information about each column in the table, along with an example, and information about completion, uniqueness, and cardinality.

To view database table schemas

1. From the Customer 360 page, open the Databases tab.

2. Choose a database, and then from the    menu, select Data Explorer.

   This opens the Data Explorer page.

3. Click the name of a table.

4. Click the Schema tab at the top of the table.

5. When finished browsing the table schema, click Close.

Export database

A database may be configured to export one (or more) tables (or even the entire database) from Amperity. Each database export must be assigned a unique name, and then is configured to select one (or more) tables to be included in the export. A database export must be associated with a configured destination and must be added to an orchestration.

Hide database table

A table may be hidden from users when they access the Data Explorer or Queries page.

Important

This setting does not prevent users from directly querying the table in the Queries page by referencing it by name.

To hide a table from users

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode.

3. Open a table, and then click Next to move to the second step in the table editor.

4. Under Advanced Settings, expand Visibility and Access.

5. Select the box next to Hide in Data Explorer and Queries page.

6. Click Activate.

Mark columns as PII

Columns that contain PII—names (first, last, and full), addresses, phone numbers, email addresses, birthdates, gender, and other profile details—should be marked for all database tables.

What is restricted PII access?

Users of Amperity who are assigned the AmpIQ User and/or Amp360 User policies along with the Restrict PII access policy option are prevented from viewing PII when that data was marked as PII in the database table.

When the PII checkbox is selected, the following locations will not show PII values to users who do not have permission to view PII data:

• The Examples page in the Data Explorer.

• Data that is returned by a query in the Queries page.

• Data that is returned by a segment in the Segments page.

When PII data is hidden, users are shown the following message:

Some personally identifiable information has been redacted from these results.

To mark columns as PII

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode.

3. Open a table, and then click Next to move to the second step in the table editor.

4. For each field that contains PII, verify that the box in the PII column is selected.

   Amperity automatically selects the PII checkbox for columns that were tagged with profile (PII) semantics. Verify that all columns associated with PII have the checkbox selected in the PII column.

5. Activate the table. Restricted access to PII will be updated the next time this database table is refreshed.

Run database

Amperity supports a variety of run options for each database your brand adds to Amperity. The primary customer 360 database may be run by clicking the Run link on the Profiles tab of the Customer 360 page. Additional databases may be run after selecting the Run option from that database’s    menu.

Individual databases have the following run options:

• Express refresh

• Full refresh

• Normal refresh

• Sequentially

• Stop

Express refresh

An express refresh will only update database tables and custom domain tables with new domain data or table definitions. This is the fastest option and is the recommended option for testing incremental changes.

Note

When a database is run, any custom domain table that has changed is run first, and then Stitch will run if any of those custom domain tables are configured for Stitch. If there are no changes to custom domain tables or if custom domain tables have changed that are not configured for Stitch, Stitch will not run.

To run a database with express refresh

1. From the Customer 360 page, open the Databases tab.

2. Open the menu for the database you want to run.

3. Select Run. The Run <Database> dialog box opens.

4. Under Run Options, select Express.

5. Under Databases to Run, select one (or more) databases to be run.

6. Click Run.

Full refresh

A full refresh will update all tables, including custom domain tables. This is the slowest option and is best used for estimating runtime performance.

Note

When a database is run, any custom domain table that has changed is run first, and then Stitch will run if any of those custom domain tables are configured for Stitch. If there are no changes to custom domain tables or if custom domain tables have changed that are not configured for Stitch, Stitch will not run.

To run a database with full refresh

1. From the Customer 360 page, open the Databases tab.

2. Open the menu for the database you want to run.

3. Select Run. The Run <Database> dialog box opens.

4. Under Run Options, select Full Refresh.

5. Under Databases to Run, select one (or more) databases to be run.

6. Click Run.

Normal refresh

Any table with new data, new table definitions, or time-dependent clauses will be refreshed. A normal refresh is the default option.

Note

When a database is run, any custom domain table that has changed is run first, and then Stitch will run if any of those custom domain tables are configured for Stitch. If there are no changes to custom domain tables or if custom domain tables have changed that are not configured for Stitch, Stitch will not run.

Time-dependent clauses include any query that uses the CURRENT_DATE(), CURRENT_TIMESTAMP(), UNIX_TIMESTAMP(), or RAND() functions.

To run a database with normal refresh

1. From the Customer 360 page, open the Databases tab.

2. Open the menu for the database you want to run.

3. Select Run. The Run <Database> dialog box opens.

4. Under Run Options, select Normal.

5. Under Databases to Run, select one (or more) databases to be run.

6. Click Run.

Sequentially

Run tables sequentially in the selected databases, rather than in parallel, to help identify tables that may be causing issues in your database.

Note

When a database is run, the system computes the tables in parallel by default. If you choose the option to run tables sequentially, this may increase the duration of the database run and should be used for debugging purposes only.

Run tables sequentially in the selected databases to do the following:

• Identify a specific table that is causing issues in your database.

• Optimize resource capacity.

• Review individual table run times to identify issues.

Note

When you run a database in this mode, the duration of the database run may increase substantially.

To run tables sequentially

1. From the Customer 360 page, open the Databases tab.

2. Open the menu for the database you want to run.

3. Select Run. The Run <Database> dialog box opens.

4. At the bottom of the dialog box, expand the Advanced Options section.

5. Select the Disable parallel table execution checkbox to apply this setting to the current database run.

6. Click Run.

Stop

You can stop a database that is running from the Workflows page.

To stop running a database

1. Open the Workflows page.

2. In the list of workflows, find the workflow for the database that is running.

3. From the    menu, select Stop workflow.

Search core tables

Use the search box to filter the list of standard core tables to match the string that is typed in the search box. The list of standard core tables automatically filters the list as the string is typed.

Set validation rules

A field in a database table may be flagged as required, as unique, or as both required and unique. These flags are validated by Amperity. When the validation conditions are not met a warning is raised.

Use flags to help ensure that data within Amperity remains healthy and to help ensure that downstream workflows are built on top of the correct data. Database field semantics are preceded by a db/ in the drop-down menu for semantics in the Database Editor.

Warning

Validation warnings appear in the Notifications pane as part of the notification for a database update. Each validation warning specifies the table name and the field name that failed validation.

To set validation rules

1. From the Customer 360 page, open the Databases tab.

2. Open a database in Edit mode.

3. Open a table, and then click Next to move to the second step in the table editor.

4. Select the combination of validation rules for each field.

   columnName	columnName
   db/unique	A field that is assigned the unique semantic requires every value for that field within the same table to be unique. Fields with NULL values are ignored by validation, but all other values, including zero-length strings, must pass. For a field that is unique, apply the db/unique semantic tag.
   db/required	A field that is assigned the required semantic requires every value for that field within the same table to have a non-NULL value, but does not require values to be unique. NULL values will cause an error during validation. All other values, including zero-length strings, will pass validation. For a field that is required, apply the db/required semantic tag.
   db/unique AND db/required	A field may be assigned the db/required and db/unique semantics. Use this only for fields that must be present and unique, such as for the Amperity ID. Some fields, such as amperity_id, are both unique and required. Apply both database semantic tags to these fields. Most fields do not require any validation rules.

5. Click Save.

View all databases

In addition to the primary customer 360 database, the Customer 360 page may contain additional databases. The Databases tab on the Customer 360 page lists all of the databases that have been created, including both active and draft states.

Other databases may be created to support any desired use case. Each database has a specific schema (i.e. collection of tables and attributes). This is called a data model. The data model and individual database tables Amperity provides should make data easy to understand and explore for its specific use case and client.

Note

Only databases in an Active state may be run against stitched data.

View core tables

Core tables are available from the Core tables tab on the Customer 360 page.

View database

From the Customer 360 page, under All Databases, open the menu for the database you want to view, select View. The Database Viewer page opens.

View permissions

Access to databases can be configured to allow only administrators, users who belong to a custom resource group, or everyone.

To view the configured permissions for a database

1. From the Customer 360 page, open the Databases tab.

2. Open the    menu for a database, and then select Permissions.

   The Permissions window appears with details about how this database is configured to allow access to users in your tenant.

View recent activity

Notifications for databases that run in the Customer 360 page appear after Amperity has processed data for that database. Notifications typically indicate successful outcomes. Less often, notifications contain details for non-successful outcomes, such as failures related to upstream or downstream processes.

To view recent activity

If a notification is about a non-successful outcome, the details for why and what happened can be found in the notification itself. Click More to view the full notification. Click View Workflow to open the workflow in the Workflows page.

In some cases viewing the log files may be helpful. In many cases, fix the root cause of the non-successful outcome, and then rerun the process manually. The Workflows page will provide a set of workflow actions that you can initiate directly.

View run history

You can view the run history for any database in the Customer 360 page.

To view the run history of a database

1. From the Customer 360 page, open the Databases tab.

2. Open the    menu for a database, and then select View run history.

   The Run History window appears with details about the run history of the database.

   Tip

   You can view the workflow information associated with the database by clicking on View Workflow on the top-right corner of the Run History window.

View SQL for core table

View the SQL for a standard core table to understand how the table was built.

To view the SQL for core tables

1. From the Customer 360 page, open the Core tables tab.

2. From the list of custom core tables, open the menu for the core table you want to edit, select View (for custom core tables) or View SQL for standard core tables.

3. This opens the Custom Core Table editor for custom core tables or the View SQL dialog box for standard core tables.