# Meta Ads Reporting for Infobip Business Messaging

Meta Ads Reporting for Infobip Business Messaging is an integration that connects Infobip with Meta It helps you track performance of your Click-to-WhatsApp (CTWA) campaigns when users start conversations from ads The integration shows whether a conversion occurred and how many new profiles were created based on a specific ad running on Facebook or Instagram

You can report conversions programmatically using the [Submit WABA conversions API](https://www.infobip.com/docs/api//channels/whatsapp/whatsapp-ad-conversions/submit-waba-whatsapp-conversions)

Note
To use advertising performance in People analytics, see [Advertising performance](https://www.infobip.com/docs/people/analytics#advertising-performance)

Important
The Advertising performance feature will be deprecated starting April 1 2026

___

## Prerequisites

The main prerequisites for setting up the integration are:

- Infobip [account](https://www.infobip.com/docs/essentials/getting-started/create-an-account)
- Facebook user with permission to connect a WhatsApp Business Account (WABA) and an Ad Account (typically an admin) to Meta Ads Reporting for the Infobip Business Messaging app
- WhatsApp Business Account with sender(s) registered in Infobip
- Users who already have an Infobip account must have the Integrations Manager role
- [API key](https://www.infobip.com/docs/essentials/api-essentials/api-authentication#api-key-header) or [OAuth token](https://www.infobip.com/docs/essentials/api-essentials/api-authorization#api-scopes) with whatsapp:conversions scope enabled (for submitting conversion over the API)

For more information on your Infobip account, contact your account manager or [Support](https://www.infobip.com/contact)

___

## Installation and configuration

To enable conversion tracking, you need a WhatsApp Business Account (WABA) with at least one registered sender in Infobip Connect your WABA using the WhatsApp Embedded Signup flow

1. [Log in](https://portal.infobip.com//) to Infobip and go to Exchange > App Marketplace
2. Find Meta Ads Reporting for Infobip Business Messaging and select Add
3. Go to the WhatsApp Accounts tab, and select Connect WhatsApp Account Infobip redirects you to Meta authentication
4. Log in with your Meta Business Account credentials and select the business portfolio to connect
5. Select the WhatsApp Business Account you want to connect
6. Select Add a phone number later The phone number must already be registered and active in Infobip
7. Confirm the requested permissions and select Finish

After setup, the connected WABAs are displayed on the page Then configure the Conversions API

Note
All senders associated with the connected WABA are available for conversion tracking The dataset ID is automatically retrieved from the WABA configuration

___

## Submit conversion with the API

Use the [Submit WABA conversions API](https://www.infobip.com/docs/api//channels/whatsapp/whatsapp-ad-conversions/submit-waba-whatsapp-conversions) to send conversion events to Meta Conversion API using you WhatsApp Business Account (WABA) and its associated dataset This method supports additional event types and provides direct WABA integration

Note
If you are not using [People](https://www.infobip.com/docs/people) you do not need to store conversion events there

To call the endpoint and submit conversion events, your API key must include the whatsapp:conversions scope You can enable this scope in the web interface by creating a new key through the API or by updating an existing key via the API

### Enable scope over web interface [#enable-scope-over-web-interface-submit-conversion-with-the-api]

To call the scope over web interface

1. In the [Infobip web interface](https://portal.infobip.com/login), go to Developer Tools > API Keys
2. Select Create API key or edit an existing key
3. In the API Scopes section, expand Channels and enable whatsapp:conversions
4. Save your changes

### Enable scope over API [#enable-scope-over-api-submit-conversion-with-the-api]

You can add the scope when you create a new key or update an existing key using our API

To create an API key, use the <apidocslink href="/platform/account-management/create-api-key">Create API key</apidocslink> endpoint and include the whatsapp:conversions scope in the scopeGuids array

For example

```json
{
  "name": "Conversions key",
  "permissions": ["PUBLIC_API"],
  "scopeGuids": ["whatsapp:conversions"]
}
```

You can also add the scope using the <apidocslink href="/platform/account-management/update-api-key">Update API key</apidocslink> endpoint When updating, include all current scopes together with the new one, since the request replaces the full list

For example

```json
{
  "name": "Updated key with conversions",
  "permissions": ["PUBLIC_API"],
  "scopeGuids": [
    "whatsapp:message:send",
    "whatsapp:inbound-message:read",
    "whatsapp:conversions"
  ]
}
```

Note
For more details about API scopes and key management, see [API scopes](https://www.infobip.com/docs/essentials/api-essentials/api-authorization#api-scopes)

Once your WABA is connected and API access is configured, you can start submitting conversion events using the <apidocslink href="/channels/whatsapp/whatsapp-ad-conversions/submit-waba-whatsapp-conversions">Submit WABA conversions API</apidocslink>

When a user clicks a Click-to-WhatsApp ad and starts a conversation, the inbound message includes a ctwaClickId in the referral object This identifier links the conversation to the ad You can use it to report conversions back to Meta through the API

Each conversion must include

- sourceId Phone number of the sender connected to the WABA (mandatory if multiple senders are connected)
- conversions Array of conversion events Each event must include
  - ctwaClickId Unique identifier of the ad click, from the inbound referral object
  - type Conversion type Can be PURCHASE or LEAD_SUBMITTED
  - details Currency and value of the conversion Value can be 0 Currency must match the currency configured in your Meta ads account
  - conversionTime (optional) Timestamp in ISO 8601 format Must not be older than 7 days If omitted, the submission time is used

Example API payload

```json
{
    "sourceId": "1234567890",
    "conversions": [
      {
        "ctwaClickId": "ARAkLkA8rmlFeiCktEJQ-QT",
        "type": "PURCHASE",
        "details": {
          "currency": "USD",
          "value": 99.99
        }
      }
    ]
}
```

### Supported conversion event types [#supported-conversion-event-types-submit-conversion-with-the-api]

WABA Conversion Tracking supports the following event types 
- PURCHASE
- LEAD_SUBMITTED
- INITIATE_CHECKOUT
- ADD_TO_CART
- VIEW_CONTENT
- ORDER_CREATED
- ORDER_SHIPPED
- ORDER_DELIVERED
- ORDER_CANCELED
- ORDER_RETURNED
- CART_ABANDONED
- QUALIFIED_LEAD
- RATING_PROVIDED
- REVIEW_PROVIDED

___

## Validate your setup and requests

Before submitting conversion events, use the checks below to validate the most common failure points when submitting conversion events

### Verify conversions in Meta [#verify-conversions-in-meta-validate-your-setup-and-requests]

After submitting conversions, you can verify them in [Meta Events Manager](https://www.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fevents-manager2%2F)

1. Log in to [Meta Events Manager](https://www.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fevents-manager2%2F)
2. Go to your dataset
3. Check for the conversion event in the events list
4. Verify the event details match what you submitted

### Setup verification checklist [#setup-verification-checklist-validate-your-setup-and-requests]

- WABA connection - Your WhatsApp Business Account appears under Exchange > App Marketplace > Meta Ads Reporting for Infobip Business Messaging > WhatsApp Accounts
- Sender alignment - The sender used in your request is linked to the connected WhatsApp Business Account
- API access - Your API key includes the whatsapp:conversions scope
- Payload format - The request is sent in JSON format and includes all required fields

### Common errors and fixes [#common-errors-and-fixes-validate-your-setup-and-requests]

The following table describes errors you may encounter and how to resolve them

| Where it fails | Example | Likely cause | What to do |
|----------------|----------|--------------|------------|
| Connect WABA | **No WABA found for phone number** | The sender is not linked to a WhatsApp Business Account connected through the Embedded Signup flow | Verify the sender in the request matches the sender associated with the connected WABA Confirm the WABA is listed as connected in the Exchange app If needed, re-run [sender registration](https://www.infobip.com/docs/whatsapp/get-started/embedded-signup) to reconnect and sync |
| Verify in Meta | **Dataset (event set) not found for page** | A Meta Conversions API dataset is not configured for the WhatsApp Business Account | In [Meta Events Manager](https://www.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Fevents-manager2%2F), verify a dataset exists for the WhatsApp Business Account If it exists but the error persists, re-run [sender registration](https://www.infobip.com/docs/whatsapp/get-started/embedded-signup) to sync the dataset |
| Submit request | **Unsupported request for WABA provider** | Invalid request structure or missing required fields | Confirm Content-Type application/json Verify the request includes sourceId and conversions Ensure conversions is a non-empty array and each event includes ctwaClickId, type, and details |

___

## Click-to-WhatsApp and Conversions in Answers

When you need to signal a conversion that happened back to Meta, use the Meta Ads Reporting for Infobip Business Messaging Answers block The supported events are

- Purchase
- LeadSubmitted

When defining the supported events, make sure that you provide the required conversion data in the Answers block

First, create a local attribute within the chatbot for all three values

- ClickID Text attribute
- Currency Text attribute
- Value Number attribute

When a conversion is happening, use the code element to store the proper values to those attributes

View JSON example

```json
{`attributeApi.set('Currency','EUR');
CTWA_Click_ID = attributeApi.get('whatsAppMoReferralCtwaClickId');
attributeApi.set('ClickID',CTWA_Click_ID);`}
```

Currency is hardcoded because it is expected to be the same throughout the chatbot It can differ based on your use cases Click ID is the value that comes from the chatbot as a part of the inbound message referral data The value of the conversion depends solely on your use case

Note
LeadSubmitted event is expected to have the same data as with Purchase to be sent with the conversion event

When everything is completed, you are ready to activate your chatbot and track conversions back to Meta