Acxiom

Deliver audience and customer data files to Acxiom via Amazon S3 for identity resolution, data enrichment, and audience activation. Zeotap exports model results, audience lists, or enriched profiles as CSV or JSONL files to an Acxiom-managed S3 bucket, where Acxiom processes them through their identity graph (AbiliTec/Real ID) and activates audiences across downstream channels.

Prerequisites

An Acxiom account with data onboarding enabled
An Acxiom-managed S3 bucket provisioned by your Acxiom representative
AWS access credentials (access key + secret key) with write permissions to the bucket
Bucket name and AWS region provided by Acxiom

Authentication

Acxiom data delivery uses AWS Access Keys to authenticate with the S3 bucket.

Contact your Acxiom representative to provision an S3 bucket for data delivery
Obtain the AWS Access Key ID and AWS Secret Access Key with write access to the bucket
Enter both credentials in Zeotap when configuring the destination

Required Permissions

The AWS credentials need the following IAM permissions on the Acxiom S3 bucket:

s3:ListBucket — required. Check bucket access. The connection test and the start-of-run check both issue a HeadBucket call, which AWS authorizes with s3:ListBucket
s3:PutObject — required. Upload data files, and write the temporary zero-byte write-check marker at the start of each sync run
s3:DeleteObject — recommended. Remove the write-check marker after each sync run. The cleanup is best-effort — without this permission the marker object is left behind, but syncs still succeed

Grant s3:ListBucket on the bucket ARN (arn:aws:s3:::your-bucket) and s3:PutObject / s3:DeleteObject on the objects ARN (arn:aws:s3:::your-bucket/*). Zeotap does not call s3:GetBucketLocation — the AWS region comes from the AWS Region setting, so that permission is not required.

Configuration

Field	Type	Required	Description
S3 Bucket Name	text	Yes	The Acxiom-managed S3 bucket for data delivery
AWS Region	select	Yes	AWS region where the bucket is hosted (default: `us-east-1`)
Path Prefix	text	No	Folder path prefix within the bucket for organizing files (default: `zeotap/`)

Target Settings

Field	Type	Required	Description
File Format	select	Yes	Output file format: `CSV` or `JSONL` (default: CSV)
Enable Gzip Compression	toggle	No	Compress files with gzip before uploading (default: enabled)

Supported Operations

Sync Modes

Mode	Supported	Description
Insert	Yes	Write the full current dataset as new files on every run
Mirror	Yes	Write changed rows as new files; removed rows are excluded
Upsert	—	Not applicable for file-based delivery
Update	—	Not applicable for file-based delivery
Snapshot	Yes	Write the complete current dataset as new files on every run — no delta, no `_operation` column

Audience Sync Modes

Mode	Supported	Description
Add	Yes	Write new and updated members as a new file (departed members excluded)
Mirror	Yes	Write new and updated members; members who left the audience are excluded
Remove	—	Not applicable for file-based delivery
Upsert	—	Not applicable for file-based delivery
Snapshot	Yes	Write the complete current membership as new files on every run — no delta, no `_operation` column

Features

Feature	Supported
Field Mapping	No
Schema Introspection	No

How It Works

Serialization — Zeotap serializes the batch rows into the configured format (CSV or JSONL)
Compression — If enabled, files are gzip-compressed before upload
Upload — Files are uploaded to the Acxiom S3 bucket using the AWS S3 PutObject API
Path — Files are organized by date partition: {prefix}/{YYYY-MM-DD}/{batch_id}.{ext}
Processing — Acxiom picks up delivered files and processes them through their identity graph for resolution and activation (typically within 24-48 hours)

Each sync batch produces a single file. Insert mode delivers the full current dataset on every run; mirror mode delivers the full dataset on the first run and only changed rows afterward, with removed rows excluded from the files.

Rate Limits

S3 supports up to 3,500 PUT requests per second per prefix partition. This is well above typical sync volumes and unlikely to be a limiting factor.

File size is limited to 5 GB per object via single-part upload. For larger datasets, Zeotap automatically splits data across multiple batch files.

Best Practices

Use CSV format for Acxiom delivery — CSV is the standard format for Acxiom data onboarding pipelines
Enable gzip compression to reduce upload time and storage costs
Coordinate path prefix with your Acxiom representative so they know where to find delivered files
Include identity fields (email, phone, postal address) to maximize Acxiom’s identity resolution match rates
Use snapshot mode for audience syncs when Acxiom needs the full membership on every run; mirror delivers only new and changed rows after the first run, excluding departed members

Troubleshooting

Connection test fails with “Access Denied”

The AWS credentials do not have permission to access the S3 bucket. Verify the access key has s3:ListBucket and s3:PutObject on the bucket (see Required Permissions) — s3:DeleteObject is only used for best-effort marker cleanup and does not fail the run. A HeadBucket/ListBucket denial fails the connection test; a PutObject denial surfaces at the start of the first sync run. Contact your Acxiom representative to verify bucket provisioning.

Connection test fails with “bucket not found”

The bucket name is incorrect or the bucket has not been provisioned yet. Double-check the bucket name provided by Acxiom and verify the correct AWS region is selected.

Files are not being processed by Acxiom

Acxiom processes delivered files on a batch schedule (typically 24-48 hours). If files are not processed after 48 hours, verify the path prefix matches what Acxiom expects and contact your Acxiom representative.

Upload fails with timeout

Large files may timeout on slow connections. Enable gzip compression to reduce file sizes, or check your network connectivity to the AWS region hosting the bucket.

”InvalidAccessKeyId” error

The AWS Access Key ID is incorrect or has been deactivated. Generate new credentials and update them in Zeotap.

Region mismatch error

The selected AWS region does not match the bucket’s actual region. Contact your Acxiom representative to confirm the correct region.