LogoLogo
WebsiteDocumentationChangelogStatusTerms
  • Getting Started
    • Overview
    • FAQs
    • Reference
      • Identifier Types
      • Identifier Profiles
      • Identity Clusters
      • Identity Resolution
      • Regular Expressions
      • Tabular Data Schema
      • Advanced Query Interface
      • IP Allowlisting
    • Global Data Regulations
  • Data
    • Sources
      • Amazon S3
      • API Source
      • Azure Blob Storage
      • BigQuery
      • Databricks
      • File Upload
      • Google Cloud Storage
      • Mailchimp
      • SDK Sources
        • Android SDK
        • iOS SDK
        • JavaScript SDK
      • SendGrid
      • Shopify
      • Snowflake
    • Data Configuration
      • Custom Identifiers
      • Traits
      • Events
      • Labels
  • Identity
    • EIDs Switchboard
  • Audiences
    • Audiences
      • Audience Builder
      • Insights
      • Activation
        • Real-Time Targeting
        • Google Ad Manager
        • Permutive
      • Exports
        • Metadata file
    • Destinations
      • Amazon DSP
      • Amazon S3
      • Azure Blob Storage
      • Campaign Manager 360
      • Display & Video 360
      • Google Ads
      • Google Cloud Storage (GCS)
      • Meta Ads
      • The Trade Desk
      • TikTok
      • Yahoo! Japan Ads
  • collaborate
    • Clean Rooms
      • Insights Clean Rooms
      • Activation Clean Rooms
      • Augmentation Clean Rooms
      • Prospecting Clean Rooms
    • Partnerships
      • Flash Partners
        • Optable Flash Node
        • AWS Connector
        • Snowflake Connector
      • Enterprise Partners
      • Flash Partner Settings
  • Differential Privacy
  • Admin
    • General
    • Accounts
      • Managing User Accounts
      • Roles
        • Permissions
      • Authentication
    • Real-Time API
    • Data Subject Requests
  • Profile Settings
    • Notifications
  • Guides
    • AWS Connector: Guides
      • Enterprise DCN
      • AWS Connector
    • Snowflake Connector: Guide
    • Optable CLI
    • Data Warehouse Exports
      • Google BigQuery
      • Snowflake
  • Announcements
    • Deprecation Notices
      • Q1 2025: Deprecation of Exports & Introduction of Syncs
      • Feb 21st, 2024: Removal of regex_allowed_http_origins
      • Dec 8th, 2022: Exports to Export Configurations
      • Deprecated uses in the CLI
Powered by GitBook
On this page
  • Formatting Your XLSX, CSV or TSV File
  • Formatting Your JSON File
  • Uploading a File as a Data Source
  • Creating Your File Upload Source via CLI
  • Editing Your File Upload Source via CLI

Was this helpful?

  1. Data
  2. Sources

File Upload

Audiences specified by a list of identifiers with their associated traits

Last updated 1 month ago

Was this helpful?

The file upload source enables you to upload CSV , TSV or JSON files containing emails, phone numbers, and other identifiers as well as their respective traits. In order for your first-party dataset to be properly ingested in your DCN, you must first ensure that it respects the specified format.

Formatting Your XLSX, CSV or TSV File

In order for your XLSX, CSV or TSV to be successfully ingested into your DCN, it must follow an established schema which is outlined within our section. Once your data has been properly organized and the columns follow the proper schema, you will be able to upload your file to your node.

File Upload also supports the above files in GZIP format.

Formatting Your JSON File

Your JSON object must follow the standardized ID profile detailed on the section. Once the JSON object is formatted correctly, you will be able to upload it to your DCN, and all of your identifiers will be ingested alongside their scope and traits.

Uploading a File as a Data Source

Once your file is ready, you can upload your file as a source by going to Data > Sources. Within the source selection page, select "File Upload" and proceed to name your source.

Every subsequent file that you upload, within a previously set up source, will replace the previous file and will be added to the source history. This can be used either as a reference or to check the status of the processing of your source.

Creating Your File Upload Source via CLI

optable-cli source create file --file=<path>

For example, if the path to your file is /my/path/file.dat, you can create an audience with it as follows:

optable-cli source create file "new file upload" --file=/my/path/file.dat

A JSON description of the newly created dataset audience is returned on success.

Editing Your File Upload Source via CLI

To update your file upload source, run the following command:

optable-cli source ingest file <id> <file>

By default an audience will be automatically created using the specified source name, you can use this audience for , , or .

To create a file upload source, you need to have a file with type-prefixed identifiers which is either an , , or file with proper formatting. You can create the source using the by running the following command:

matching
activation
exporting it to a destination
CLI
XLSX
CSV
TSV
JSON
tabular data schema
loading ID profiles
File Upload source creation