中文
Documentation menu

Traffic source integrations/AdMaven

Supported · ready to use

AMAdMavenMeetROAS

Put the MeetROAS campaign URL into AdMaven, 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 settings, run a test conversion with your AdMaven account.

What to copy and where to paste it

CopyPaste into
The complete MeetROAS campaign URL containing {:click_id}Campaign Destination URL
The complete account-generated AdMaven postback URLMeetROAS Campaign → Conversion integrations

Interface map

AMAdMaven

Profile → Tracking URL / Conversion Tracking

1
Campaign Destination URLPaste the complete MeetROAS campaign URL

URL must keep{:click_id}

MeetROAS

Campaign → Conversion integrations

2
Event conversion settingComplete AdMaven postback URL

✓ Finally confirm the conversion in AdMaven

Interface map: first place the campaign URL in AdMaven, then save the conversion settings in MeetROAS. The provider's UI appearance may change.

What you need

Provider areaProfile → Tracking URL / Conversion Tracking
Click macro{:click_id}
Return methodHTTPS GET Postback

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 the provider does not list a MeetROAS tile, use Custom, Other tracker, or the provider's 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.

Sourcevalue →price →currency / missing-value rules
AdMavenvalue={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.

SourceCampaign macro / parameterOutgoing click fieldEvent / 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.

  • 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 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.

Continue