Supported · ready to use
RichAdsMeetROAS
Put the MeetROAS campaign URL into RichAds, then paste the provider-generated conversion settings back into MeetROAS. Choose Custom or Other tracker when no MeetROAS tile is listed.
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.
What to copy and where to paste it
| Copy | Paste into |
|---|---|
| The complete MeetROAS campaign URL containing [CLICK_ID] | RichAds Campaign URL |
| The complete account-generated RichAds postback URL | MeetROAS Campaign → Conversion integrations |
Interface map
Tracking Setup → Main / Approved conversion / Make a Conversion
Paste the complete MeetROAS campaign URLURL must keep[CLICK_ID]
Campaign → Conversion integrations
Create the fixed Main and Approved conversions in one click✓ Finally confirm the conversion in RichAds
What you need
| Provider area | Tracking Setup → Main / Approved conversion / Make a Conversion |
|---|---|
| Click macro | [CLICK_ID] |
| Return method | HTTPS GET Postback |
Main uses https://us.ahows.co/log?action=conversion&key=[CLICK_ID]; Approved uses the same endpoint with action=conversion1.
Setup steps
- Create or open a MeetROAS Campaign whose traffic source is RichAds, then copy the generated campaign URL.
- Use the MeetROAS campaign URL in RichAds; [CLICK_ID] is already included.
- 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.
- 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 the provider does not list a MeetROAS tile, use Custom, Other tracker, or the provider's 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.
- The provider generates the test click and MeetROAS attributes it to the correct source.
- MeetROAS shows the event as received and an identical retry does not create a duplicate.
- 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.