Clarisights provides multiple ways of importing CSV files - 

  1. Primary Data Sources - Custom Advertising (CADV), or POD

  2. Secondary Data Source - Custom Analytics (CA)

Data can be uploaded into these sources, in any one of the following modes - 

  1. Ad-hoc CSV uploads

  2. CSV attachment in e-mails

  3. CSV through URL

  4. CSV in Amazon S3 bucket

  5. Google BigQuery table

  6. Google Sheets

In the case of Google Sheets and Google BigQuery table, Clarisights generates the CSV from these sources, so we are able to automatically ensure that the CSVs are compliant with the standard format.

However, in the rest of the modes, the system which is exporting the CSV and uploading it to Clarisights needs to ensure that the CSV is RFC-4180 compliant. Sending files that comply with RFC standards ensures that Clarisights can process these files without issues.

A few important points to note that will help your CSV be compliant with RFC - 

  1. The separator should be a comma and not a semicolon.

  2. If even one field contains commas, then every field needs to be double-quoted.

  3. A double-quote that appears inside a field must be preceded with another double quote.

If you'd like to validate your CSV to know whether it is RFC-compliant or not, we recommend using this tool - CSV Lint.

Now that you know which kinds of CSVs can be processed in Clarisights, learn more on how custom POD channels work.

Did this answer your question?