That way all the Facebook hits (that require deduplication) can fire on the event and use the Event ID in the pushed object. Another option is to push an event to dataLayer for each set of Facebook tags that needs to be deduplicated, and with that event also push the random, unique Event ID. So if you have, for example, the variable used as Event ID in a web pixel and a server-side call, then it will return a different number for both times the variable is called.Ī fairly simple way to create the Event ID would be to generate a random Page ID for every page load, and then concatenate this with a sequence number that is increased by one for each set of Facebook events that needs to be deduplicated. With Google Tag Manager, creating a consistently unique event ID is a bit difficult, as variables are resolved each time they are invoked. ![]() Each set of events that needs to be deduplicated must have its own unique event ID, otherwise Facebook will not be able to consistently deduplicate the data. The event_id must be unique for all the events that should be deduplicated. If you are only collecting events using one or the other, you do not have to use event_id! ![]() This is only relevant if you are duplicating data collection between the web pixel and the Server container, for example. event_timeĮvent_id is used for deduplicating identical events collected from more than one source (e.g. There are a handful of utility parameters that you can set as GA4 event parameters, and they will be handled in a special way by the Facebook tag. So if you use any of the event name values in the left column, Facebook will convert them to the corresponding values in the right column when collecting the data.Īny other event names will be used as-is without modifications when collecting the data to Facebook. However, some event names have special functionality, and they are automatically converted to Facebook’s standard event name format. You can set anything you like into this and it will work with Facebook’s endpoint. Event Nameįirst, there’s the Event Name field in the GA4 web tag itself. The Facebook server-side tag has a limited inventory of parameters it can make use of. Instead, we’ll focus on utilizing the GA4 web tag for Facebook’s purposes. You might want to create a new data stream in GA4 just for your server-side hits.īut this isn’t a guide on how to create a GA4 server-side setup. That way you can “parallel track” via the web tag AND the Server container. If you’re just starting to work with Server containers, it might be wise to copy your existing GA4 web tags rather than replace their functionality with the transport_url field. Let’s start with modifying the GA4 web tag. Here’s a brief overview of how the process works.Īnd that’s it for the overview! Let’s jump into each part in more detail. Subscribe to the Simmer newsletter to get the latest news and content from Simo Ahava into your email inbox! If you want to use the Facebook web pixel to handle both the web stream and the server-side data dispatch, you will have to wait a while until Facebook officially releases their solution for splitting the web pixel stream into both a Facebook server request and a custom endpoint request (e.g. Modify any possible GA4 server-side tags.Trigger when any GA4 request is received.Create and configure the Facebook Conversions API Tag.Load the Facebook Conversions API Tag template from the template gallery.Make sure the GA4 Client is running in the server container. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |