# Kadam × MeetROAS

Status: supported and ready to use.

## Can I use it?

Ready to use with verified end-to-end delivery. Save the fixed postback and Global event; each account should still run Test conversion with its own campaign and reconcile it in Conversion Details.

- Provider area: Campaign creative menu → Test conversion / Conversion Details
- Click macro: `{click_id}`
- Official documentation: https://wiki.kadam.net/en/index.php?title=API_setting

## What to copy and where to paste it

- Copy the complete MeetROAS campaign URL and paste it into: Kadam Campaign URL
- Copy the provider account setup and paste it into: MeetROAS Campaign → Conversion integrations

## What you need

Use exactly https://kdtrk.net/ru/postback/?data={click_id}. MeetROAS rejects legacy hosts, extra parameters, status, and all monetary fields.

## Setup steps

1. Create or open a MeetROAS Campaign whose traffic source is Kadam, then copy the generated campaign URL.
2. Paste the MeetROAS campaign URL into Kadam and keep {click_id}.
3. Run Test conversion from the campaign creative menu; open the link incognito and find the Test row in Conversion Details.
4. Use the fixed postback and create pwa_install → Global in one click.
5. A Kadam official test click entered the DEMO Campaign. The production account_registration returned 202 first, an identical retry returned 200 duplicate, and a conflicting request returned 409. MeetROAS stored exactly one event and one HTTP 200 delivery; Kadam Conversion Details showed the single Test conversion for Campaign 958214 and Ad 7997066. The postback has no monetary field, so monetary reconciliation is not required.

> If no MeetROAS tile is listed, use Custom, Other tracker, or the generic postback option.

## Events and money

Each campaign permits one Global binding, defaulting to pwa_install. The postback projects no value, price, or currency; {cpc} is only for campaign-URL cost capture.

## Destination money → upstream parameter reference

Direction: destination → MeetROAS Partner Event API → attributed source. value is revenue; price is acquisition cost; currency is declared by the destination. — means this MeetROAS connector does not project that field, not that the upstream lacks it. URL money columns show optional template placeholders: replace only when both template parameter and destination amount exist; omit when the amount is absent. No automatic parameter insertion, substitution between amounts, or FX conversion. Registration and login cannot carry money.

| Source | value → | price → | currency / missing-value rules |
| --- | --- | --- | --- |
| Kadam | — | — | No currency projection or FX conversion |

## Click, Goal and slot defaults

The upstream expands the campaign macro into a real click ID, which MeetROAS returns; it is not the destination's mrc_. These are defaults for new bindings; existing manual bindings are not overwritten. Obtain account identifiers and URLs from each provider; never infer events from slot numbers or tokens.

| Source | Campaign macro / parameter | Outgoing click field | Event / Goal mapping |
| --- | --- | --- | --- |
| Kadam | {click_id} | data={click_id} | pwa_install → Global; one binding per Campaign. The postback carries no status, cost, payout, or currency; the campaign URL may separately capture click cost with {cpc} |

## How to confirm success

A Kadam official test click entered the DEMO Campaign. The production account_registration returned 202 first, an identical retry returned 200 duplicate, and a conflicting request returned 409. MeetROAS stored exactly one event and one HTTP 200 delivery; Kadam Conversion Details showed the single Test conversion for Campaign 958214 and Ad 7997066. The postback has no monetary field, so monetary reconciliation is not required.

Finally, confirm that Kadam received the conversion. The provider dashboard is the final result.

## Cautions

- Do not add status, cost, payout, or currency. Official documentation versions conflict on these fields, so the connector rejects all of them.