# AdMaven × MeetROAS

Status: supported and ready to use.

## Can I use it?

Ready to use. After saving settings, run a test conversion with your AdMaven account.

- Provider area: Profile → Tracking URL / Conversion Tracking
- Click macro: `{:click_id}`
- Official documentation: https://advertisers-help.ad-maven.com/en/article/how-to-integrate-ad-maven-s2s-conversion-tracking-1secpce/

## What to copy and where to paste it

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

## What you need

Use the account-generated https://pixel-maven.com/pixel?info=<account>&unique_req={externalid}; value={payout} is optional. Add dimension=adp only for the second conversion.

## Setup steps

1. Create or open a MeetROAS Campaign whose traffic source is AdMaven, then copy the generated campaign URL.
2. Use the MeetROAS campaign URL as Destination URL, keeping {:click_id}.
3. Obtain your account URL from Profile → Tracking URL. Omit dimension for Main; use dimension=adp only for the second conversion.
4. Choose the business event, paste the complete account-generated postback URL, then run a test conversion.
5. Paste the campaign URL into Profile → Conversion Tracking and run Test Conversion. Send the mapped event, then Refresh to confirm receipt. The test page exposes no per-event amount and cannot reconcile money.

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

## Events and money

Bind each event manually; there are no one-click defaults. value={payout} receives destination value (revenue), never price (cost). No currency parameter or FX conversion.

## 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 |
| --- | --- | --- | --- |
| AdMaven | value={payout} | — | 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 |
| --- | --- | --- | --- |
| AdMaven | {:click_id} | unique_req={externalid} | Main conversion has no dimension; second conversion uses dimension=adp, never for the first conversion. info comes from the account URL; no one-click defaults |

## How to confirm success

Paste the campaign URL into Profile → Conversion Tracking and run Test Conversion. Send the mapped event, then Refresh to confirm receipt. The test page exposes no per-event amount and cannot reconcile money.

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

## Cautions

- Never use another account's info identifier. Omit value when revenue is absent; never substitute cost.