# Choose the ad accounts

Pick which ad accounts receive your website's conversions, and where in each one they land: a pixel, a dataset or a conversion action.

Each ad account a website sends to has one switch and one destination: the pixel, dataset or conversion action that records its conversions.

## Switch an ad account on

The one click links the ad accounts you picked when you connected each platform. Every other ad account on the profile appears under **Destinations** with a switch.

Turn on **Send conversions to** an account, and its website conversions start at the next event. An account connected later shows **Connected after your sites were set up** until you switch it on.

## Choose where it sends

Zernio picks the account's purchase pixel or conversion action. Open **Choose where it sends** to pick another.

If the account has none, Zernio creates one when you switch it on:

| Platform | What Zernio creates |
|---|---|
| <PlatformName slug="meta-ads" /> | A pixel named **Zernio** |
| <PlatformName slug="google-ads" /> | A conversion action named **Purchase (Zernio)**, counted as a secondary goal until you make it primary |
| Other platforms | Nothing: create a pixel or conversion action on the platform first |

## Send to Google Analytics 4

A GA4 web stream can receive your conversions too, as `purchase`, `generate_lead` and `sign_up`. Connect <PlatformName slug="google-analytics" /> and switch on the stream.

Zernio creates a Measurement Protocol API secret named **Zernio** on the stream. If the connection cannot, paste one from GA4 **Admin**, **Data streams**, **Measurement Protocol API secrets**.

## Send to AppLovin

Connect <BrandName icon="AppLovin" name="AppLovin" /> with the **Event Key** and **Conversion API key** from Axon Ads Manager, under **Account**, **Keys**. The Event Key is the destination, so each connection has exactly one.

## What each platform gets

Each platform matches a website conversion to its ad with what the tag collected. A visitor you [identify](/products/server-side-tracking/script#identify-the-visitor) matches far better.

| Platform | Receives | Matched on |
|---|---|---|
| <PlatformName slug="meta-ads" /> | `Purchase`, `Lead`, `CompleteRegistration` | `fbc` from the ad click, `fbp`, IP and user agent, identified email and phone |
| <PlatformName slug="google-ads" /> | The conversion action's own type | `gclid`, `gbraid` or `wbraid`, identified email and phone |
| <PlatformName slug="tiktok-ads" /> | `Purchase`, `Lead`, `CompleteRegistration` | Identified email or phone, needed on every event |
| <PlatformName slug="linkedin-ads" /> | The conversion rule's own type | `li_fat_id`, identified email, needed when there is no click |
| <PlatformName slug="pinterest-ads" /> | Pinterest's names, such as `checkout` and `lead` | `epik`, IP and user agent, identified email |
| <PlatformName slug="reddit-ads" /> | Reddit's standard names | `rdt_cid`, `rdt_uuid`, IP and user agent |
| <PlatformName slug="openai-ads" /> | OpenAI's standard names | IP and user agent, identified email |
| <PlatformName slug="google-analytics" /> | `purchase`, `generate_lead`, `sign_up` | The `_ga` client id |
| <BrandName icon="AppLovin" name="AppLovin" /> | `Purchase`, `Lead`, `CompleteRegistration` | `aleid` from the ad click, the `_axwrt` cookie |

Identified fields are hashed before they leave Zernio. What each platform reads from an event is on [Platforms](/products/conversions-api/platforms).

## Choose with the API

Each switch is a [forwarding rule](/products/conversions-api#choose-where-events-go). To send only website events to a destination, create the rule with `sources`:

```bash
curl -X POST "https://zernio.com/api/v1/events/forwarding-rules" \
  -H "Authorization: Bearer $ZERNIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "profileId": "66a1f0c2a4b9d3e8f1a2b3c4",
    "accountId": "66b2e19d8c3f5a7e9d0b1c2d",
    "destinationId": "1234567890123456",
    "sources": ["web"]
  }'
```

A rule without `sources` sends events from every source: the website, your backend, lead forms and stores. Switch an account off with `DELETE /v1/events/forwarding-rules/{ruleId}`.

## How it behaves

- **One destination per ad account.** Choosing another replaces the first.
- **Shared pixels.** When two ad accounts send to the same pixel, switching one off asks before stopping both.
- **Every site of the profile.** A rule sends conversions from all of the profile's websites. Use one profile per brand to keep them apart.

## If it fails

| Problem | Cause | Fix |
|---|---|---|
| The account's check says it has no pixel or conversion action | The platform has nothing to send to, and Zernio cannot create one there | Create a pixel or conversion action on the platform, then switch the account on again |
| **Fix** next to an account | Its sends are failing, often after a password change or lost access | Reconnect the ad account |
| GA4 stream listed as inactive | It has no Measurement Protocol API secret | Reconnect Google Analytics, or paste a secret |

## Related

- [Platforms](/products/conversions-api/platforms)
- [Count each conversion once](/products/server-side-tracking/deduplication)
- [Test and verify](/products/server-side-tracking/verify)