Amperity + AWS

Build an AWS CDP with trusted customer context

Q: Is AWS a customer data platform?

AWS is a cloud platform with services that can support a CDP architecture. Your customer data platform capabilities depend on the applications and workflows you choose. Amperity is the Customer Context Platform, adding customer identity resolution, profile building, segmentation, and supported audience delivery to that environment.

Q: What is a customer data platform on AWS?

A customer data platform on AWS combines cloud infrastructure with capabilities that connect customer records and make them useful for analysis and engagement. When evaluating an AWS customer data platform, separate where data is stored from where processing, application services, and audience delivery run.

Q: Can Amperity use customer data in Amazon S3?

Yes. Amperity can pull files from a configured Amazon S3 source and send supported output files to an S3 destination. Your team configures the bucket, access, formats, and workflows. Plan those transfers separately from Amperity processing and application services.

Q: How does Amperity support a Redshift CDP architecture?

Amperity can deliver selected customer data toward Amazon Redshift: it sends the data to Amazon S3 for a separately configured Redshift load. Identity processing stays in Amperity. Bringing Redshift data into Amperity depends on your configuration, so confirm the supported inbound path with Amperity during implementation.

Q: Can we use our own S3 storage?

Eligible new tenants can configure Bring Your Own Storage using customer-owned Amazon S3. Amperity continues to manage its application and control layer. Storage eligibility, cloud, region, and access requirements need to be confirmed for your implementation.

Q: Does Amperity run on our own AWS compute?

Processing is Amperity-managed by default. Amperity runs identity resolution, profile generation, and its application services on managed compute. S3 source connections and customer-owned S3 storage are separate from compute ownership and do not move Amperity processing into your AWS account.

Q: Can marketers build audiences without writing SQL?

Yes. The Amperity Segment Editor provides dropdowns, picklists, and conditions for building audiences from configured attributes. Your data team prepares the underlying data and permissions. Marketers can then define, review, and activate segments through supported destinations.

Recognize valuable customers across the records you already manage on AWS. Amperity connects fragmented first-party data into resolved profiles, helping your teams decide who to reach, what matters to them, and which audience to activate next.

Build on your AWS investment with supported Amazon S3 connections, customer identity resolution, and audience workflows that fit your existing marketing tools.

Request a demo Explore lakehouse demo

Your AWS data holds the history. Identity connects the customer.

An online order, a store purchase, and a loyalty account can describe the same person under different identifiers. Count them separately and a loyal customer can appear to be a new prospect, while their purchase history understates their value.

AWS gives your team services for storing, processing, and analyzing those records. Amperity adds identity resolution and usable customer context, so customer decisions can reflect the relationship across the sources you connect.

Identity Resolution

How Amperity works with your AWS environment

Connect the customer data your use case needs

Bring selected customer files from Amazon S3 into Amperity through a configured source connection. Your team defines the bucket, available files, supported formats, and access. This can include regular exports from upstream systems alongside other connected first-party sources.

Amazon S3 source setup

Resolve records into useful customer history

An exact email match can miss someone who changed addresses or used a different account in store. Amperity combines configured rules with AI-assisted scoring to evaluate connections between records. Your team can inspect the resulting profiles and tune the matching approach to the use case.

Explore Profiles

Build audiences and put them to work

Use configured customer attributes and purchase history to build segments in Amperity. Review the audience and destination before sending it through a supported connection. You can also export selected data to S3 for downstream analysis, including a separately configured load into Amazon Redshift.

Customer segmentation

Plan storage, processing, and delivery separately

An AWS CDP architecture can use several AWS services, each with its own role. An S3 connector, customer-owned storage, and a Redshift delivery workflow are different choices. Match each one to your data, access, and operating requirements.

Layer or option	What it supports	What to plan for
Amazon S3 source connection	Pull selected customer files into Amperity.	Configure bucket access, file formats, and ingestion workflows.
Bring Your Own Storage	Customer-owned S3 storage for configured Amperity data, for eligible new tenants.	Confirm tenant eligibility, cloud, region, and access during implementation. Storage and compute are independent choices.
Amperity processing and application	Identity resolution, profile generation, segmentation, and managed application services.	Default processing is Amperity-managed. S3 storage ownership does not determine compute ownership.
Amazon S3 and Redshift output	Send selected output to S3, then load it into Redshift through an AWS workflow.	Configure the downstream load, access, and refresh schedule separately.

Bring Your Own Storage is available for eligible new Amperity tenants provisioned for Amazon S3 or Azure. Choosing your own S3 storage does not move the Amperity application or its processing into your AWS account; processing stays Amperity-managed. Confirm tenant eligibility, cloud, region, and access with Amperity during implementation.

Review storage options

Make better customer decisions with your AWS data

Recognize valuable customers across channels

Connect store and online purchase history to understand the value visible across your connected sources. Use that context to distinguish an occasional shopper from a loyal customer whose activity spans multiple systems.

Keep existing buyers out of acquisition audiences

A recent buyer can still look like a prospect when their records are fragmented. Build suppression audiences from resolved customer history, apply the relevant eligibility criteria, and send reviewed segments to supported advertising destinations.

Give retention campaigns a clearer starting point

Use available purchase history and loyalty attributes to identify repeat buyers or customers whose buying pattern has changed. Build audiences for retention and win-back programs, with the relevant consent and exclusions included in your segment design.

Bring customer context back to AWS analytics

Export selected resolved data to S3 and configure your downstream Redshift load. Analysts can use that customer context alongside other business data to examine cross-channel behavior and campaign results, with refresh schedules appropriate to the analysis.

Delivery to Redshift

See how resolved identity becomes usable context

Explore the lakehouse demo for a closer look at Amperity identity graphs and analytics workflows. Bring your AWS use case to a personalized walkthrough to discuss the S3 connections, storage choices, and destinations your team needs.

Explore lakehouse demo

Start with the customer decision you need to improve

Choose an initial use case and the source records behind it. Work with Amperity to assess identity, define the profile and audience attributes, and agree on the data flows. Your AWS team reviews bucket access and storage requirements; your marketing team defines the audience and destination.

Before activation, review the resulting profiles and segment. Set the refresh schedule and success measures, then compare the outcome with your starting baseline. Expand to additional sources and use cases as your team validates the foundation.

AWS CDP FAQs

Is AWS a customer data platform?

What is a customer data platform on AWS?

Can Amperity use customer data in Amazon S3?

How does Amperity support a Redshift CDP architecture?

Can we use our own S3 storage?

Does Amperity run on our own AWS compute?

Can marketers build audiences without writing SQL?

Put your AWS customer data to work on the next decision

Bring us the customer relationship your team needs to understand. We will show how identity, profiles, and audience activation can build on the AWS environment you already use.

Request a demo