中文
Documentation menu

Traffic source integrations

Send destination events back to ad platforms

Every platform below is supported and ready to use. If MeetROAS is not listed as a tile, choose Custom or Other tracker; each guide shows exactly what to copy and where to paste it.

Supported platforms ready to use

Send one test conversion after setup. The traffic-source dashboard is the final confirmation of success.

Shared flow

  1. Select the correct traffic source on the MeetROAS Campaign.
  2. Copy the MeetROAS campaign URL that already contains the provider click macro.
  3. Obtain the account-specific postback from the ad platform, or save the account settings for an Event API connector.
  4. Follow the page to create defaults in one click, or bind events individually only when the provider requires it.
  5. Confirm the conversion in the traffic-source dashboard; its result is final.

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
Meta (Facebook CAPI)data[].custom_data.value—data[].custom_data.currency; Send money only when both value and currency exist; no FX conversion
TikTok Events APIdata[].properties.value—data[].properties.currency; Send money only when both value and currency exist; no FX conversion
TrafficStarsvalue={value}price={price}No currency projection or FX conversion
PropellerAdspayout=${PAYOUT}—No currency projection or FX conversion
RichAds——No currency projection or FX conversion
ExoClickvalue={value}—No currency projection or FX conversion
Adsterra—atpay={payout}/name/.../at means USD; /code/CCC/.../at means CCC. No currency parameter; reject an explicit currency conflicting with the URL; no FX conversion
BidVertiserrevenue={REVENUE}—No currency projection or FX conversion
HilltopAds—price={{price}}currency={{currency}} is passed through; template must also contain price. Missing price removes both; missing currency removes currency only; no FX conversion
EvaDavpayout={PAYOUT}—No currency projection or FX conversion
AdMavenvalue={payout}—No currency projection or FX conversion
AdsGram——No currency projection or FX conversion
Kadam——No currency projection or FX conversion
GeeMeedata.value—data.currency; send both value and currency or data={}; no FX conversion
MGSkyAdsdata.value—data.currency; first_deposit / deposit require both value and currency or are rejected; first_day_deposit allows the pair or data={}; other events accept only data={}; no 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
Meta (Facebook CAPI)fbcliddata[].user_data.fbc ← fb.1.<clickObservedAtMs>.<fbclid>data[].event_name uses the defaults below
TikTok Events APIttcliddata[].user.ttcliddata[].event uses the defaults below; custom events are not used for Campaign optimization
TrafficStars{click_id}clickid={click_id}goalid: account Goal ID, manually bound per event; no one-click defaults. lead_code={lead_code} uses a stable opaque MeetROAS event identity
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
RichAds[CLICK_ID]key=[CLICK_ID]pwa_install → action=conversion; first_deposit → action=conversion1 (Approved). One binding per slot
ExoClick{conversions_tracking}tag={conversions_tracking}goal: account-generated 32-character token; no inferred business name or one-click defaults
Adsterra##SUB_ID_SHORT(action)##subid_short={clickid}Main conversion has no event; other slots use event=event1 / event2 / event3. Slots have no business meaning; no one-click defaults
BidVertiser{BV_CLICKID}CLICKID={BV_CLICKID}pwa_install → Global (no Goal); one binding per Campaign; the upstream ignores repeated conversions for the same click
HilltopAds{{ctoken}}token={{ctoken}}With no existing Main: pwa_install → Main (no goal), other public events → Micro (goal=<event_key>). With an existing Main, all new defaults use Micro
EvaDav{CLICKID}click_id={CLICKID}No one-click defaults; bind each event to its account-generated URL
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
AdsGram{record_data}record={record_data}account_registration → goaltype=1; first_deposit → goaltype=2; deposit → goaltype=3. The token comes from the AdsGram account; one binding per slot
Kadam{click_id}data={click_id}pwa_install → Global; one binding per Campaign. The postback carries no status, cost, payout, or currency; the campaign URL may separately capture click cost with {cpc}
GeeMee{pixel_click_id}pixel_click_ideid uses the defaults below; pixel_id comes from the account. Alternatives require manual selection
MGSkyAds{pixel_click_id}pixel_click_ideid uses the defaults below; pixel_id comes from the account. Events without a mapping do not get a binding

Event API one-click defaults

The first six rows are MeetROAS browser / PWA events. The destination Partner Event API accepts only account_registration, first_deposit, first_day_deposit, deposit and login. — means no mapping and no automatic binding. Recommendations are optional: manual settings allow the provider catalog and supported custom names; alternatives shown here are examples, not the complete catalog. standard / custom indicates the upstream event type. pwa_open is a hidden runtime event, not a one-click default or public Goal choice; do not confuse it with pwa_first_open.

MeetROAS event_keyMeta (Facebook CAPI)TikTok Events APIGeeMeeMGSkyAds
landing_viewViewContent (standard)ViewContent (standard)EVENT_CONTENT_VIEW—
install_clickInstallClick (custom)InstallClick (custom)—EVENT_PWA_INSTALL
install_prompt_acceptedInstallPromptAccepted (custom)InstallPromptAccepted (custom)EVENT_PWA_INSTALL—
pwa_installPWAInstall (custom)Download (standard)——
pwa_open_attempt———EVENT_PWA_OPEN
pwa_first_openPWAFirstOpen (custom)PWAFirstOpen (custom)EVENT_PWA_ACTIVATEEVENT_PWA_ACTIVATE
account_registrationCompleteRegistration (standard)CompleteRegistration (standard)EVENT_COMPLETE_REGISTRATIONEVENT_COMPLETE_REGISTRATION
first_depositFirstDeposit (custom)FirstDeposit (custom)EVENT_FIRST_DEPOSIT (alternative: EVENT_FTD)EVENT_FIRST_DEPOSIT
first_day_depositFirstDayDeposit (custom)FirstDayDeposit (custom)EVENT_FIRST_DAY_PURCHASE—
depositPurchase (standard)Purchase (standard)EVENT_PURCHASE (alternative: EVENT_REPEAT_PURCHASE)EVENT_PURCHASE
loginLogin (custom)Login (custom)EVENT_LOGIN—