# TrafficStars × MeetROAS

Status: supported and ready to use.

## Can I use it?

Ready to use. After saving, run one TrafficStars S2S Test and start traffic after the test row shows OK.

- Provider area: Goals & Postbacks → Postback / S2S Test
- Click macro: `{click_id}`
- Official documentation: https://trafficstars.com/faq/articles/how-to-set-up-tracking-conversions

## What to copy and where to paste it

- Copy the complete MeetROAS campaign URL and paste it into: TrafficStars Campaign URL
- Copy the provider account setup and paste it into: MeetROAS Campaign → Conversion integrations

## What you need

Copy the complete TrafficStars-generated Postback URL and keep clickid={click_id}. An Advanced URL may also contain value, price, and lead_code.

## Setup steps

1. Create or open a MeetROAS Campaign whose traffic source is TrafficStars, then copy the generated campaign URL.
2. Create or select a Goal in Goals & Postbacks and choose S2S tracking.
3. If no MeetROAS preset is listed, choose Custom and copy the complete provider-generated Postback URL.
4. Use the MeetROAS campaign URL as the Campaign URL; it already contains {click_id}.
5. In MeetROAS, choose the business event, enter the required TrafficStars Goal ID, and paste that Goal's complete postback URL. The full URL remains visible and editable.
6. Paste the campaign URL into S2S Test and open the one-time test URL. Confirm the send in MeetROAS, then finish only after the TrafficStars test row shows OK.

> If no MeetROAS tile is listed, use Custom, Other tracker, or the generic postback option.

## Events and money

The Goal ID is an external TrafficStars identifier. Bind each MeetROAS event to a Goal explicitly. value receives destination-reported revenue only, price receives cost only, and missing amounts are never inferred.

## 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 |
| --- | --- | --- | --- |
| TrafficStars | value={value} | price={price} | 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 |
| --- | --- | --- | --- |
| 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 |

## How to confirm success

Paste the campaign URL into S2S Test and open the one-time test URL. Confirm the send in MeetROAS, then finish only after the TrafficStars test row shows OK.

Finally, confirm that TrafficStars received the conversion. The provider dashboard is the final result.

## Cautions

- Multiple events for one click require distinct, stable lead_code values; duplicate combinations are ignored.