# AdsGram × MeetROAS

Status: supported and ready to use.

## Can I use it?

Ready to use. Save your AdsGram token and create the fixed event defaults; after the next Web Landing Campaign runs, you can reconcile conversions in Statistics.

- Provider area: Campaign → Web Landing Link; the account token is in the AdsGram advertiser account
- Click macro: `{record_data}`
- Official documentation: https://docs.adsgram.ai/advertiser/tracking

## What to copy and where to paste it

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

## What you need

Use https://api.adsgram.ai/confirm_conversion with your own account token. MeetROAS keeps record={record_data}; the token is encrypted and never displayed again.

## Setup steps

1. Create or open a MeetROAS Campaign whose traffic source is AdsGram, then copy the generated campaign URL.
2. Create a Web Landing Campaign and place the MeetROAS campaign URL in Web Landing Link; the URL already contains {record_data}.
3. Obtain the token from the AdsGram advertiser account; MeetROAS derives goaltype 1, 2, and 3 from one URL.
4. In MeetROAS, paste the complete Conversion Confirmation URL containing your token, then create the registration, first deposit/purchase, and repeat deposit/purchase defaults in one click.
5. Request shape, event mapping, HTTP 200 success classification, and retry dedupe were verified against AdsGram's official documentation; this is not funded-traffic end-to-end proof. After running traffic, you can reconcile actual conversions in AdsGram Statistics.

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

## Events and money

One-click defaults are registration → goaltype=1, first deposit/purchase → goaltype=2, and repeat deposit/purchase → goaltype=3. The official API has no value, price, or currency field, so MeetROAS neither infers nor sends money.

## 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 |
| --- | --- | --- | --- |
| AdsGram | — | — | 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 |
| --- | --- | --- | --- |
| 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 |

## How to confirm success

Request shape, event mapping, HTTP 200 success classification, and retry dedupe were verified against AdsGram's official documentation; this is not funded-traffic end-to-end proof. After running traffic, you can reconcile actual conversions in AdsGram Statistics.

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

## Cautions

- Telegram Ads Campaigns do not pass AdsGram macros and cannot use this Conversion Confirmation API; use a Web Landing Link.
- Only HTTP 200 means AdsGram accepted the conversion; other 2xx responses are not treated as success.