# BidVertiser × MeetROAS

Status: supported and ready to use.

## Can I use it?

Ready to use. After saving your conversion settings, run Test Postbacks and start traffic after Recent Test Conversions shows OK.

- Provider area: Manage Postbacks → Global Postback / Test Postbacks
- Click macro: `{BV_CLICKID}`
- Official documentation: https://zendesk.bidvertiser.com/hc/en-us/articles/360009414399-Global-Postback

## What to copy and where to paste it

- Copy the complete MeetROAS campaign URL and paste it into: BidVertiser Edit Ad destination URL
- Copy the provider account setup and paste it into: MeetROAS Campaign → Conversion integrations

## What you need

Copy the complete Global Postback generated by Manage Postbacks. It must contain ver=1.0, a numeric AID, and CLICKID={BV_CLICKID}. revenue={REVENUE} is optional.

## Setup steps

1. Create or open a MeetROAS Campaign whose traffic source is BidVertiser, then copy the generated campaign URL.
2. Use the MeetROAS campaign URL in Edit Ad so {BV_CLICKID} reaches MeetROAS on a real click.
3. Generate and copy the complete Global Postback in Manage Postbacks.
4. In MeetROAS, paste the complete Global Postback once and create PWA install as the sole conversion in one click. If the primary goal differs, revoke it and select one replacement event. The full URL remains visible and editable.
5. First ensure the campaign URL contains {BV_CLICKID}, then run Test Postbacks. Check the send in MeetROAS and confirm OK in Recent Test Conversions.

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

## Events and money

Global Postback has no external Goal selector, and repeated conversions for one Click ID are ignored; bind one MeetROAS event per campaign. revenue receives destination value only, never price.

## 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 |
| --- | --- | --- | --- |
| BidVertiser | revenue={REVENUE} | — | 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 |
| --- | --- | --- | --- |
| BidVertiser | {BV_CLICKID} | CLICKID={BV_CLICKID} | pwa_install → Global (no Goal); one binding per Campaign; the upstream ignores repeated conversions for the same click |

## How to confirm success

First ensure the campaign URL contains {BV_CLICKID}, then run Test Postbacks. Check the send in MeetROAS and confirm OK in Recent Test Conversions.

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

## Cautions

- Do not invent a Goal ID or replace AID; AID must come from the BidVertiser account, and the Global conversion is not a multi-stage funnel.