ClientSuccess can support the import of aggregate Client, Contact, Revenue, and NPS data of your customers from "flat file".
The intended use case for a flat file import is to support Customers that are not able to integrate via the native integrations or push data via the General API.
The frequency of ingesting this file is approximately every hour, though may not be at the exact same time every hour.
Required Steps from Customer side
- Folder has been set up and is available via S3, Google Cloud Files, or SFTP
- Username/password has been provided (if SFTP) to email@example.com
- Folder that will be used has been created and is in place
- At least 1 production-ready sample file is in place - this file could represent real data or a few events for a ‘test’ event that can be discarded later
- File has been validated for format (Date format including time, Org ID and Org Name are required. When applicable, user fields are required in header but can be blank, value is provided (not empty) for at least 1 event.
- Metric or Custom Field columns must have a numeric value i.e. "0" and cannot be left blank. Do not send files with empty metric columns. This will cause the file to fail to process.
- ClientSuccess support will then respond to validate that file ingestion process was successfully configured and initial file was successfully ingested.
"If the S3 bucket you are providing uses custom encryption keys additional configuration is required. Please reference this article (https://aws.amazon.com/premiumsupport/knowledge-center/cross-account-access-denied-error-s3/) and provide the ARN for the encryption key to your CSM or support when requesting setup."
The required file format is a CSV with the fields identified in the example below. It is expected that proper escaping of string literals will be applied and that the first row is always the column header.
1.) Please provide empty columns for user columns where user-level information is not in use with no values/blanks. Do not provide empty strings ("").
2.) Please ensure columns are listed in proper order/sequence starting with event.time, org.id, etc. as described below.
3.) File size is limited to 50,000 events. Anything exceeding this amount should be separated into different files.
*Note: An event does NOT represent a single row of data in the flat file. Each row could (and usually do) contain more than one event. Blank cells do not count as an event.
It is recommended that files be named according to a convention that includes the date that the file contains data for.
Note: This example is referring to the date that the flat file would be sent. It does not indicated that a daily flat file should be submitted. We suggest a cadence of no more than weekly if you are going to submit a flat file for usage tracking.
Note: S3 server is needed only if you are planning to upload a recurring flat file for regular usage tracking
1. Provide access to the clientsuccess-usage-bot IAM user via ARN.
The ClientSuccess ARN is: arn:aws:iam::990004405076:user/clientsuccess-aws-bot
2. Send your S3 bucket policy to support.
Below is an example of what your S3 bucket policy may look like, and what we need you to provide to us to configure the auto-ingestion process of your usage flat file from your S3 bucket:
"arn:aws:s3:::<your bucket name here>",
"arn:aws:s3:::<your bucket name here>/*"
Google Cloud Storage
Provide access to the clientsuccess-api-bot IAM user to your bucket.
Secured FTP folder
Provide access with a specific user credentials to ClientSuccess for auto ingestion of the flat file.
Note: Files can be automatically pulled from the SFTP server 4 to 6 times a day, or whenever the file is successfully updated.
For additional questions, please contact firstname.lastname@example.org.