Supported · ready to use
EvaDavMeetROAS
Put the MeetROAS campaign URL into EvaDav, 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 the conversion settings, run Test conversion tracking and start traffic after the EvaDav test row shows success.
What to copy and where to paste it
| Copy | Paste into |
|---|---|
| The complete MeetROAS campaign URL containing {CLICKID} | EvaDav Campaign URL / test URL |
| The complete account-generated EvaDav postback URL | MeetROAS Campaign → Conversion integrations |
Interface map
Tracking → Test conversion tracking
Paste the complete MeetROAS campaign URLURL must keep{CLICKID}
Campaign → Conversion integrations
Paste the complete EvaDav postback URL; no Goal ID is required✓ Finally confirm the conversion in EvaDav
What you need
| Provider area | Tracking → Test conversion tracking |
|---|---|
| Click macro | {CLICKID} |
| Return method | HTTPS GET Postback |
Use https://evadav.com/phpb?click_id={CLICKID}. Add payout={PAYOUT} only when conversion value must be returned. Other hosts, paths, parameters, and monetary placeholders are rejected.
Setup steps
- Create or open a MeetROAS Campaign whose traffic source is EvaDav, then copy the generated campaign URL.
- Use the MeetROAS campaign URL as the Campaign URL; it already contains {CLICKID}.
- Use payout={PAYOUT} only when conversion value is required; keep the version without payout when no authoritative value exists.
- In MeetROAS, choose the business event and paste the complete EvaDav postback URL; no Goal ID is required. The full URL remains visible and editable.
- Paste the MeetROAS campaign URL into Tracking → Test conversion tracking, then generate and open the test URL. After sending the mapped event, finish only when the EvaDav test row shows a successful conversion. When payout is used, Payout sum must exactly match Partner Event value.
If the provider does not list a MeetROAS tile, use Custom, Other tracker, or the provider's generic postback option.
Events and money
Bind each MeetROAS event explicitly to an EvaDav conversion. payout receives signed destination value only, never price; MeetROAS forwards the decimal unchanged and performs no currency conversion. EvaDav's official campaign-macro table labels {COST} as Conversion payout, so MeetROAS does not import it as ad spend.
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 |
|---|---|---|---|
| EvaDav | payout={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 |
|---|---|---|---|
| EvaDav | {CLICKID} | click_id={CLICKID} | No one-click defaults; bind each event to its account-generated URL |
How to confirm success
Paste the MeetROAS campaign URL into Tracking → Test conversion tracking, then generate and open the test URL. After sending the mapped event, finish only when the EvaDav test row shows a successful conversion. When payout is used, Payout sum must exactly match Partner Event value.
- 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 EvaDav received the conversion. The provider dashboard is the final result.
Cautions
- Do not import {COST} as ad spend; EvaDav currently labels it as Conversion payout. Use fixed cost, CPC/CPM, or CSV for advertising cost.
- The EvaDav postback has no currency parameter. Ensure Partner Event value already uses the reporting currency of your EvaDav account; MeetROAS does not convert it.