Pre-Built Tooling
| Category | Details |
|---|---|
| Authentication | HTTP Basic Authentication (Site ID and API Key) |
| Two-Way Sync | Yes |
| Events Supported | Yes (Webhooks) |
| Realtime | Yes |
| Supports Rate Limiting | Yes |
| Authentication Scopes Supported | N/A (API Key based authentication) |
Objects Supported
Alloy Automation supports syncing the following objects from Customer IO:- Customers
- Events
- Campaigns
- Segments
- Messages
- Broadcasts
- Newsletters
- Transactional Messages
Set Up Guide
Trial Access
| Question | Answer |
|---|---|
| Offers free trial? | Yes. Customer.io offers a free tier for up to 12,000 profiles. Sign up at https://customer.io to get started. |
| Requires requires paid sandbox | No paid sandbox required. You can use the free tier for testing. |
| Requires partnership to obtain authentication? | No. API credentials can be obtained directly from your Customer.io workspace settings. |
Authentication (HTTP Basic Authentication)
Customer.io uses HTTP Basic Authentication with your Site ID and API Key.- Log in to your Customer.io account at https://fly.customer.io.
- Navigate to Settings → API Credentials in your workspace.
- Copy your Site ID and API Key (or create a new API key if needed).
- Enter your Site ID as the username and API Key as the password in Alloy Automation.
API Documentation
For detailed API documentation, visit: https://customer.io/docs/api/Important Notes
- Customer.io provides separate API keys for tracking and app API access
- Tracking API is used for sending customer data and events
- App API is used for managing campaigns, segments, and exports
- Make sure to use the correct API key based on your integration needs
Use Cases
1) Customer lifecycle automation
Sync customer data from your application into Customer.io to trigger automated email campaigns, push notifications, and SMS messages based on user behavior and lifecycle stages.2) Event-driven messaging
Send real-time events from your platform to Customer.io to trigger transactional emails, in-app messages, and multi-channel campaigns based on specific user actions.3) Segment synchronization
Keep customer segments in sync between Customer.io and your CRM or data warehouse, ensuring consistent targeting across all marketing channels.4) Campaign performance tracking
Pull campaign metrics and message delivery data from Customer.io into your analytics platform for comprehensive marketing performance reporting.5) Profile enrichment
Enrich customer profiles in Customer.io with data from other systems like CRMs, support tools, and product analytics platforms to enable more personalized messaging.API Gotchas
- Rate limiting: Customer.io enforces rate limits on API requests. The tracking API has different limits than the app API. Monitor response headers and implement appropriate backoff strategies.
- Site ID vs API key: Customer.io uses a Site ID (username) and API Key (password) for basic authentication. Don’t confuse the Site ID with the API key.
- Different APIs for different purposes: Customer.io has separate APIs for tracking (sending data) and app operations (managing campaigns). Ensure you’re using the correct endpoint.
- Batch operations: For sending large volumes of customer data or events, use the batch API endpoints to improve performance and reduce rate limiting issues.
For questions or troubleshooting, contact support@runalloy.com.