Customer.io

Integrate Mavera with Customer.io — campaign metric analysis, attribute-based personas, and webhook-driven research triggers

Pull data from Customer.io (Campaign Metrics, Customer Attributes, Reporting Webhooks) → analyze with Mavera (Mave Agent, Custom Personas, Chat, Generate) → get persona-validated messaging strategies, audience clusters, and automated retention research.

Customer.io API — Two APIs: Track (https://track.customer.io/api/) uses HTTP Basic auth (Site ID : API Key), ~1,000 req/sec. App (https://api.customer.io/v1/) uses Bearer Token, 10 req/sec. Campaign metrics live in the App API; event tracking and customer attribute reads use Track.

---

Prerequisites

1. Customer.io API credentials

   Create a Track API key (Site ID + API Key) and an App API key (Bearer Token) from your Customer.io workspace settings.
2. Mavera API key

   Get your key from Mavera dashboard.
3. Environment variables

   export CIO_SITE_ID="your_site_id"
   export CIO_API_KEY="your_api_key"
   export CIO_APP_KEY="your_app_api_key"
   export MAVERA_API_KEY="mvra_live_xxxxx"
   

---

Jobs

#	Job	Customer.io Data	Mavera Surface	Output
1	Campaign Event Analysis → Messaging Strategy	Campaign metrics	Mave Agent + Generate	New message variations
2	Customer Attribute Personas	App API customer attributes	Custom Personas	Attribute-clustered personas
3	Webhook Event → Mave Research Trigger	Reporting webhooks	Mave Agent	Retention research

---

Rate Limits & Production Notes

Endpoint	Limit	Strategy
Track API (identify/track)	~1,000 req/sec	Generous; batch where possible
App API (campaigns, customers)	10 req/sec	120ms delay; retry on 429
Segment membership	10 req/sec	Paginate with next cursor
Reporting webhooks	N/A (push)	Queue high-volume events

The App API at 10 req/sec is the bottleneck. Individual customer attribute lookups are the most expensive pattern. For bulk operations, use Customer.io’s Data Export or segment-level APIs instead of per-customer calls.

Production checklist:

• Store CIO_SITE_ID, CIO_API_KEY, CIO_APP_KEY, and MAVERA_API_KEY in a secrets manager — never commit tokens.
• Implement webhook signature verification with CIO_WEBHOOK_SECRET in production.
• For webhook receivers, deploy behind a load balancer and use a message queue to decouple event ingestion from Mave research calls.
• Monitor Mavera credits at Dashboard.
• Cache customer attributes locally if running persona creation frequently — App API rate limits make per-customer lookups expensive.

---

What’s Next

All Integrations

Customer.io API

Personas

Mave Agent

Generate

Focus Groups