Supported · ready to use
ExoClickMeetROAS
Put the MeetROAS campaign URL into ExoClick, 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 your conversion settings, run Test Variation and start traffic after ExoClick shows the Goal Count.
What to copy and where to paste it
| Copy | Paste into |
|---|---|
| The complete MeetROAS campaign URL containing {conversions_tracking} | ExoClick Campaign Variation |
| The complete account-generated ExoClick postback URL | MeetROAS Campaign → Conversion integrations |
Interface map
Campaigns → Conversions tracking / Test Variation
Paste the complete MeetROAS campaign URLURL must keep{conversions_tracking}
Campaign → Conversion integrations
Enter the required 32-character Goal ID and paste that Goal's complete S2S URL✓ Finally confirm the conversion in ExoClick
What you need
| Provider area | Campaigns → Conversions tracking / Test Variation |
|---|---|
| Click macro | {conversions_tracking} |
| Return method | HTTPS GET Postback |
Create a Conversion Goal, choose Conversion Tracking API - S2S, and copy the complete URL containing a 32-character lowercase hexadecimal goal and tag={conversions_tracking}.
Setup steps
- Create or open a MeetROAS Campaign whose traffic source is ExoClick, then copy the generated campaign URL.
- Create a Conversion Goal and choose No Value, Fixed, or Dynamic according to whether revenue is required.
- Copy the S2S postback URL for the next step and use the MeetROAS campaign URL as the Campaign Variation.
- In MeetROAS, choose the business event, enter the required 32-character ExoClick Goal ID, and paste that Goal's complete S2S URL. The full URL remains visible and editable.
- Use Test Variation on a paused Direct Link Campaign to obtain a real token and open the campaign URL. After MeetROAS sends the event, check the Goal Count in ExoClick.
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 Goal explicitly to one MeetROAS event. Dynamic Conversion Value is offer payout/revenue and receives Partner Event value only, 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.
| Source | value → | price → | currency / missing-value rules |
|---|---|---|---|
| ExoClick | value={value} | — | 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 |
|---|---|---|---|
| ExoClick | {conversions_tracking} | tag={conversions_tracking} | goal: account-generated 32-character token; no inferred business name or one-click defaults |
How to confirm success
Use Test Variation on a paused Direct Link Campaign to obtain a real token and open the campaign URL. After MeetROAS sends the event, check the Goal Count in ExoClick.
- 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 ExoClick received the conversion. The provider dashboard is the final result.
Cautions
- {conversions_tracking} may be up to 700 characters; every system in the chain must preserve the full token.
- If revenue is returned, compare the actual amount in ExoClick and finish only when it matches.