# GeeMee × MeetROAS

Status: supported and ready to use.

## Can I use it?

Ready to use. Ask GeeMee to allowlist 157.230.193.182, save your Pixel ID and event settings, then send one test. Start traffic after the GeeMee UI or log shows the matching eid.

- Provider area: GeeMee Event API and account allowlist
- Click macro: `{pixel_click_id}`
- Official documentation: https://interactive.craft.me/n9K3ibIFmD3c6V

## What to copy and where to paste it

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

## What you need

GeeMee does not use a copied URL postback. MeetROAS calls the official Event API through fixed egress 157.230.193.182; one Campaign-level Pixel ID is shared by fixed eid mappings.

## Setup steps

1. Create or open a MeetROAS Campaign whose traffic source is GeeMee, then copy the generated campaign URL.
2. Use the MeetROAS campaign URL in GeeMee; it contains pixel_click_id={pixel_click_id}.
3. Ask GeeMee to allowlist 157.230.193.182.
4. In MeetROAS, create all fixed eid defaults in one click; mapping creation does not require saving the Pixel ID first. The Pixel ID remains visible and editable, and only ambiguous event meanings need an individual revoke-and-replace.
5. Use GeeMee's test tool to generate a real pixel_click_id and open the campaign URL, then confirm the matching eid in the GeeMee UI or log.

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

## Events and money

Choose only from MeetROAS' fixed eid list. EVENT_PWA_INSTALL means tapping the install control and initiating the flow; it does not claim completion. Ambiguous events require an explicit buyer choice; test again after changing the Pixel ID.

## 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 |
| --- | --- | --- | --- |
| GeeMee | data.value | — | data.currency; send both value and currency or 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.

| Source | Campaign macro / parameter | Outgoing click field | Event / Goal mapping |
| --- | --- | --- | --- |
| GeeMee | {pixel_click_id} | pixel_click_id | eid uses the defaults below; pixel_id comes from the account. Alternatives require manual selection |

## 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_key | GeeMee |
| --- | --- |
| landing_view | EVENT_CONTENT_VIEW |
| install_click | — |
| install_prompt_accepted | EVENT_PWA_INSTALL |
| pwa_install | — |
| pwa_open_attempt | — |
| pwa_first_open | EVENT_PWA_ACTIVATE |
| account_registration | EVENT_COMPLETE_REGISTRATION |
| first_deposit | EVENT_FIRST_DEPOSIT (alternative: EVENT_FTD) |
| first_day_deposit | EVENT_FIRST_DAY_PURCHASE |
| deposit | EVENT_PURCHASE (alternative: EVENT_REPEAT_PURCHASE) |
| login | EVENT_LOGIN |

## How to confirm success

Use GeeMee's test tool to generate a real pixel_click_id and open the campaign URL, then confirm the matching eid in the GeeMee UI or log.

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

## Cautions

- Do not send browser parameters or invented eid values directly to GeeMee; MeetROAS sends events from its fixed-egress server.