Attentive

​

Pre-Built Tooling

Category	Details
Authentication	OAuth 2.0 (Authorization Code with refresh tokens) or Bearer Token (JWT)
Two-Way Sync	Yes
Events Supported	Yes
Realtime	Yes
Supports Rate Limiting	Yes (429 status code handling)
Authentication Scopes Supported	subscriptions:write (write subscription events), events:write (write custom events), ecommerce:write (write ecommerce events), attributes:write (write attributes events), privacy_requests:write (write privacy requests events)

---

​

Objects Supported

Alloy Automation supports syncing the following objects from Attentive:

• eCommerce Events (Product View, Add to Cart, Purchase)
• Offers
• Custom Events
• Custom Attributes
• Subscribers
• Product Catalog
• Privacy Requests
• Identity (User Identifiers)

---

​

Set Up Guide

​

Trial Access

Question	Answer
Offers free trial?	Contact Attentive for trial access information at https://www.attentivemobile.com/demo. Attentive typically requires a paid plan to access API features.
Requires requires paid sandbox	Contact Attentive to inquire about sandbox environments for testing.
Requires partnership to obtain authentication?	No, but you must be an existing Attentive customer with API access enabled for your account.

---

​

Authentication (OAuth 2.0 or Bearer Token)

For customers who want to completely whitelabel their OAuth experience, you can provide your own developer keys instead of using Alloy Automation’s.

​

Option 1: OAuth 2.0 (Recommended for user-facing integrations)

1. Contact your Attentive Customer Success Manager to request API access and OAuth credentials.
2. Once approved, you’ll receive:
   • Client ID
   • Client Secret
3. Configure your OAuth application in Attentive:
   • Add the redirect URI: https://api.runalloy.com/api/strategy/connector/attentive/callback
   • Select the scopes your integration requires (e.g., subscriptions:write, ecommerce:write, events:write)
4. Enter your Client ID and Client Secret into Alloy Automation.

​

Option 2: Bearer Token (API Key)

1. Log in to your Attentive account and navigate to Settings → Integrations.
2. Generate a new API token with the appropriate permissions.
3. Copy the generated Bearer token (JWT format).
4. Enter the token into Alloy Automation as a Bearer token.

​

OAuth Authorization URL

The authorization URL for Attentive is: https://ui.attentivemobile.com/integrations/oauth-install

​

Scopes

Attentive uses write-scoped permissions:

• subscriptions:write - Manage subscriber subscriptions and unsubscriptions
• ecommerce:write - Send eCommerce events (product views, cart additions, purchases)
• events:write - Send custom events for segmentation and journey building
• attributes:write - Set custom attributes on subscribers
• privacy_requests:write - Submit CCPA deletion requests

---

​

Use Cases

​

1) Abandoned cart SMS recovery

Automatically send “Add to Cart” events to Attentive when customers add items to their cart, triggering personalized SMS reminders and recovering lost revenue through timely follow-ups.

​

2) Post-purchase SMS engagement

Sync purchase data to Attentive in real-time, enabling automated order confirmations, shipping updates, and post-purchase review requests via SMS to enhance customer experience.

​

3) Subscriber synchronization

Keep subscriber lists synchronized between Attentive and your CRM or eCommerce platform, ensuring consistent opt-in/opt-out status and preventing compliance issues.

​

4) Custom event-based journeys

Send custom events from your application to Attentive to trigger sophisticated SMS journeys based on user behavior, such as milestone achievements, usage patterns, or account activity.

​

5) Product catalog synchronization

Sync your product catalog with Attentive to enable advanced SMS campaigns like back-in-stock alerts, price drop notifications, and personalized product recommendations based on customer preferences.

---

​

API Gotchas

• ⚠️ Rate limiting: Attentive enforces rate limits and returns 429 status codes when exceeded. Implement exponential backoff and retry logic in your integration.
• ⚠️ API access requirements: API access is not enabled by default. You must contact your Attentive Customer Success Manager to enable API features for your account.
• ⚠️ Identity bridging: When using custom identifiers, avoid sending duplicate values as this can unintentionally bridge separate user profiles together.

For questions or troubleshooting, contact support@runalloy.com.