# RichAds × MeetROAS

Status: supported and ready to use.

## Can I use it?

Ready to use. After saving your conversion settings, run Make a Conversion and start traffic after RichAds shows the new conversion.

- Provider area: Tracking Setup → Main / Approved conversion / Make a Conversion
- Click macro: `[CLICK_ID]`
- Official documentation: https://docs.richads.com/advertiser/overview

## What to copy and where to paste it

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

## What you need

Main uses https://us.ahows.co/log?action=conversion&key=[CLICK_ID]; Approved uses the same endpoint with action=conversion1.

## Setup steps

1. Create or open a MeetROAS Campaign whose traffic source is RichAds, then copy the generated campaign URL.
2. Use the MeetROAS campaign URL in RichAds; [CLICK_ID] is already included.
3. In MeetROAS, create the fixed Main and Approved conversions in one click: PWA install defaults to Main and first deposit defaults to Approved. If the business meaning differs, revoke and replace only the ambiguous binding. The fixed URLs remain fully visible and editable.
4. Use Tracking Setup → Make a Conversion to open the MeetROAS campaign URL. After MeetROAS shows the send, finish only when the RichAds conversion counter increases.

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

## Events and money

Each campaign has at most one Main and one Approved conversion. MeetROAS defaults PWA install to Main and first deposit to Approved; neither has a Goal ID or monetary field.

## 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 |
| --- | --- | --- | --- |
| RichAds | — | — | 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 |
| --- | --- | --- | --- |
| RichAds | [CLICK_ID] | key=[CLICK_ID] | pwa_install → action=conversion; first_deposit → action=conversion1 (Approved). One binding per slot |

## How to confirm success

Use Tracking Setup → Make a Conversion to open the MeetROAS campaign URL. After MeetROAS shows the send, finish only when the RichAds conversion counter increases.

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

## Cautions

- Approved is RichAds' second fixed conversion, not an arbitrarily named or repeatable Goal.