AWS S3
Overview
Section titled “Overview”Leads that Signals receives are written as files into an Amazon S3 bucket you own. Each export produces a timestamped object in the bucket and path you nominate.
Supported sources
Section titled “Supported sources”Sources supported by AWS S3
| Category | Supported |
|---|---|
| Lead generation |
Prerequisites
Section titled “Prerequisites”- An S3 bucket that already exists. Signals writes into a bucket you have created; it does not create one.
- An active access key pair for a user with write permission to that bucket.
Authentication
Section titled “Authentication”In Studio, open Destinations, find the Files category, and click the AWS S3 tile. This connector authenticates with keys you add manually, so there is no sign-in screen.
Configuration
Section titled “Configuration”Integration type and connection
Section titled “Integration type and connection”Select the Integration Type, which is the lead generation source the leads come from. The options are Meta Lead Ads, Snapchat Lead Generation Ads, TikTok Lead Ads, LinkedIn Lead Ads and Google Forms. Then select the lead ads connection name you want to deliver from, and give the instance a name. The instance name is yours to choose and does not have to match anything.
Export frequency
Section titled “Export frequency”Set the Export Frequency, which can be Real-time, 1 hour, 3 hours or 1 day, then click Next.
Credentials and file location
Section titled “Credentials and file location”Enter the following, then click Validate Credentials.
| Field | What it is | Where to find it |
|---|---|---|
| S3 Bucket Name | Unique identifier for your storage container. | AWS console, S3, Buckets. |
| S3 Bucket Access Key | Access key for authentication. | AWS console, IAM, Users, then Security credentials for the user. |
| S3 Bucket Secret | Secret key for authentication. | Shown once when the access key is created. If it is lost, create a new key pair. |
| Relative Path to Data Folder | Path or prefix where data files should be stored. | Your own convention. |
Once validated, the file path and file name are displayed so you can confirm where exports will land. Click Finish.
Studio creates the folder structure for you. A folder named Datahash is created inside the path you give, or at the root if you leave the path blank, and inside it a subfolder named after the lead ads connection. Each export is written there with a timestamp in the filename.
Manage instance
Section titled “Manage instance”One connection writes one source to one bucket and path. To deliver a second source, or into a second location, add another instance from Manage Connections. To change an existing one, click the connection name in Manage Connections, click the edit icon in the top right, update the values, click Validate Credentials, confirm the updated file path and click Finish.
Data & identifiers
Section titled “Data & identifiers”Leads are delivered as submitted. Personal data is not hashed on this destination, because the system receiving it is your own and the point is that people and applications can read it.
Once an object lands in your bucket, encryption, retention, lifecycle and access are governed by your bucket configuration and IAM policies, not by Signals.
Which fields arrive is decided by the lead form on the connected source, so a field you need that is not appearing has to be added there.
Best practices
Section titled “Best practices”- When the access key is rotated, update the instance with the new key. Delivery stops the moment the old key is deactivated.
- Agree the file contents with whoever consumes them, and tell them before the lead form changes.
Troubleshooting & FAQ
Section titled “Troubleshooting & FAQ”Validate Credentials fails. Check the key is active, the bucket name is right, and that the bucket policy does not deny the write. A bucket policy denial overrides a permissive user policy and is the easiest one to miss.
Access denied on an encrypted bucket. The bucket enforces server-side encryption with a managed key, and the key policy does not allow this user to use it. Bucket permissions alone are not enough.
No files are appearing. Confirm the path on the connection is the path you are looking in, then confirm the source has produced leads. An export with no leads does not write an object.
The file will not parse downstream. A field value contains a line break or the delimiter, usually a free-text answer. Clean it at the form.
Delivery stopped without any configuration change. Almost always a rotated or deactivated access key.