Data Requirements for a List-Based Data Studio Configuration

The only required piece of data to get a Terminus Data Studio instance up-and-running is the Account data itself. If customers can provide a list of Accounts with the required fields, then the Terminus Technical Consultant team can create a Data Studio instance. Optional data can be provided, which will fill in the additional columns and reporting capabilities for Data Studio.

 

Data Ingestion Frequency

Terminus uploads any new CSV files for list-based organizations over the weekend. This process begins after Fridays at 5PM ET.

 

Object File Requirements

  • Each object must be contained within its own .csv file
    • The file name should reflect the object data it contains (i.e.,  Accounts.csv, Opportunities.csv, Campaigns.csv, etc.)
    • New uploads must include ALL the object data and not be limited to incremental uploads
  • Each object’s .csv file must contain the mandatory fields in the correct data type. For example, all account records must have an:
    • Account ID,
    • Account Name, and
    • Website
  • If your organization would like a particular global filter within the Data and Measurement Studios, that field data must be included in the respective object CSV file. This includes any custom fields your organization may need, such as Account Segment, Company Size, etc.
  • Each record’s Unique ID field must be consistent between data file uploads. For example, Account IDs must remain consistent for historical accounts when uploading new Account.csv files.
    • Salesforce → 18-Character ID
    • Dynamics365 → 36-Character ID
  • Each record ingested from the file will be treated as its own record. Terminus will not deduplicate this data after ingesting it into Data Studio.
  • Character Encoding should be UTF-8

 

Mandatory Object

Accounts

The required fields must be populated for every account record. Only recommended and custom fields may have NULL values within the CSV file.

  • Required Fields + Type
    • Account/Company ID → VARCHAR(36)
    • Account Name → VARCHAR(255)
    • Website → VARCHAR(255)

  • Recommended Fields + Type:
    • Owner ID → VARCHAR(36) *Required if sending User.csv
    • Owner Email → VARCHAR(255)
    • Owner Name → VARCHAR(255)
    • Last Activity → DATETIME
    • Parent Account ID → VARCHAR(36)
    • Account Type → VARCHAR(255)
    • Industry → VARCHAR(255)
    • Tier → VARCHAR(255)
    • Country → VARCHAR(255)
    • Region → VARCHAR(255)
    • Territory → VARCHAR(255)

*If your organization opts to import a Users.csv file, then an Account `Owner ID` is considered required and cannot be NULL for any account records.

 

Optional Objects that Provide Additional Value

All required fields must be populated, with only a few exceptions denoted by an asterisk (*). Only recommended and custom columns may be NULL.

Opportunities

  • Required Fields + Type:
    • Opportunity ID → VARCHAR(36)
    • Account ID → VARCHAR(36)
    • Name → VARCHAR(120)
    • Closed → CHAR(1)
    • Won → CHAR(1)
    • Created Date → DATETIME
    • Close Date → DATETIME  *Required if `Closed` = ‘t’

  • Recommended Fields + Type:
    • Amount → DECIMAL(12,4)
    • Stage → VARCHAR(40)
    • Opportunity Type  → VARCHAR(40)

Contacts

  • Required Fields + Type:
    • Contact ID → VARCHAR(36)
    • Full Name → VARCHAR(121)
    • Email → VARCHAR(80)
    • Account ID → VARCHAR(36)
    • Created Date → DATETIME

  • Recommended Fields + Type:
    • Title → VARCHAR(128)

Leads

  • Required Fields + Type:
    • Lead ID → VARCHAR(36)
    • Full Name → VARCHAR(121)
    • Email → VARCHAR(80)
    • Converted Account ID → VARCHAR(36)
    • Created Date → DATETIME

  • Recommended Fields + Type:
    • Converted Contact ID → VARCHAR(36) *Required if associated Contact record
    • Title → VARCHAR(128)
    • Company → VARCHAR(255)

Campaigns

  • Required Fields + Type:
    • Campaign ID → VARCHAR(36)
    • Campaign Name → VARCHAR(80)
    • Start Date → DATETIME
    • Created Date → DATETIME
    • Type → VARCHAR(40)

  • Recommended Fields + Type:
    • Parent Campaign ID → VARCHAR(36)


Campaign Responses (or Marketing Activities)

  • Required Fields + Type:
    • Response ID → VARCHAR(36)
    • Campaign ID → VARCHAR(36)
    • Lead ID → VARCHAR(36)
    • Contact ID → VARCHAR(36)
    • Responded → CHAR(1)
    • Response Date → DATETIME
    • Created Date → DATETIME

Sales Activities

  • Required Fields + Type:
    • Activity ID → VARCHAR(36)
    • User ID → VARCHAR(36)
    • Lead/Contact ID → VARCHAR(36)
    • Type → VARCHAR(40)
    • Created Date  → DATETIME
    • Subject → VARCHAR(255)

Users

  • Required Fields + Type:
    • User ID → VARCHAR(36)
    • Full Name → VARCHAR(121)
    • Email → VARCHAR(80)

 

Database Relationship Visual

image2.png

Was this article helpful?
1 out of 2 found this helpful

Comments

0 comments

Please sign in to leave a comment.