# Attentive

Connect Attentive with a custom app's API key and send purchases, carts, product views and custom events to it from your server.

Connect Attentive to a profile with the API key of a custom app. The account (`platform: "attentive"`) receives your events as Attentive eCommerce and custom events, so Journeys and segments react to server-side sales.

## Quick reference

| Property | Value |
|----------|-------|
| Platform value | `attentive` |
| What it does | Receives your events through Attentive's eCommerce and Custom Events APIs |
| Auth | A custom app's API key with Custom Events and eCommerce write access |
| Destination | The Attentive company id. Each connection has exactly one |
| Match keys | Unhashed email, phone with its country code, or external id |
| Test mode | None: every event is live and can start a Journey |
| Plan | Requires the Ads add-on |

## Before you start

In Attentive, create a custom app under **Integrations** with write access to **Custom Events** and **eCommerce**, and copy its API key.

## Connect

Send the key to `POST /v1/connect/attentive/credentials`. Zernio reads the key's company to check it before saving anything. See [Connect](/platforms/attentive/connect).

## Common errors

| Error | Cause | Fix |
|-------|-------|-----|
| `401` with `invalid_credentials` | Attentive refused the key | Copy the key again from the custom app and connect again. |
| `403` | The Ads add-on is off | Turn on the Ads add-on, then connect. |
| `Attentive needs an unhashed email, …` | The event has no plain email, international phone or external id | Send one of them as typed. |

## In this section

<PlatformPages platform="attentive" />

## Related

- [Connect an Attentive account](/connect/connect-attentive-credentials)
- [Send events](/conversions/send-events)
- [Create a forwarding rule](/conversions/create-forwarding-rule)
- [Email, SMS and affiliate destinations](/products/conversions-api/email-sms-affiliates)