Attentive SMS integration with Amperity

Q: How does Amperity integrate with Attentive?

Amperity sends audience membership through Attentive’s Subscriber Segment Upload process over SFTP. A separate API destination sends custom profile attributes for segmentation in Attentive. An inbound SFTP source can pull subscriber lists and status into Amperity.

Q: Can I send phone numbers and email addresses to Attentive?

Yes, using separate audience files. Each SFTP audience file contains phone numbers or email addresses, plus its segment name. The API attribute destination requires the primary identifier configured for your Attentive account.

Q: Does importing an audience subscribe customers to Attentive SMS?

No. Attentive remains the source of truth for subscription status. The SFTP audience process ignores unmatched or ineligible identifiers, and Amperity cannot use this connection to change subscriber status.

Q: How often do Attentive audiences update, and are removed members deleted?

Allow up to 24 hours after Amperity finishes sending an audience. An upload with an existing segment name replaces that membership list, so send the full current list. Removing segment membership is not a request to delete a subscriber or change consent.

Q: Does the integration automatically send SMS campaigns?

No. Audience and attribute exports prepare data for use in Attentive. Your team configures messaging in Attentive, where subscription eligibility continues to apply.

Use Amperity customer context to build more relevant Attentive SMS audiences. Send segment membership through SFTP and custom profile attributes through the API, and bring subscriber status into Amperity while Attentive manages subscription permissions.

Get a demo See the Attentive docs

SFTP audiences • API attributes • Subscriber status imports

Target subscribers using purchase history and other customer context available in Amperity.

Personalize Attentive segments with custom attributes that describe the customer relationship.

Refresh audience membership as customers enter or leave your selection criteria.

Identify opted-in customers using subscriber status imported from Attentive.

How the Attentive integration connects customer context to messaging

Bring subscription context into Amperity. Pull audience subscriber lists and status from Attentive’s /downloads directory through an SFTP source, then link that data to customer records.
Define who belongs and what matters. Build a segment or query from your customer context, choosing either audience membership for SFTP delivery or descriptive profile attributes for the Attentive API destination.
Send the right data by the right route. Export subscriber identifiers and segment names through the Attentive Mobile SFTP destination, or send custom attributes through the Bulk attribute endpoint.
Validate before you message. Verify a sample in Attentive, then configure campaigns or journeys there for eligible subscribers; transferring an audience or attributes does not itself send an SMS.

Attentive controls subscription status. Messaging is configured in Attentive.

What the Attentive integration supports

Capability	Supported behavior
Direction and method	Outbound: Amperity to Attentive through SFTP for audience membership or API for attributes. Inbound: Attentive subscriber lists and status to Amperity through a separate SFTP source.
Objects and identifiers	SFTP audience: Phone or Email, plus segment_name; never mix phone and email in one file. API attributes: include the account’s primary identifier, email or phone.
Refresh and replacement	SFTP audience updates can take up to 24 hours after sending. Reusing a segment name replaces its membership list. API attribute updates are asynchronous; Amperity success means request acceptance, without attribute update status tracking.
Authentication	SFTP: hostname sftp.attentivemobile.com, username, passphrase and folder permissions. API: bearer API key for a custom app with Custom Attributes: All and Subscribers: All.
Subscription permissions	Attentive controls subscriber status. Amperity does not update that status. SFTP imports ignore identifiers that do not match active, opted-in subscribers; segment membership does not grant messaging permission.

Put the Attentive integration to work

Reconnect with lapsed repeat buyers

Build a lapsed-buyer audience using the purchase history available in Amperity, including transactions from connected channels. Use imported Attentive subscriber status to identify opted-in customers, then send the selected audience through SFTP. As buying behavior changes, refresh the full membership list under the same segment name. Your team can review the resulting segment in Attentive and configure a relevant re-engagement campaign for subscribers who remain eligible to receive messages.

Tailor loyalty messaging with customer attributes

Send a customer’s loyalty tier or preferred product category as a custom profile attribute when that information is available and appropriate to share. Build segments in Attentive from those attributes to distinguish loyalty recognition from broader promotional messaging. Keep attribute names and values consistent so your segment conditions match the exported data. The API route supplies descriptive customer context; your team still defines the segment rules, campaign content and journey behavior inside Attentive.

Set up the Attentive integration for your workflow

Ask Attentive’s White Glove team to enable subscriber segment uploads and confirm the identifier and assigned SFTP folder. Have your Datagrid Operator or Amperity representative configure the destination, test a sample in a sandbox, and verify the result in Attentive before production use. Use headerless audience CSV files unless Attentive approves a different configuration. Follow its filename rules and 500,000-row limit per file.

For attributes, configure the Attentive API credential and primary identifier separately. Custom attribute names and values are case sensitive, and attributes cannot contain sensitive or special categories of information. Configure an inbound SFTP source separately if you need subscriber status in Amperity.

Review the audience destination setup, attribute destination setup and subscriber source setup for the exact configuration requirements.

Attentive integration FAQs

How does Amperity integrate with Attentive?

Can I send phone numbers and email addresses to Attentive?

Does importing an audience subscribe customers to Attentive SMS?

How often do Attentive audiences update, and are removed members deleted?

Does the integration automatically send SMS campaigns?

Make your next Attentive audience more relevant

See how customer context in Amperity can help your team choose the right subscribers and prepare more relevant messaging in Attentive.

Get a demo