Learn business growth with Google Analytics 4 Forums Google Analytics 4 Ensuring accurate transmission of Firebase item-specific custom parameters in the console

  • Ensuring accurate transmission of Firebase item-specific custom parameters in the console

    Posted by Oliver on 23 June 2023 at 9:39 pm

    Hey there, I’ve been trying to use the Firebase iOS SDK version 10.7.0 to send item-scoped custom parameters. I know this feature was added in version 10.6.0.

    There’s not a ton of details about it in the official docs, but I guessed that it would be similar to sending an event-scoped custom parameter. For the event-scoped ones, I would just add a new key in the logEvent parameters dictionary, like this:

    let params = [
    "some_custom_key": "someValue"
    Analytics.logEvent(AnalyticsEventAddToCart, parameters: params)

    So I figured this would work in the same way. I added a custom key to the item dictionary, which I sent in the items array. It looked like this:

    let params = [
    AnalyticsParameterItems: [[
         AnalyticsParameterItemID: "someID",
         AnalyticsParameterItemCategory: "someCategory",
         AnalyticsParameterItemName: "someName",
         AnalyticsParameterQuantity: 1,
         AnalyticsParameterItemBrand: "someBrand",
         AnalyticsParameterItemVariant: "someVariant"
         "param_item_custom_id": "someCustomId", // This one being the custom parameter
    Analytics.logEvent(AnalyticsEventAddToCart, parameters: params)

    However, I can’t seem to verify that this is working correctly. There’s no changes on the Debug View, and I’m not getting anything back from the explorer tab queries.

    When I check the Debug View, I can see the events and items, but none of the custom item-scoped parameters are showing up.

    I also tried to add a custom dimension (even though this wasn’t needed for the event-scoped parameters), but it didn’t change anything.

    I waited for 48 hours as suggested, but still no luck. Both Debug View and the explore tab are still not showing my item – it’s just showing as (not set).

    I doubt they’d release a feature that couldn’t be verified on the console, so I’m guessing the mistake here has been on my end. Either I’m sending the custom parameters incorrectly, or I’m looking in the wrong place to validate them on the console.

    Could anyone point out what I’m doing wrong? How would I properly send these item-scoped custom parameters and where should I look to check my implementation in the Firebase console?

    Elijah replied 11 months, 2 weeks ago 3 Members · 2 Replies
  • 2 Replies
  • Emma

    6 July 2023 at 2:59 am

    The issue seems to be with how the person is trying to send item-scoped custom parameters using the Firebase iOS SDK. They are adding a custom key to the item dictionary which they are then sending in the items array. However, they are unable to verify if this is working correctly as they can’t see any changes on the Debug View or get any results from the explorer tab queries. They’ve also tried adding a custom dimension but to no avail. They’ve waited for the suggested 48 hours but still have not seen their item appear – it is showing as ‘not set’. They are asking for help on what they could be doing wrong and how to properly send these item-scoped custom parameters, as well as where should they check their implementation in the Firebase console.

  • Elijah

    8 July 2023 at 2:11 pm

    The issue you’re experiencing might be due to the fact that custom parameters don’t show up in the Firebase Debug View. The Debug View is designed to display predefined event parameters. Custom parameters, whether item-scoped or event-scoped, may not appear in Debug View but they should be recorded and should appear in BigQuery exports or any custom reports you’ve set up. It’s worth checking that you’ve registered your custom parameters in the Firebase console under custom definitions. Keep in mind that it can take up to 24 hours for data to propagate to these areas. If the custom parameters data still don’t appear, you might want to reach out to Firebase support for further investigation.

Log in to reply.