The default value of this is set to auto. Once this setting is enabled, Google Analytics anonymizes the address at the earliest possible stage of the collection network. You can turn on Anonymize IP Address in the RudderStack destination settings under the Other Settings option. RudderStack supports the following measurement protocol parameters: You can collect the value of the parameter as a RudderStack trait or property when sending server-side events to Universal Analytics. It provides parameters which are automatically collected by the device mode Google Universal Analytics tracker. You can also send data to Google Analytics using the measurement protocol. Also, campaign.term and ntent are optional. campaign.name and diums must be sent together to show up in the report. UTM parameters are passed in the context object in context.campaign. The UTM parameters need to be passed manually to the server. However, on the server-side, the visitor's IP has to be included in the track call. On the client-side tracking, the IP address of the HTTP request is sent automatically to determine the location of the visitor. On the server-side, user_agent is set from erAgent. If the Disable MD5 encryption from Client ID setting is disabled in the dashboard, RudderStack passes the userId as the clientId in the MD5-hashed format. The checkout flow can be implemented by calling track with checkout step viewed and checkout step completed for the steps you have added in Google Analytics. You can configure the checkout funnel in the Google Analytics admin interface as shown below: The Checkout steps feature is a key difference between the regular E-Commerce and Enhanced E-Commerce tracking, and a major feature of the latter. To send Enhanced E-Commerce events, please enable it in the RudderStack destination settings page.

order_id is required for refunded orders.

product_id will check if properties.product_id is present or not.

The product ID or name must be passed for all the events that has the product details.

For each product, id and nameare required. Similar to E-Commerce tracking, for every order completed the orderId is required.This is a necessity for product-scoped custom dimensions.Įnhanced E-Commerce must be enabled in Google Analytics, and should follow RudderStack's E-commerce Events Specification. The E-Commerce tracking should be enabled otherwise it will not be shown in the reports.Įnhanced E-Commerce allows you to derive insights on the E-Commerce events by combining impression data, product data, promotion data and action data.For each product in the order, there must be an id and name. For every order completed, orderId is required.RudderStack supports basic E-Commerce tracking for Google Analytics. In Google Analytics, some events can be tagged as non-interaction events. Similar activity is to be done for metrics.Īn identify call with custom dimensions will be recorded after the next track or page call. For example, dimension1 and it will map accordingly when the user sets the dimension in GA settings as shown below.

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.

Anonymizer universal location