SFTP integration and cloud file transfer with Amperity
Move customer data files between Amperity and SFTP, Amazon S3, Azure Blob Storage, or Google Cloud Storage. Configure secure access, define the file schema, and automate recurring transfers.
Request a demoSee SFTP docsConnect file-based customer data to Amperity
Files from any system
Ingest files from systems that do not connect directly to Amperity.
Automated deliveries
Automate recurring customer data deliveries from cloud storage.
Standardized files
Standardize incoming files with defined schemas and semantic tags.
Protected files
Protect sensitive files with connector-specific access controls and encryption.
Cloud storage connection at a glance
Capability | Details |
|---|---|
Direction | Inbound and outbound, depending on connector |
Methods | SFTP, Amazon S3, Azure Blob Storage, and Google Cloud Storage |
Data movement | Files are transferred between the configured location and Amperity |
Workflow | One-time, manual, or scheduled file workflows |
Common inbound formats | Avro, Parquet, CSV, DSV, JSON, NDJSON, PSV, TSV, and XML; outbound options vary by destination |
Security | Connector-specific credentials and access controls; PGP options vary by workflow |
Load behavior | Upsert or truncate-and-upsert for supported inbound feeds |
Schema | Each inbound file requires a defined feed schema |
What teams do with cloud storage and SFTP
Bring legacy and third-party files into Amperity
Ingest scheduled file drops from legacy applications, agencies, partners, or other systems without a direct connector. Amperity validates the files and maps their fields into domain tables for downstream customer-data workflows.
Load large customer datasets from cloud storage
Use Amazon S3, Azure Blob Storage, or Google Cloud Storage for recurring customer data deliveries. Supported file formats include common delimited, structured, and columnar formats such as CSV, JSON, Avro, and Parquet.
Prepare files for identity resolution
Define primary keys, semantic tags, update fields, and schema rules for each inbound feed. Customer records can then be made available to Amperity identity resolution and incorporated into unified profiles.
Deliver governed data to downstream systems
Send prepared customer datasets to supported storage locations for analytics, archival, or downstream processing. Connector-specific permissions and encryption controls help teams govern how files are accessed and transferred.
Cloud storage and SFTP FAQs
Put file-based customer data to work
Connect SFTP and cloud storage to Amperity so customer files can support identity resolution, useful attributes, and governed datasets for analytics and activation.
Request a demo