[BUG] - Missing fields in Meta Ads Integration - Conversions API Payload

I have identified an issue where RevenueCat does not send complete app event data to the Meta Conversions API.Below is a sample request body obtained from the RevenueCat → Meta Ads integration:

Reference: Meta Conversions API documentation – https://developers.facebook.com/documentation/ads-commerce/conversions-api/app-events

{
      "action_source": "app",
      "app_data": {
        "advertiser_tracking_enabled": 1,
        "application_tracking_enabled": 1,
        "extinfo": [
          "i2",
          "com.my.app",
          "",
          "1.0.0",
          "26.3.1",
          "",
          "en-US,en;q=0.9",
          "",
          "",
          0,
          0,
          "",
          0,
          0,
          0,
          ""
        ],
        "vendor_id": "5E153361-2630-4731-9D6F-XXXXXXX"
      },

• Device: Apple Iphone 12 Pro Max
• React Native (Expo)
• "react-native-purchases": "^10.0.1",
• "react-native-purchases-ui": "^10.0.1",

---

Why This Data Matters for Ad Performance

The missing parameters are not just optional metadata—they play a significant role in improving ad performance and attribution accuracy within Meta’s advertising ecosystem:

1. Improved Event Matching & Attribution
Meta relies on multiple signals to match incoming conversion events with user profiles. Fields like device model, timezone, carrier, and app version increase the likelihood of accurate event matching. Missing these signals can lead to under-attribution of conversions.

2. Better Optimization Algorithms
Meta’s ad delivery system uses machine learning models that depend on rich contextual data. Parameters such as device type, OS version, and screen properties help optimize ad delivery toward users more likely to convert. Incomplete data limits the effectiveness of these models.

3. Audience Segmentation & Personalization
Granular device and environment data (e.g., locale, timezone, carrier) allow better audience segmentation. Without this, ads may be less relevant, reducing engagement and conversion rates.

4. Enhanced Reporting & Debugging
Full extinfo data enables more detailed reporting in Meta Events Manager. Missing fields make it harder to diagnose performance issues or analyze trends across devices and regions.

5. Compliance with Meta Best Practices
According to Meta’s Conversions API documentation, providing complete extinfo improves data quality and event reliability. Partial implementations may degrade campaign performance over time.

The current implementation by RevenueCat sends only a subset of the recommended extinfo fields. This incomplete data transfer can negatively impact attribution accuracy, optimization efficiency, and overall ad performance in Meta Ads.

I recommend that RevenueCat expand its integration to include all supported extinfo parameters as defined in Meta’s Conversions API documentation.