DOCUMENTATION
Sign In

Get access to My SAS, trials, communities and more.

Data Dictionary
 

Analytical Base Tables

About Analytical Base Tables

Analytical base tables (ABTs) contain data about user behavior that is used in analytical reports. The ABT_ATTRIBUTION table is used by SAS Customer Intelligence 360 as a source for attribution modeling. Each row in the attribution table represents one customer interaction, so you might see multiple rows for the same person. Currently, the table shows two types of data: origination data (one row per visit) and conversion events that are associated with data views.

You can download the table and take one of these actions:

  • Run the data against your own analytical models.
  • Append any other data you have, such as on-premises data, to the table for a more robust set of data.
  • Review the data that SAS Customer Intelligence 360 uses as a source for attribution modeling.

These tables can be downloaded using the SAS Customer Intelligence 360 download API. Use the following information when downloading ABTs:

  • In your API call, use the dbtReport endpoint to download these tables. For more information, see Download Discover Base Tables (DBTs) and Analytical Base Tables (ABTs) in SAS Customer Intelligence 360: Administration Guide or Downloading Data Tables with the REST API in SAS Customer Intelligence 360: Administration Guide.
  • Only completed sessions are available for download. Hourly data is not available for ABTs because attribution data is available only on the 23rd hour of a given day. To include a specific day of data, include the 23rd hour of that day.
  • Make sure that you review the category and schema version for the tables that you want to download.
    TipTo download all tables that you have access to, use the ALL category and the most recent schema version (23).
Note: In some situations, there might be a mismatch between the contents of the tables and the schema version:
  • The downloaded data might contain more columns than are documented in the Help Center or in the schema files. These columns might have been introduced for internal consumption already and will be added to a future version of the schema.

    The same scenario can happen when you are not using the most recent schema. The data that you download always uses the columns from the latest schema, but you might have requested a schema version that has fewer columns.

  • A schema might add columns to tables, but the columns are not populated with data until a later release of SAS Customer Intelligence 360. For example, a table in the current schema might have nine columns, but data records populate only seven columns. When columns are added but not yet populated with data, you can ignore these columns when you process the data.

    When SAS Customer Intelligence 360 is updated to populate these columns, you might need to wait 2–3 days before the data is populated in the downloaded tables.

To mitigate any issues, configure your ETL processes to allow for the physical files to have more columns than what is described in the JSON schema and the documentation.

See Also

Prerequisites for Enabling Attribution Data

Attribution data depends on data views. Data views track the conversions and common attributes for a collection of events. Those events typically track one or more goals that you have for your organization. For example, when a person purchases a product on your site or subscribes to a newsletter, they might be completing one of your organization’s goals. A conversion occurs when a person completes one of the goals.

Attribution analysis also requires information about the set of actions that a person takes before converting, known as a customer journey. The data about customer journeys is tracked in traffic sources. For example, traffic sources can tell you whether a visitor went directly to a website or arrived there from a search result via a search engine, or by clicking a link in an email or clicking a banner.

To enable attribution data to be collected, complete these prerequisites to enable data:

  1. Create data views and publish them. For more information, see these topics:
    Note: The data views must have conversions before attribution data is collected.
  2. Define traffic sources. Navigate to Administration Administrationthen selectTasks. Click Traffic Sources in Digital. For more information, see Traffic Sources in SAS Customer Intelligence 360: Administration Guide.

ABT_ATTRIBUTION (Partitioned)

ABT_ATTRIBUTION

Column Name

Data Type

Column Label

Description

Schema First Introduced

identity_id

VARCHAR(36)

Identity ID

The information that SAS Customer Intelligence 360 uses to identify a person. This information must match the identity_id that appears in other data, such as the VISIT_DETAILS table.

For more information about identities, see Overview of Identities in SAS Customer Intelligence 360 in SAS Customer Intelligence 360: Administration Guide.

3

interaction_type

VARCHAR(15)

Interaction type

Used by attribution analysis to determine how to interpret this row of data. Possible values are Origination, Conversion, and Task.

3

interaction_id Primary key

VARCHAR(36)

Interaction ID

Identifies which instances of an event receives credit in attribution analysis. When the value of interaction_type is Conversion, this value matches the ID of the data view. When the value of interaction_type is Origination, this value matches the session ID.

3

interaction

VARCHAR(260)

Interaction

Identifies the interaction. The value depends on the interaction_type. For example, if the interaction_type is Task, this value is set to the task name. Alternatively, if the interaction_type is Origination, this value matches the origination_nm value in the VISIT_DETAILS table.

3

interaction_subtype

VARCHAR(100)

Interaction Subtype

Can be used to aggregate interactions that have the same interaction_type value. This value depends on the interaction_type. For example, if the interaction_type is Task, this value is set to the task name. Alternatively, if the interaction_type is Origination, this value matches the origination_type_nm value in the VISIT_DETAILS table.

3

interaction_dttm Primary key

VARCHAR(26)

Interaction Datetime

Specifies the event timestamp in this format: YYYY-MM-DD HH:MM:SS.SSS.

3

task_id

VARCHAR(36)

Task ID

Identifies the task for this interaction.

Note: This value is populated only when the value of interaction_type is Task.

3

conversion_value

INT(11)

Conversion Value

This value is used in attribution analysis. However, it is not displayed in the attribution.

Note: This value is populated only when interaction_type is Conversion. It has a value of 1.

3

interaction_cost

INT(11)

Interaction Cost

This column currently contains no value and is not used in any analysis.

3

load_id

VARCHAR(36)

Load ID

Identifies a specific page view instance.

Note: This value is populated only when interaction_type is Task.

3

creative_id

VARCHAR(36)

Creative ID

Identifies the creative that is displayed during this interaction.

Note: This value is populated only when interaction_type is Task.

3

Last updated: November 2, 2026