Supported · ready to use
Meta (Facebook CAPI)MeetROAS
Put the MeetROAS campaign URL into Meta (Facebook CAPI), 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?
Official-contract verification passed. Live delivery is enabled after a valid data-source ID and Access Token are saved.
What to copy and where to paste it
| Copy | Paste into |
|---|---|
| The complete MeetROAS campaign URL containing fbclid | Website URL |
| Enter Dataset／Pixel ID and Access Token | MeetROAS Campaign → Conversion integrations |
Interface map
Events Manager → Data sources → Settings → Conversions API
Paste the complete MeetROAS campaign URLURL must keepfbclid
Campaign → Conversion integrations
Enter Dataset／Pixel ID and Access Token✓ Finally confirm the conversion in Meta (Facebook CAPI)
What you need
| Provider area | Events Manager → Data sources → Settings → Conversions API |
|---|---|
| Click macro | fbclid |
| Return method | Server Event API |
MeetROAS uses the Meta Conversions API. The Access Token is encrypted at rest and is not a postback URL.
Setup steps
- Create or open a MeetROAS Campaign whose traffic source is Meta (Facebook CAPI), then copy the generated campaign URL.
- Create or select a web data source and generate an Access Token.
- Use the MeetROAS Website URL for traffic and retain fbclid.
- Enter Dataset／Pixel ID and Access Token, then create the official event defaults in one click. The token is never displayed again.
- MeetROAS reviewed request shape, event mapping, response classification, and dedupe against the public official contract. No real account was used, so this is not an end-to-end verification; Events Manager diagnostics remain an optional check.
If the provider does not list a MeetROAS tile, use Custom, Other tracker, or the provider's generic postback option.
Events and money
Deposit uses the official Purchase event. First Deposit uses the custom FirstDeposit event; First-day Deposit uses the custom FirstDayDeposit event.
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 |
|---|---|---|---|
| Meta (Facebook CAPI) | data[].custom_data.value | — | data[].custom_data.currency; Send money only when both value and currency exist; 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 |
|---|---|---|---|
| Meta (Facebook CAPI) | fbclid | data[].user_data.fbc ← fb.1.<clickObservedAtMs>.<fbclid> | data[].event_name uses the defaults below |
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 | Meta (Facebook CAPI) |
|---|---|
| landing_view | ViewContent (standard) |
| install_click | InstallClick (custom) |
| install_prompt_accepted | InstallPromptAccepted (custom) |
| pwa_install | PWAInstall (custom) |
| pwa_open_attempt | — |
| pwa_first_open | PWAFirstOpen (custom) |
| account_registration | CompleteRegistration (standard) |
| first_deposit | FirstDeposit (custom) |
| first_day_deposit | FirstDayDeposit (custom) |
| deposit | Purchase (standard) |
| login | Login (custom) |
How to confirm success
MeetROAS reviewed request shape, event mapping, response classification, and dedupe against the public official contract. No real account was used, so this is not an end-to-end verification; Events Manager diagnostics remain an optional check.
- 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 Meta (Facebook CAPI) received the conversion. The provider dashboard is the final result.
Cautions
- When browser Pixel and server events overlap, event name and event_id must match for deduplication. Report one transaction as either Deposit or First Deposit, not both.