# Limits & errors

What the Klaviyo connection does not do, its limits, and the common errors when connecting or sending events.

## Limits

| Limit | Value |
|-------|-------|
| Klaviyo accounts per profile | One |
| Events per request to Klaviyo | One, five requests at a time |
| Metric name length | 128 characters |
| Test mode | None |

## What you cannot do

- Send hashed emails or phones: Klaviyo needs the plain value to reach the person
- Test without reaching a live account: use a separate Klaviyo account for tests
- Read Klaviyo lists, profiles or campaign results through Zernio
- Post, schedule or use the Inbox API on a Klaviyo account

## Common errors

| Error | Cause | Fix |
|-------|-------|-----|
| `400` on `apiKey` | The key does not start with `pk_` | Use a private API key. |
| `401` with `invalid_credentials` on connect | Klaviyo refused the key | Create a key with Events (write) and Accounts (read). |
| `403` on connect | The Ads add-on is off | Turn on the Ads add-on. |
| `409` with `profile_platform_conflict` | The profile already has another Klaviyo account | Disconnect it first, or use another profile. |
| A failure naming "Klaviyo needs" on an event | No usable match key | See [Conversions](/platforms/klaviyo/conversions#if-it-fails). |
| `401` with `reconnect_required` on an event | Klaviyo refused the saved key | Connect again with a fresh key. |

## Related

- [Connect](/platforms/klaviyo/connect)
- [Conversions](/platforms/klaviyo/conversions)
- [Rate limits](/guides/rate-limits)