In Firebase Analytics Dashboard showing Landing Page as not set

[sandeep14]

Hello Team,

I am using @react-native-firebase/analytics for capturing analytics in react native android and iOS apps , But on the analytics dashboard I can not see Landing Page analytics. I can see (not set) value for the same. I can see Events and pages and screen

Can someone help what exact code is required for capturing landing Page analytics.

refer screenshot what I see in firebase console

I am using react-native version 0.72.5 and firebase analytics version as [20.3.0]

[russellwheatley]

I'm not 100% sure, but I think "Landing page" is done automatically by the Firebase SDK. But I'm also not sure if this even applies to android/iOS as it sounds like web (i.e. web page) It might be worth setting the view using logScreenView() API if you want to attribute events to views on native apps. Might be worth reaching out to Firebase support and asking how "Landing page" is set. Or even on Stack Overflow.

[sandeep14]

Yes , We are using it in react-native mobile App, We tried with setting logScreenView using below code
analytics().logScreenView({
screen_name: currentRouteName,
screen_class: currentRouteName,
});
}

but it will be showing under pages and views section. under landing PAge section it still showing not set , we are using version 20.3.0 of firebase-analytics library, if it is automatic done by firebasse sdk then why it showing, if any other code syntax to it , kindly guide on same

[sandeep14]

I ask communicate with firebase team , But I got below response

Firebase has yet to provide official support for React-Native framework. Unfortunately, we have limited knowledge and expertise with React-Native, and general consulting services such as specific code implementation items like designing / architecting apps are beyond our support scope. Please take note that we cannot guarantee a 100% workable solution since we have limited knowledge and expertise with React-Native due to the fact that it's not fully supported and is considered as a third party library or framework. However, I'll try my best to share some helpful insights with you.
​
To give an overview, (not set) is a placeholder name that Google Analytics uses when it hasn't received information for a dimension. Additionally, there are multiple factors that could cause this to occur:
A particular event is logged in previous versions of the app and the parameters were not yet supplied. This will result in "(not set)" values for those parameters.
If the custom parameter is an empty string, it will be treated as "(not set)". Note that the default value of the custom parameter is an empty string which will also be evaluated as "(not set)". Please make sure that you've defined the user-scoped dimension (or user property) in your Analytics dashboard.
(not set) is a placeholder name that Google Analytics uses when it hasn't received information for a dimension. It's most likely the value for a custom dimension you set, is not in use anymore (a previous event parameter).
Additionally, it’s expected to see a value of (not set) for a custom dimension in the first 48 hours.
​
Lastly, Custom Dimensions refers to the "text" type parameters while Custom Metrics refers to the "number" type parameters. You need to pass a string data type for custom dimensions, and integer (double/long) data type for custom metrics. You need to make sure that you're passing the proper data type for the parameters associated with your custom event that you're logging. You can check this document for more information on this.

I still not understood what to do
​