Setting up conversion measurement

• New metrics: The Ads Manager UI and Insights API report new Conversion metrics (for example, Web, App) that Cloud API and the Business Management API do not support. When Marketing template messages sent via MM API for WhatsApp lead to Conversion events (for example, add to cart, purchase) that a business reports from their website or app, these conversion events are attributed to the Marketing message and are shown in metrics, leading to a better understanding of Marketing message ROI. Reporting events is done via integration with Pixel or Conversions API for Web and App Events and the Meta SDK.

• Marketing templates map to Ads only once during initial onboarding to Marketing Messages API for WhatsApp.
• Syncs must be completed for templates to display correct app conversion metrics.
• Ads syncing can take up to 10 minutes.
• Avoid sending messages with new templates before syncing completes to prevent errors or loss of optimization and tracking.
• Existing templates prior to initial onboarding will not have conversion metrics enabled.
• To reactivate unused templates for over 7 days: Send one message using the template and wait 10 minutes for Ad sync to re-activate.

• Event reporting is detected by whether the URL points to a website or app which the same business portfolio has enabled for event reporting via Pixel, Conversions API, or Meta SDK.

https://www.jaspersmarket.com/?fbclid=IwAR2F4-dbP0l7Mn1IawQQGCINEz7PYXQvwjNwB_qa2ofrHyiLjcbCRxTDMgk

• You configure your CTA destination as: https://www.jaspersmarket.com/checkout?campaign=whatsapp_template
• Your link partner rewrites it to a short link that redirects to your site: https://www.example.com/jaspersmarket
• Before sending, Meta appends a click ID to the short link: https://www.example.com/jaspersmarket?fbclid=xyz789
• When the user clicks, the short-link service redirects to your site but drops the query string, sending the user to: https://www.jaspersmarket.com/checkout?campaign=whatsapp_template (missing fbclid=xyz789)

• Test that the final URL retains all query parameters (including fbclid).
• Validate conversion reporting in Ads Manager and Insights API before sending production workloads.
• Avoid appending parameters after fbclid in ways that could disrupt the URL structure.

• Scheme (for example, https, myapp) — helps determine which app can open the link
• Path (for example, /product/123) — the route inside the app
• Query parameters (for example, ?fbclid=...) — includes attribution data like fbclid, campaignId, al_applink_data, and others

• Finds apps with intent filters that match the URL (scheme/host/path).
• Creates an implicit Intent.
• Delivers it to the target Activity (often via onCreate() and/or onNewIntent()), where the app must read the full URL (including query parameters).

• Android intent resolution behavior (multiple handlers, re-launch behavior, or activity launch modes)
• How WhatsApp invokes app links (intermediary parsing and handoff to Android)
• Receiving app implementation gaps, for example:
  • Only reading the URL in onCreate() but not onNewIntent()
  • Not persisting the parameters for later use (install/deferred deep linking/session attribution)
  • Redirecting internally and dropping query params when rebuilding a new URI

• Read the full URI from the incoming Intent
  • Handle both cold start (onCreate()) and warm start/re-use (onNewIntent())
• Extract attribution params (at minimum fbclid, and any others you rely on)
• Persist them for later conversion reporting/session attribution
  • Store in a durable place (for example, SharedPreferences or a database) with a timestamp
  • Refresh if a newer value arrives (these identifiers can change over sessions)
• Do not drop query parameters when redirecting internally
  • If your app converts a URI to an internal route, ensure you carry attribution params forward or persist them before routing

myapp://some/path?fbclid=TEST123&campaignId=TESTCAMPAIGN

adb shell am start -W -a android.intent.action.VIEW \
  -d "myapp://some/path?fbclid=TEST123&campaignId=TESTCAMPAIGN"

• Add to cart
• Initiate checkout
• Purchase
• Purchase value

• App Purchase
• App Purchase value
• App Add to cart
• App Initiate checkout
• App Activations

1. Via the Meta SDK
2. Via the Conversions API
3. Via a 3rd party mobile measurement partner, who sends events to Meta on your behalf

1. If your app is using Meta SDK, upgrade your SDK version to Meta Android SDK v17.0.2 or above. Note iOS app measurement is currently not supported.
2. If your app is using a supported Mobile Measurement Partner (MMP), check with your MMP to get your app ready.
3. If your app is using Conversions API, learn how to send campaign_ids parameters with app events. To get campaign_ids, you’ll need to parse campaign_ids from al_applink_data parameters from the deep link that the user clicked from.

exampleapp://applink/ad_landing_recommend?data={"goods_id":"39109246","page_type":"B"}&al_applink_data={"target_url":"https://www.exampleapp.com&fbclid=IwZXh0bgNhZW0BMAABHbKVD62Fa0uTdpAh6KZn16BmrnWgsTbZgiCEsKGLOcF9RDncEAsbJKWp0Q_aem_y0zBYthdxb0j9epvkZum7w","extras":{"fb_app_id":312563225523989},"referer_app_link":{"url":"fb:///?app_id=312563225523989","app_name":"Facebook"},"campaign_ids":"IwAR2rBBgtFjvI_IUUes4nZ6FcQ0dtqujIz1w9JIwrs1YKKn7tGIIqC4kKrXk_wapm_fVVosPGBQJWpvSW8Z8emXg_aem_pyDxR3ch5qDkVdd0Y138yg","ad_id":"1234567","adgroup_id":"1234567","campaign_id":"1234567","campaign_group_id":"1234567","account_id":"1234567"}