RC Meta Ads Integration - No parameters were detected

Hey ​@roberto-cruz-ae4360!

I believe the message you’re seeing about no event parameters being detected is due to the use of custom events. At this link in Meta’s documentation under “Custom Events”, it says:

If the event you wish to track isn't available above, you can create a custom event, which will provide you with insights and targeting on the event, but not measurement or optimization. Therefore, we recommend taking advantage of standard events whenever possible.

If you click into the one of the events sent by RevenueCat in your Meta Events Manager, are you able to see any noted parameters?

On our end, here is an example event sent to Meta:

{
  "access_token": "access_token",
  "data": [
    {
      "action_source": "website",
      "app_data": {
        "advertiser_tracking_enabled": false,
        "application_tracking_enabled": false,
        "extinfo": [...]
      },
      "custom_data": {
        "content_ids": [
          "content_ids"
        ],
        "content_type": "content_type",
        "contents": [
          {
            "id": "id",
            "quantity": 1
          }
        ],
        "currency": "currency",
        "order_id": "order_id",
        "value": 0
      },
      "event_id": "event_id",
      "event_name": "event_name",
      "event_time": event_time,
      "user_data": {
        "anon_id": "anon_id",
        "external_id": "external_id"
      }
    }
  ],
  "partner_agent": "revenuecat"
}

Thanks for your response

I am sending Start Trial and Subscribe events to META, which as I understand are META standard events. However, when I click on the event in Events Manager, I don’t see any event parameters.

Hi Roberto,

Thanks for the details. I took a look at your project’s Meta Ads integration in RevenueCat. Everything looks wired up, but the event names you chose are non-standard in Meta (e.g. StartTrialComplete, ConvertedTrialComplete, fb_mobile_purchase) which would cause Meta to infer them as custom events.

When Meta treats an event as custom, Events Manager often shows “no event parameters detected” even though data was sent, parameters aren’t surfaced the same way for custom events, and you lose optimization/measurement benefits. Switching to Meta’s standard event names should fix what you’re seeing.

Please update your Meta event names in the RevenueCat Meta integration to the standard names documented in our docs here.

If you switch the event names to the recommended ones and still don’t see parameters after a day, let me know and I can dig further into this for you.

Hope this helps, let me know if you have any other questions. I’m happy to help!

Best,

Hussain

Hello Hussain I removed the META Ads Integration, thank you, since we need to customize some data in the payload before to sent it to META, thanks for your help