Links

S3

Connect Vitally to S3 to sync account and user data from CSV files in an S3 bucket.

Step 1 - Connect

We'll need these values to connect to your S3 data:
  • Bucket Name: The S3 Bucket you would like to access.
  • Prefix: The sub-folder you would like to access (optional).
  • Region: Your AWS region.
  • Access Key ID: Username for access to a bucket.
  • Access Key Secret: Password for access to a bucket.

Step 2 - Configure

Map files to Accounts, Users, Organizations, & Events.

Sync and File Selection

After you're connected, the next step to syncing Accounts & Organizations, Users, Events, and NPS is to identify the files you would like to pull into Vitally on each sync.
We will only sync the first 1000 files and they will be selected in alphabetic order
The initial steps are the same for all object types. Simply toggle the sync "on" and either enter a regular expression to choose specifc files from your bucket or enter .* to sync all files.

Accounts & Organizations

  1. 1.
    Choose the column that contatins the external ID used for Accounts in Vitally.
  1. 2.
    Select if you would like to Create Accounts from S3 data or that are not representing in Vitally or only Update exsisting accounts in Vitally.
3. Define the column that contains the name of the Account.
4. (Optional) Select the column that references the Organization ID the Account belongs to (only applicable in the Account setup flow when Organizations is enabled).
Once you have configured these settings we will pull in the fields as traits. No additional field mapping is required.

Users

  1. 1.
    Choose the column that contatins the external ID used for Users in Vitally.
2. Select if you would like to Create Users from S3 data or that are not representing in Vitally or only Update exsisting Users in Vitally.
3 & 4. Select the Account details to associate Users to Accounts.
5 & 6. Define additional identifying details for the User.
7. (Optional) Select the column that references the Organization ID the User belongs to (only applicable in the Account setup flow when Organizations is enabled).
Once you have configured these settings we will pull in the fields as traits. No additional field mapping is required.

NPS

  1. 1.
    Define the column contains the Unique ID of the NPS response.
2. Define the column that contains the external ID of the User who submitted the response.
3-5. Define the columns that containt the NPS score, Feedback Provided, and Timestamp of the repsonse date.
Any additional fields in the file will be ignored and will not be pulled into Vitally.

Tracks

1-3. Choose the ID of the object you want to relate the Event to. If the Event is for a user, enter a column to map for User ID, etc. Only one of these three should be selected.
4. Choose the column mapped to the Message ID. This should be unique per event.
5. Choose the column mapped to the timestamp of the event.
6. Choose the column mapped to the type of event (like User Deactivated).

Step 3 - Sync

Select how often you would like to sync data from S3 into Vitally. You can sync data every 6, 12, or 24 hours. After updating the sync scheudle we will run an intial sync and each subsequent one will run with the chosen internval.
Last modified 1mo ago