中文
Documentation menu

Traffic source integrations/PropellerAds

Supported · ready to use

PPropellerAdsMeetROAS

Put the MeetROAS campaign URL into PropellerAds, 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, run one Test conversion and confirm that PropellerAds registers it.

What to copy and where to paste it

CopyPaste into
The complete MeetROAS campaign URL containing ${SUBID}PropellerAds Target URL
The complete account-generated PropellerAds postback URLMeetROAS Campaign → Conversion integrations

Interface map

PPropellerAds

Tracking → Other tracker or CPA network

1
PropellerAds Target URLPaste the complete MeetROAS campaign URL

URL must keep${SUBID}

MeetROAS

Campaign → Conversion integrations

2
Event conversion settingPaste the Main postback URL once and create Main, Goal 2, and Goal 3 in one click

✓ Finally confirm the conversion in PropellerAds

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

What you need

Provider areaTracking → Other tracker or CPA network
Click macro${SUBID}
Return methodHTTPS GET Postback

Copy the complete account URL on ad.propellerads.com/conversion.php and keep aid, tid, and visitor_id=${SUBID}. Keep payout=${PAYOUT} only when conversion revenue is required.

Setup steps

  1. Create or open a MeetROAS Campaign whose traffic source is PropellerAds, then copy the generated campaign URL.
  2. Open Tracking and choose Other tracker or CPA network; a native tile is not required.
  3. Copy the account-generated Main postback URL; MeetROAS derives Main, Goal 2, and Goal 3 from this one URL.
  4. Paste the MeetROAS campaign URL into the PropellerAds Target URL; ${SUBID} is already included.
  5. In MeetROAS, paste the Main postback URL once, then create the Main, Goal 2, and Goal 3 defaults in one click. Revoke and replace only the individual binding whose business meaning differs. Every full URL remains visible and editable.
  6. Paste the MeetROAS campaign URL into Tracking → Test conversion and open the Test Banner. Confirm the send in MeetROAS and wait for PropellerAds to register the conversion.

If the provider does not list a MeetROAS tile, use Custom, Other tracker, or the provider's generic postback option.

Events and money

No goal parameter means Main conversion; goal=2 and goal=3 are secondary levels. Only Main affects CPA Goal optimization. payout receives destination value, 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.

Sourcevalue →price →currency / missing-value rules
PropellerAdspayout=${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
PropellerAds${SUBID}visitor_id=${SUBID}pwa_install → Main (no goal); account_registration → goal=2; first_deposit → goal=3. One binding per slot; only Main is used for CPA optimization

How to confirm success

Paste the MeetROAS campaign URL into Tracking → Test conversion and open the Test Banner. Confirm the send in MeetROAS and wait for PropellerAds to register the conversion.

  • 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 PropellerAds received the conversion. The provider dashboard is the final result.

Cautions

  • Do not assume fixed business meanings for Main, goal=2, or goal=3; your MeetROAS bindings define the actual events.
  • The provider notes that conversion statistics may take up to 24 hours to update.

Continue