How to Integrate Privy with Attentive

Privy’s Attentive integration needs account authorization, the default Phone field and a display sync rule containing an Attentive Source ID. Verify custom fields separately: Privy documents that a successful sync result can still overlook custom-field errors.

This guide follows Privy’s Attentive v2.0 documentation, checked September 6, 2026. The verification worksheet below is editorial guidance, not a report of customer-account testing.

Connect the correct accounts

1. In Privy, open Settings → Linked Accounts and select Attentive.
2. Sign in to Attentive and authorize the connection.
3. If your login belongs to multiple Privy accounts, select the intended account to link.
4. Confirm Attentive appears among authorized accounts and use the connection-test option.

Privy says connections established before August 19, 2021 need the updated setup to use the expanded field-sync features. If you are reviewing an older account, check that history before diagnosing a missing custom property.

Prepare the display and Source ID

Use Privy’s default Phone field, identified as contact_phone, to collect a single number. Add the SMS marketing disclosure required for your setup; Privy directs users to their Attentive representative for appropriate wording and placement. Do not copy another brand’s example disclosure into your campaign unchanged.

Then open the display’s Settings → Show Advanced Settings → Sync Integrations. Choose Add Integration, select Attentive, enter the Source ID, and save. Obtain that ID from your Attentive representative if you do not have it. Review the display before publishing.

The Source ID also matters for the message type associated with the subscriber’s channel. Record which source you are using with the campaign name so someone reviewing the setup can trace the intended behavior.

Check the supported data shape

Verify one complete test signup

Use a controlled test contact and record its submission time, campaign and Source ID. Check these stages separately:

1. Collection: confirm the submitted phone and any email are recorded in Privy.
2. Arrival: locate the same contact in Attentive.
3. Channels: inspect the resulting TEXT and, when collected, EMAIL channel state against the intended source.
4. Confirmation: follow the applicable opt-in flow. Privy documents a double-opt-in text for new subscribers and a possible already-subscribed text for existing subscribers.
5. Properties: compare each required custom-field value in Privy and Attentive.
6. Follow-up: verify the intended message or workflow separately from record creation.

Do not use only the sync success indicator as acceptance evidence. Privy says it reports success when the phone and/or email transfers successfully, while custom-field errors are ignored. A contact can therefore arrive without every property you expected.

Diagnose missing data without changing everything

If no contact arrives, inspect the connection test, saved Source ID and default Phone field first. If the contact arrives but a property is missing, compare its source value and field format before reconnecting the whole integration.

For an unexpected message, inspect the source and channel configuration and whether the test contact was already subscribed. Keep evidence of the actual result rather than assuming every signup behaves like a new subscriber.

Remove the connection when it is no longer needed

Privy documents two removal steps: delete the Attentive connection in Linked Accounts, then revoke Privy under Attentive’s Connected Apps. Identify affected displays before changing either side and verify where future signups should go.

Review Privy Profile Attributes for collected data, or browse Privy integrations for other destinations.