Iterable integration with Amperity

Q: How does Amperity integrate with Iterable?

Amperity sends audience data outward through the Iterable API using campaigns or query orchestrations. Configure the destination first, then validate a sample in Iterable before enabling ongoing delivery.

Q: Does Iterable use email or userId to identify customers?

It depends on the project. UserID-based projects use userId; email-based projects use email, while hybrid projects accept either. Align the connector’s chosen identifier with your project, and exclude missing lookup values. Iterable rejects blank or null userId lookup fields.

Q: Can I send custom profile attributes to Iterable?

Yes. Select the attributes to send with the identifier. Fields outside the standard profile fields are stored in dataFields for personalization and segmentation. Preserve exact field names: Iterable profile fields are case-sensitive and space-sensitive.

Q: Can I update existing Iterable users without creating new profiles?

The connector has an “Update existing profiles only?” setting. Enabling it limits updates to existing profiles, but hybrid projects may still create new users. Test your project’s behavior before using this setting as a creation restriction.

Q: Does an Iterable audience list establish messaging consent?

No. List membership does not establish a customer’s consent or subscription preferences. Filter the audience using the eligibility information available in Amperity, then check message eligibility and subscription settings in Iterable before sending.

Send customer audiences and profile attributes from Amperity to Iterable through the Iterable API. Use customer context to shape relevant outreach, with identifiers matched to your Iterable project and delivery managed through campaigns or orchestrations.

The Iterable connector is in beta. Contact your Amperity representative about access and configuration.

Get a demo See the Iterable docs

Outbound API delivery • Audience lists • Profile attributes

Make Iterable outreach more relevant

Tailor follow-up to the customer history available in Amperity.

Distinguish loyalty audiences before choosing the next message.

Personalize messages with selected customer profile attributes.

Reduce repeated audience exports with scheduled delivery.

How Amperity and Iterable connect

Define the audience. Build a segment for an Amperity campaign or a query for an orchestration.
Map customer context. Choose the project’s identifier and the profile attributes your Iterable team needs.
Validate, then schedule. Send a sample, check the results in Iterable, and enable recurring delivery after verification.

Outbound audience delivery; messaging is configured in Iterable.

What the Iterable integration supports

Capability	Supported behavior
Direction, method, and state	Amperity to Iterable through the Iterable API; beta connector.
Customer identity	email or userId, selected for the Iterable project. Campaign mappings include email → email and amperity_id → userId.
Lists and profiles	Named audience list; created if absent. Selected profile attributes. New-profile creation can be disabled, with a hybrid-project exception.
Delivery cadence	Campaign or orchestration scheduling. Query orchestrations can start manually, then switch to automatic after validation.
Authentication	Server-side API key. US: https://api.iterable.com. EU: https://api.eu.iterable.com.

Map audiences and attributes to Iterable

Iterable object	Amperity data	Documentation
Audience list	Selected customers are sent to the named Iterable list.	Amperity mapping · Iterable reference · Iterable API
User profile	Send selected standard fields and custom dataFields.	Amperity mapping · Iterable reference · Iterable API

What teams do with Amperity and Iterable

Tailor follow-up to purchase history

Use purchase history available in Amperity to distinguish first-time buyers from repeat customers before sending an audience to Iterable. Include selected attributes that help the messaging team choose relevant content, such as a customer’s preferred category when that information is available. Review the audience and attributes before delivery, then configure the message in Iterable. This gives the team a practical way to base follow-up on the customer relationship rather than treating every recipient alike.

Give loyalty members a relevant next message

Build a loyalty audience from the membership and transaction attributes available in Amperity, then send the selected customers and useful profile fields to Iterable. A team might separate established members from newly enrolled customers so each group receives appropriate content. Set the delivery schedule around the source data’s refresh and the outreach plan. Keep message eligibility and subscription checks in the Iterable workflow, and verify a sample before using the audience for a broader send.

Set up the Iterable connection

An Amperity operator or representative configures the destination. Provide a server-side API key for the intended Iterable project and select its US or EU base URL; the key and endpoint must belong to the same data center.

Configure and test in a sandbox before production. Verify the selected identifier, audience list, attribute names, and new-profile behavior in Iterable. Confirm list removal, subscription changes, and field-clearing requirements with your Amperity representative before relying on those behaviors.

Read the setup guide

Iterable integration FAQs

How does Amperity integrate with Iterable?

Does Iterable use email or userId to identify customers?

Can I send custom profile attributes to Iterable?

Can I update existing Iterable users without creating new profiles?

Does an Iterable audience list establish messaging consent?

Put customer context to work in Iterable

Give your messaging team audiences and attributes that help them choose a more relevant next interaction.

Get a demo