Sending Data to Totango via .csv Files

Overview

This document describes the elements needed for a full CSV integration method. For this example, we will send 3 files to Totango:

1. Accounts Data
1. Parent and Child Accounts
2. Product Accounts (holding account information as contract value, renewal date, etc)
2. User Data (user information as email, role, etc)
3. Usage Data (information on how users are using your product)

Accounts Data

Creating a CSV file for account data. Screenshot of sample below:

To upload account data into Totango use the following format, typically sourced from a report from your CRM.

The CSV file format should be:

AccountID, ParentID (must be present for product accounts) [ Account-Attribute-1, Account-Attribute-2, ... ]

Where:

• AccountID: Please see this article in regards to choosing and using AccountID in MultiProduct
• ParentID(optional): The account that the account being referenced is the child of. A product account should always have a parent.
• Account-Attribute-N: List of attributes you want to update for every account (if any).

The first row in the CSV file should be the header row containing the name of the attributes, followed by the actual data (there should be one account per CSV row, there should not be any duplicates)

User Data

Creating a CSV file for user data. Screenshot of sample below:

The CSV file format should be:

User id, AccountId, User-Attribute-1, User-Attribute-2, ...

• User id: The user's identity (email or any identity)
• For AccountID: Please see this article in regards to choosing and using AccountID in MultiProduct
• User-Attribute-N: List of attributes you want to update for every user (if any)

Special attributes:

• Contact - Add or remove the user to the contact widget. 
  • value = yes (lowercase) will add the user as a contact
  • value = no (lowercase) will remove the contact (and keep the user)
• Key Contact - set the user as a key contact on the account
  • value = yes (lowercase) will add the user as a key contact
  • value = no (lowercase) will set the user as a normal user (not key contact). 

The first row in the CSV file should be the header row containing the name of the attributes, followed by the actual data (one user per CSV row, each user MUST be associated to an Account, there should be no duplicates of account/user combinations)

Usage Data

Creating a CSV file for usage data. Screenshot of sample below:

The CSV file format should be:

User id, AccountId, Action, Module

• User id: The user's identity (email or any identity)
• AccountID: please see this article in regards to choosing and using AccountID in MultiProduct
• Action: Name of the activity the user performed
• Module: Name of the module the user performed
• Count: Optional (Number of times this line item occurred, max 10K, if you have more than 10K occurrences, simply split it into as many lines as needed.  If you have 30K, that's 3 lines each having 10K for the count)

The first row in the CSV file should be the header row containing the name of the fields, followed by the actual data (one user per CSV row)