# Conversion mapping

Group platform conversions into one reporting taxonomy, so you can review Meta and Google performance side by side in Soku.

# Conversion mapping

Conversion names are a mess across platforms. The same business goal might be tracked as `Lead` in one Meta campaign, `CompleteRegistration` in another, `Submit lead form` on Google Search, and `Sign-up` on PMax. Conversion mapping fixes that — you group all of those into the categories you actually want in your reports, so Meta and Google line up side by side.

> This defines your reporting taxonomy. It is **not** used to evaluate lead quality.

## Why it matters

The same objective, tracked four different ways, becomes one clean column:

| In ad platforms | In Soku reports |
|---|---|
| Meta — `Lead` | Sign-up / Acquisition |
| Meta — `CompleteRegistration` | Sign-up / Acquisition |
| Google Search — `Submit lead form` | Sign-up / Acquisition |
| Google PMax — `Sign-up` | Sign-up / Acquisition |

Map it once, and every report uses the same columns across platforms and campaigns.

## Before you start

Have these ready:

1. **The categories you want in reports** — e.g. Sign-up / Acquisition, Purchase / Paid, Booking / Inquiry.
2. **Your existing conversions on each platform** — Meta events / custom conversions, and Google Ads conversion actions.
3. **Which category each conversion belongs to** — multiple conversions can map to the same category.

> **Prerequisite:** your ad accounts must be connected so their conversion actions flow into Soku. See [Connecting accounts](/docs/connecting-accounts).

## Open the conversion group editor

From the **Dashboard**, click **Conversion Groups** in the top-right toolbar. A conversion group is one reporting category plus the rules and platform conversions that feed it.

There are two ways to set one up:

- **Set up with Soku** — the quickest route if you are not sure where to start. Soku opens a chat, looks at the conversion events your ad accounts actually report, suggests which events belong in which group, and confirms each group with you before anything is applied.
- **New group** (or **Set up manually** when you have no groups yet) — the step-by-step editor described below.

The editor walks through five steps — **Events → Basics → KPI Requirements → Goals → Review** — and you can jump back into any step from the Review screen.

![The conversion group editor, showing the Basics spec and selected conversion actions on the Review screen](https://cdn.soku.ai/marketing/images/docs/conversion-mapping/editor-overview.png)

## Step 1 — Events

This is the heart of mapping: pick which platform conversions count toward this group.

1. Optionally pick a preset under **What are you measuring?** — New User Sign-up, Qualified New User, High Value Action, Payment Success, or App Installation. A preset fills in the name and metric labels on the next step; you can still change them.
2. Events your accounts reported in the **last 30 days** are listed first, busiest first, with the number of conversions each one reported. Events with no recent conversions are listed underneath. If you only recognize two or three of your events, those are usually the ones at the top.
3. Filter by **All / Google / Meta** to narrow the list. Each row is a real conversion action from your connected accounts, tagged with its type — `SIGNUP`, `PURCHASE`, `LEAD`, `DEFAULT`, etc. — and the account it belongs to.
4. **Check the events** that belong in this group. For a Sign-up / Acquisition group, you might select Meta's `Complete Registration` and Google's `(web) signup` together. A header shows how many are selected.

![Selecting conversion actions — each row is tagged SIGNUP, PURCHASE, LEAD, or DEFAULT, with a counter showing how many are selected](https://cdn.soku.ai/marketing/images/docs/conversion-mapping/select-actions.png)

> One group can include many conversions across both platforms — that's how four different platform names collapse into a single reporting category.

### Attribution window per platform

Once a Meta event is selected, you can set Meta's attribution window (e.g. `7d_click_1d_view`). For **GA4-imported sources the window is display-only** — the source of truth lives in the GA4 backend.

## Step 2 — Basics

Name the group and decide what it reports:

- **Name and priority** — a short name (e.g. `NU` for new users) and a priority (`P0` / `P1` / `P2`). `P0` groups appear on the Dashboard's summary cards, at most two per brand.
- **Metrics to compute** — the labels for the KPIs this group reports, such as `CP-NU`, `Reg Rate`, `Pur Value`, and `ROAS`. Leave a label blank to hide that metric.
- **Advanced** — how conversions are dated (by conversion time or click time), which count to use, and whether to count conversion value. The defaults fit most accounts; open this only if you need to match another report. The count-source choice is not shown for Meta-only groups, where it has no effect.

## Steps 3–5 — KPI Requirements, Goals, Review

The remaining steps let you set KPI thresholds and goals for the group, then **Review** everything on one screen. Use the inline **Edit** on any section to adjust it without stepping backward, then **Save Changes**.

Once saved, the group's conversions are unified — your reports and dashboard use the same conversion columns across every platform and campaign.

> **Tip:** Start from the categories you want to show in reports, then map existing platform conversions into them — not the other way around.