Supported · ready to use
MGSkyAdsMeetROAS
Put the MeetROAS campaign URL into MGSkyAds, 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. MeetROAS always sends from 157.230.193.182; provide that IP to MGSkyAds, save your Pixel ID and event settings, then send one test. Start traffic after the provider UI or log shows the matching eid.
What to copy and where to paste it
| Copy | Paste into |
|---|---|
| The complete MeetROAS campaign URL containing {pixel_click_id} | MGSkyAds Campaign URL |
| Create the fixed MGSkyAds eid defaults in one click; the Pixel ID remains visible and editable | MeetROAS Campaign → Conversion integrations |
Interface map
MGSkyAds Event API and server IP setup
Paste the complete MeetROAS campaign URLURL must keep{pixel_click_id}
Campaign → Conversion integrations
Create the fixed MGSkyAds eid defaults in one click; the Pixel ID remains visible and editable✓ Finally confirm the conversion in MGSkyAds
What you need
| Provider area | MGSkyAds Event API and server IP setup |
|---|---|
| Click macro | {pixel_click_id} |
| Return method | Server Event API |
MGSkyAds does not use a copied URL postback. MeetROAS always 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
- Create or open a MeetROAS Campaign whose traffic source is MGSkyAds, then copy the generated campaign URL.
- Use the MeetROAS campaign URL in MGSkyAds; it contains pixel_click_id={pixel_click_id}.
- Provide MGSkyAds with MeetROAS fixed egress 157.230.193.182; every request uses this IP whether or not an allowlist is enabled.
- In MeetROAS, create all fixed MGSkyAds eid defaults in one click; mapping creation does not require saving the Pixel ID first. The Pixel ID remains visible and editable.
- Use MGSkyAds' test tool to generate a real pixel_click_id and open the campaign URL, then confirm the matching eid in the MGSkyAds UI or log.
If the provider does not list a MeetROAS tile, use Custom, Other tracker, or the provider's generic postback option.
Events and money
Recommended mappings: install control tap → EVENT_PWA_INSTALL; attempted PWA open tap → EVENT_PWA_OPEN; first successful open → EVENT_PWA_ACTIVATE; registration, first deposit, and deposit → EVENT_COMPLETE_REGISTRATION, EVENT_FIRST_DEPOSIT, and EVENT_PURCHASE. The attempted-open tap is the pwa_open_attempt event; do not substitute completed installation or an observed launch. The downstream must supply value/currency for deposit amounts.
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 |
|---|---|---|---|
| MGSkyAds | data.value | — | data.currency; first_deposit / deposit require both value and currency or are rejected; first_day_deposit allows the pair or data={}; other events accept only 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 |
|---|---|---|---|
| MGSkyAds | {pixel_click_id} | pixel_click_id | eid uses the defaults below; pixel_id comes from the account. Events without a mapping do not get a binding |
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 | MGSkyAds |
|---|---|
| landing_view | — |
| install_click | EVENT_PWA_INSTALL |
| install_prompt_accepted | — |
| pwa_install | — |
| pwa_open_attempt | EVENT_PWA_OPEN |
| pwa_first_open | EVENT_PWA_ACTIVATE |
| account_registration | EVENT_COMPLETE_REGISTRATION |
| first_deposit | EVENT_FIRST_DEPOSIT |
| first_day_deposit | — |
| deposit | EVENT_PURCHASE |
| login | — |
How to confirm success
Use MGSkyAds' test tool to generate a real pixel_click_id and open the campaign URL, then confirm the matching eid in the MGSkyAds UI or log.
- 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 MGSkyAds received the conversion. The provider dashboard is the final result.
Cautions
- Do not send browser parameters or invented eid values directly to MGSkyAds; MeetROAS sends events from its fixed-egress server, and money comes only from signed destination events.