中文
Documentation menu

Traffic source integrations/Adsterra

Supported · ready to use

AAdsterraMeetROAS

Put the MeetROAS campaign URL into Adsterra, 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. Save your conversion settings and complete a test before starting traffic.

What to copy and where to paste it

CopyPaste into
The complete MeetROAS campaign URL containing ##SUB_ID_SHORT(action)##Adsterra Campaign Landing URL
The complete account-generated Adsterra postback URLMeetROAS Campaign → Conversion integrations

Interface map

AAdsterra

Conversion tracking → S2S → Test

1
Adsterra Campaign Landing URLPaste the complete MeetROAS campaign URL

URL must keep##SUB_ID_SHORT(action)##

MeetROAS

Campaign → Conversion integrations

2
Event conversion settingChoose the business event and paste the complete postback URL

✓ Finally confirm the conversion in Adsterra

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

What you need

Provider areaConversion tracking → S2S → Test
Click macro##SUB_ID_SHORT(action)##
Return methodHTTPS GET Postback

Copy the complete account-generated www.pbterra.com postback URL, retaining subid_short={clickid} and optional atpay={payout}.

Setup steps

  1. Create or open a MeetROAS Campaign whose traffic source is Adsterra, then copy the generated campaign URL.
  2. Use the MeetROAS campaign URL as Landing URL so ##SUB_ID_SHORT(action)## reaches MeetROAS with a real click.
  3. Copy the S2S postback URL from Conversion tracking. Omit event for the main conversion; enable Multi-event for extra conversions.
  4. Choose the corresponding business event in MeetROAS and paste the complete account-generated URL. Retain the matching event1/event2/event3 for an extra conversion.
  5. Start the test in MeetROAS, paste its test campaign URL into CHECK URL, and run MAKE A TEST CONVERSION. Confirm in MeetROAS after the provider CHECK STATUS shows Valid.

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

Events and money

The main conversion omits event. Extra conversions use event1, event2, or event3 and require Multi-event on the campaign. atpay is conversion cost: it receives Partner Event price, never revenue value.

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

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

How to confirm success

Start the test in MeetROAS, paste its test campaign URL into CHECK URL, and run MAKE A TEST CONVERSION. Confirm in MeetROAS after the provider CHECK STATUS shows Valid.

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

Cautions

  • Without price, atpay is omitted. /name/ URLs use USD; /code/ URL currency must match the event. No automatic currency conversion occurs.
  • Extra events are unpaid by default; follow Adsterra's instructions and contact its support for paid multi-events.

Continue