To add first-party user data ( for Server containers), you need to add a new setting with the name user_data and set its value to a User-Provided Data variable.Īs before, custom event parameters you add will be included in any events that fire after this Google Tag, as long as these event tags reference the Measurement ID loaded by the Google Tag.Īlso as before, the values configured in the Google Tag will be fixed to the values when the Google Tag last fired. If you do want to add user properties in bulk (or with dynamic evaluation criteria), you can use the parameter user_properties set to a JavaScript object.
You can also add (or override) individual parameters using the table fields.Īn additional perk of using a Google Tag: Event Settings variable is that the variable has a table for setting Google Analytics User Properties one by one instead of in bulk. Ideally, you should follow the documentation to figure out what the predefined configuration settings and predefined event settings are.Īs with configuration settings, I recommend loading shared event settings from a Google Tag: Event Settings. In fact, there’s a lot of overlap between what you can set in Configuration settings and what you can set in Shared event settings. currency) as well as custom settings that do not correspond with actual event parameters (e.g. navigation_menu_id), predefined event parameters (e.g. This includes custom event parameters (e.g. Shared event settings is where you can configure event parameters that any product tags that reference this Google Tag will make use of.
#Reaktor user library full
You can find the full list of supported configuration settings here. The URL of your server container, if you want to divert this Google Tag’s traffic to your server-side GTM.įirst-party user data for Server containers and user properties for Google Analytics are configured with Shared event settings.
Whether to send a page_view event automatically when this Google Tag loads. Since the new configuration settings only accept key-value pairs of parameters, the settings that used to have dedicated UI toggles in the GA4 configuration tag have now been replaced with the following keys: Parameter name I recommend loading the settings using a Google Tag: Configuration Settings variable, but you can also add (or override) individual parameters using the table fields. Product-specific configurations can be added directly to the Google Tag under the Configuration settings heading. Once you’ve added the Tag ID, you can proceed to add configuration settings as well as shared event settings across your product tags.
0 kommentar(er)
