Adobe Experience Platform integration with Amperity

Q: How does Amperity integrate with Adobe Experience Platform?

Amperity exports CSV files to a configured SFTP destination. Its Experience Platform destination creates a .fin completion file after each successful upload. Coordinate the receiving schema and processing configuration before sending a full audience.

Q: Can I import Adobe Analytics data into Amperity?

Yes. Use an Adobe Analytics Data Feed staged in Amazon S3, Azure Blob Storage or SFTP. Adobe identifies FTP and SFTP destinations as legacy and recommends cloud destinations. Include an identifier linked to your internal customer IDs.

Q: Does Amperity send data directly to Adobe Campaign recipients?

Amperity delivers CSV files through SFTP. Configure Adobe Campaign to import the file and reconcile its rows with the intended recipient table. File delivery alone does not create or update recipients.

Q: Which Adobe Commerce data can Amperity ingest?

The source supports Customers, Customer Address, Customer Group, Orders, Order Address and Order Items. It requires the storefront host and OAuth-based consumer and access credentials.

Q: Is the Adobe integration real time?

The documented Adobe workflows use files or courier runs. Set the cadence for each connection and its receiving process. Analytics Data Feeds offer hourly or daily batches; that delivery cadence is separate from Amperity ingestion.

Amperity sends customer attributes and audience files to Adobe Experience Platform through CSV and SFTP. Separate connections bring Adobe Analytics and Adobe Commerce data into Amperity and exchange files over SFTP with Adobe Campaign and Adobe Customer Attributes.

Get a demo See the Adobe docs

CSV over SFTP • Adobe data sources • Product-specific connections

Connect customer context to your Adobe workflows

Personalize Adobe workflows with customer attributes shaped in Amperity.

Target Campaign audiences using purchase history from connected sources.

Understand customer behavior by connecting Analytics events with known identifiers.

Inform retention decisions with Commerce customer and order history.

How Amperity and Adobe connect

Choose the product and direction. Configure the relevant source or destination, rather than treating Adobe as one connector.
Align the data and identity fields. Shape exported columns for the receiving schema, or define feeds and semantic tags for incoming data.
Validate and schedule the workflow. Test a small sample, verify its interpretation in the receiving product, and coordinate file delivery with ingestion.

Direction and method depend on the selected Adobe product.

What the Adobe integration supports

Capability	Supported behavior
Adobe Experience Platform	Outbound CSV over SFTP; username/passphrase; static schema.
Adobe Campaign	Inbound SFTP files; outbound CSV over SFTP with username/private key; receiving import required.
Adobe Analytics	Inbound raw Data Feed through S3, Azure Blob Storage or legacy SFTP; Amperity recommends daily hit_data.tsv.
Adobe Commerce	Inbound customer, address, group, order and item datasets; OAuth consumer key/secret and access token/secret.
Adobe Customer Attributes	Inbound SFTP files; outbound CSV over SFTP with username/passphrase; customer ID alignment required.

Map Adobe objects to the intended workflow

Match each connection to its receiving schema, recipient key, or source fields.

Adobe object	Field handling	Technical references
Experience Platform schema fields	Shape CSV columns to the receiving schema; preserve existing field definitions.	Amperity destination · Adobe Schema Registry API
Campaign recipients	Map exported fields and choose a reconciliation key in the receiving Campaign workflow.	Amperity Campaign · Adobe recipient schema
Analytics hit_data.tsv	Select relevant clickstream fields and a login or cookie ID linked to internal IDs.	Amperity Analytics · Adobe Data Feed API
Commerce Customers and Orders	Retain ENTITY_ID and order CUSTOMER_ID; review semantic tags after ingestion.	Amperity Commerce · Adobe REST reference
Customer Attributes customer ID	Use the unique customer ID passed to Visitor ID Service as the first CSV column.	Amperity Customer Attributes · Adobe setCustomerIDs

Put Adobe customer context to work

Build Campaign audiences from purchase history

Bring Adobe Commerce customer and transaction data into Amperity alongside other configured sources. Use the resulting customer history to define an audience, such as purchasers who have not returned, then deliver selected attributes as a CSV over SFTP to Adobe Campaign. Configure Campaign’s import and reconciliation workflow to identify the intended recipients before using the audience in a campaign. This gives teams a way to base targeting on the customer relationship across connected data.

Connect digital behavior with customer attributes

Ingest selected Adobe Analytics Data Feed events with an identifier that links to your internal customer IDs. Combine those signals with available customer history in Amperity to support segmentation. For a separate outbound workflow, send selected attributes as a CSV over SFTP to Adobe Customer Attributes, where configured subscriptions make them available to Adobe Analytics or Adobe Target. Align the uploaded customer ID with the Visitor ID Service implementation so the receiving applications can associate the attributes with the intended visitor.

Set up each Adobe connection for its receiving system

For Experience Platform, configure the SFTP host, username, passphrase and remote folder. Keep the output aligned with its static schema: existing fields cannot be renamed, removed or redefined. A Datagrid Operator configures and validates the destination before business users send data.

For Campaign, configure SFTP delivery with a username and private key, then the receiving import and reconciliation key. For Customer Attributes, configure SFTP delivery with a username and passphrase, align customer IDs and validate the required CSV completion file. Apply your organization’s permitted-use and suppression rules when selecting export fields and audiences.

Use the Experience Platform, Campaign source, Campaign destination, Analytics, Commerce, Customer Attributes source, and Customer Attributes destination guides for credentials, schema and validation.

Adobe integration FAQs

How does Amperity integrate with Adobe Experience Platform?

Can I import Adobe Analytics data into Amperity?

Does Amperity send data directly to Adobe Campaign recipients?

Which Adobe Commerce data can Amperity ingest?

Is the Adobe integration real time?

Make Adobe targeting more relevant

Use connected customer history to define who belongs in your next Adobe audience.

Get a demo