Upload People and Companies to Primer via S3 (Beta)
Upload people or company CSV files to a secure, Primer-provided Amazon S3 location.
Primer’s S3 ingestion beta is designed for scheduled exports, data warehouse unloads, and large recurring data deliveries. Each uploaded CSV becomes an imported dataset that you can use when building audiences in Primer.
Beta availability
S3 ingestion is currently available as a beta feature. Contact your Primer representative or support@sayprimer.com to request access and receive your upload credentials.
Choose between S3 and API ingestion
Primer supports two beta options for programmatically importing data:
Choose
Best for
Update behavior
S3 ingestion
Scheduled exports, warehouse unloads, and large recurring files
Each file replaces the complete dataset associated with its filename.
API ingestion
Keeping individual records synchronized as they change
Each request updates only the records included in that request.
Use S3 when your source system regularly generates a complete snapshot. For incremental record updates, see Push People and Companies to Primer via API.
How S3 ingestion works
You upload files containing either people or companies to a dedicated S3 path provided by Primer. You can set this up easily from your data warehouse or ETL tool
Export Data from Snowflake to Primer via S3Export Data from Fivetran to Primer via S3Export Data from Hightouch to Primer via S3Primer processes each file as a snapshot:
The filename becomes the dataset name in Primer.
Uploading the same filename again replaces that dataset.
Rows missing from the new file are removed from the dataset.
Uploading a new filename creates a separate dataset.
After processing, the dataset appears under CSV Imports in Primer and can be used when building audiences.
Important: An S3 upload is a complete replacement, not an incremental update. Every upload should contain all rows you want the dataset to retain.
Before you begin
Primer will provide:
An AWS role ARN to assume when uploading files
A dedicated S3 access point and upload path
Separate folder paths for people and company CSVs
Credentials limited to writing to your organization’s assigned path
Uploads must use the S3 access point provided by Primer. Do not upload directly to the underlying bucket.
Keep your access credentials private. Do not place them in public repositories, client-side applications, or shared documentation.
Folder layout
Primer will give you a dedicated prefix with two supported folders:
Upload:
Person CSVs to
<prefix>/datasets/people/Company CSVs to
<prefix>/datasets/companies/
Do not place files outside these folders.
CSV requirements
Every file must:
Use CSV format
Include a header row
Contain either people or company records—not both
Be uploaded to the corresponding folder
Use Primer’s supported column names or column names agreed upon with your Primer representative
Extra columns, such as job title or phone number, are ignored and do not cause the import to fail.
Choose a filename strategy
The filename determines the dataset name in Primer.
Maintain one recurring dataset
Use the same filename for every upload:
Each new contacts.csv replaces the existing contacts.csv dataset. Rows that were present in the previous file but are missing from the new file are removed.
This is the recommended approach when maintaining a current snapshot of a source system.
Create a new dataset for every upload
Use a different filename each time:
Each filename creates a separate dataset that remains in Primer. Previous datasets are not automatically replaced or removed.
Plan your filename strategy before the first upload. Renaming a file later creates a new dataset instead of updating the dataset associated with the original filename.
Supported people fields
Upload people files to <prefix>/datasets/people/.
Field
Recommended header
Also accepted
First name
First Name
first_name, firstName, Given Name
Last name
Last Name
last_name, lastName, Surname
Email
Work Email, work_email, workEmail
LinkedIn profile
Person Linkedin Url
LinkedIn URL, linkedin_url
Company name
Company Name
company_name, Account Name
Company domain
Company Domain
company_domain, Website, Domain
Country
Country
country
State or region
State
state, Province, Region
City
City
city, Town
For the best matching results, include an email address and LinkedIn profile URL whenever available.
Supported company fields
Upload company files to <prefix>/datasets/companies/.
Field
Recommended header
Also accepted
Company name
Company Name
company_name, Account Name
Company domain
Company Domain
company_domain, Website, Domain
LinkedIn company page
LinkedIn URL
linkedin_url, Linkedin
Country
Country
country
State or region
State
state, Province, Region
City
City
city, Town
For the best matching results, include a company domain, LinkedIn company page, or both. Companies with neither value may not match successfully.
Example people file
Example company file
Last updated