Support

Troubleshooting

Template to Ad syncing

• Mapping of Marketing templates to Ads happens when the business first onboards to MM Lite API. This means that if a Marketing template is updated after first registration to add/edit/remove a CTA URL that points to a website or app with event reporting enabled, it will not have Conversion measurement enabled. If you would like to add/edit/remove a URL from a CTA button, it is necessary to set up a new Marketing template in order for the system to recognize and correctly map the URL to Campaign and Message set parameters that enable conversion reporting from that URL.
• Ads syncing takes up to 10 minutes under certain circumstances. Using Templates before syncing is complete may send the message without optimization or conversion tracking enabled, or may fail with error 131009. Be aware of this in the following circumstances: Businesses which have newly onboarded to MM Lite API. Wait 10 minutes after registration before sending messages to ensure sync. Newly created Templates. Wait 10 minutes prior to sending to ensure sync. Templates that have not been used in >7 days can become dormant. If a Template has not been used in >7 days, send a single message using the Template and wait 10 minutes to re-activate the Ad sync.

Website and App conversions

Ensure your URL is compatible with conversion measurement by sending a test event. Some partners will reformat URLs prior to sending them to MM Lite API, which breaks Meta’s ability to append a Click ID to the URL which enables conversion measurement. Reach out to your Meta partner if you are working with a platform or partner whose URL reformatting breaks Meta’s conversion measurement. If your app is using Meta SDK, you must upgrade your SDK version to Meta Android SDK v17.0.2 or above.

Error Codes

MM Lite API uses the same error codes as Cloud API, with a few additions, listed below.

Syntax

{
  "error": {
    "message": "<MESSAGE>",
    "type": "<TYPE>",
    "code": <CODE>,
    "error_data": {
      "messaging_product": "whatsapp",
      "details": "<DETAILS>"
    },
    "fbtrace_id": "<TRACE_ID>"
  }
}

Example

{
  "error": {
    "message": "(#100) Invalid parameter",
    "type": "OAuthException",
    "code": 100,
    "error_data": {
      "messaging_product": "whatsapp",
      "details": "Message must be a template message."
    },
    "fbtrace_id": "Ak6nxJSySLEJz32Ps-QiZ1t"
  }
}

Codes