Customer.io Known Pitfalls

Prerequisites

• The intended workspace, consent/data classification, event schema, and deployment owner.
• A synthetic test profile and a redacted diagnostic process; never investigate with production recipients by default.

Instructions

1. Identify the applicable pitfall before changing an event, campaign, segment, or integration setting.
2. Validate schema, identity, consent, environment, and idempotency in development/staging.
3. Make one reversible correction and verify its effect with synthetic data before promotion.
4. Record recurring failures in reviewed runbooks/contracts rather than relying on ad hoc retries.

Output

• A documented prevention or correction for a specific delivery, data, consent, or integration pitfall.

Error Handling