# Email, SMS and affiliate destinations

Send the same events to Klaviyo, Attentive, Impact and Awin: what each needs, how events are named and how the affiliate click ids are kept.

Besides ad platforms, your events can go to your email and SMS tool and to your affiliate networks. You connect each one with its keys, then add a forwarding rule like for any destination.

## Connect them

| Destination | Connect with | `destinationId` |
|---|---|---|
| Klaviyo | [A private API key](/connect/connect-klaviyo-credentials) with Events (write) and Accounts (read) | The Klaviyo account id |
| Attentive | [A custom app's API key](/connect/connect-attentive-credentials) with Custom Events and eCommerce write access | The Attentive company id |
| Impact | [An Account SID and Auth Token](/connect/connect-impact-credentials), the program id and the event type id | `<program id>:<event type id>` |
| Awin | [The advertiser id and an API key](/connect/connect-awin-credentials) | The advertiser id |

Each one needs the Ads add-on, like every destination. Then [add a forwarding rule](/conversions/create-forwarding-rule) for the events it should get.

## What each one needs

| Destination | Each event needs | Event names | Dedup on |
|---|---|---|---|
| Klaviyo | An unhashed `email`, a `phone` with its country code, or an `externalId` | `Purchase` is Placed Order, `InitiateCheckout` Started Checkout, `ViewContent` Viewed Product, `AddToCart` Added to Cart; others keep their name | `eventId` as `unique_id` |
| Attentive | An unhashed `email`, a `phone` with its country code, or an `externalId` | `Purchase`, `AddToCart` and `ViewContent` with priced `items` use the eCommerce events; the rest are custom events | `eventId` on custom events. eCommerce events carry none, so an unanswered one is not sent again |
| Impact | `clickIds.irclickid`, an `externalId` or `platformData.promo_code` | Ignored: the event type sets what is counted | `eventId` as `OrderId` |
| Awin | `clickIds.awc` (or `platformData.voucher`), `value` and `currency` | Ignored: `value` goes to the `DEFAULT` commission group | `eventId` as `orderReference` |

Klaviyo and Attentive need the address or number as typed, so a hashed email does not reach them. Impact gets the email SHA-256 hashed. `platformData.order_id` replaces `eventId` as the order id for all four.

## Affiliate click ids

The [Zernio tag](/products/server-side-tracking/script) keeps `irclickid` (Impact) and `awc` (Awin) from the landing URL, like the ad click ids.

Your backend events get them too when you send the visitor id, or the visitor's email, phone or external id.

In the EEA, UK and Switzerland the tag keeps them only after the visitor accepts ad cookies, and an event without consent goes to none of these destinations.

## How it behaves

- Impact and Awin never get browsing or funnel steps such as `ViewContent`, `AddToCart` or `InitiateCheckout`, since they pay a partner for every conversion. A rule turned on in the dashboard sends them `Purchase` only.
- Klaviyo, Attentive and Impact have no test mode: a request with `testCode` is refused. Test against a separate Klaviyo account or an Impact test partner.
- Awin takes `testCode` as `isTest`: the order reaches Awin and is not tracked.
- Zernio checks an Awin key with one test order when you connect it.
- An event whose visitor denied ad user data is not sent to Klaviyo or Attentive. Impact then gets only the click id.

## Related

- [Platforms](/products/conversions-api/platforms): what each ad platform gets.
- [Send events](/products/conversions-api/send): the event and its fields.
- [Consent](/products/server-side-tracking/consent): where consent comes first.