Once these are set up in Google Analytics, the traits and properties can be mapped to custom dimensions as set by the user in the RudderStack destination settings page (as seen in the Getting Started section).Ī custom dimension should be set as dimension. There are multiple scopes for custom dimensions, such as hits, session, user, and products (If Enhanced eCommerce is enabled). In Google Analytics, you can configure custom dimensions in the Admin page. And if Send User ID to GA setting is enabled, the user ID property will be set as uid and will be sent as well. This id is used as the cid in Google Analytics. If userId is not set, RudderStack sends a generated ID (called anonymousId) from its SDKs with every call made to the RudderStack servers. You can call identify once in order to set the userId and user traitsfor all subsequent calls that you make from our SDK for a particular user.
Traits are not mapped to custom dimensions, metrics and content grouping yet from our side in server-side. RudderStack passes an internally generated ID as the cid parameter for Google Analytics to understand every unique user. Traits along with custom dimensions, metrics, and content groupings can be set in the SDK.įor server-side, Google Analytics needs a customer identifier for each call to be made.
In the above snippet, the userid will be set to user123 for Google Analytics, but the name and email will not be shared with Google.
0 kommentar(er)
