I've a Stape business plan. My CMS is Shopify and I'm using custom event to enable datalayer instead of Stape's plugin. Will this work on theme independent datalayer? Also I don't see Google Ads cookie _gcl_aw in the cookie list. Should I add this cookie in the cookie keeper?
Yes, of course you can use your data layer without any restrictions. _gcl_aw is a web conversion linker cookie, so it is used if you have Google ADS running in a web container. When using Google ADS on a server container, the FPGCLAW and FPGCLGB cookies are used - they are in the list of standard Cookie Keeper cookies for Google ADS. But of course you can add any other cookie you want to the list of cookies that Cookie Keeper restores. So if you want to use web tracking for Google ADS - you need to add _gcl_aw as a custom cookie.
Does this enable you to extend the 7 day click attribution window on facebook? Person A saw Facebook Ad and decides to purchase or fill out a form 14 days later? Does the extended cookie allow me to still send back a conversion event to facebook?
When the conversion process takes a long time, and most conversions occur more than 7 days after the initial click, we suggest comparing offline and standard conversions. Offline conversions have longer attribution periods than web conversions. Based on our test, Facebook's standard conversion tracking does not record conversions that happen more than 7 days after the initial click.
@@Stape help me understand, if someone does not want to be tracked and has says so through their opt out either via cookie banner or browser feature options, can i still force the use of 1st party cookies to track a campaign source , medium, name and content used?
@@mikehill8097 server-side tagging should comply with the user consent, similar to web tracking. So you can't force the use of cookies or tracking with the help of sst. We have this article on how to use consent in sGTM stape.io/blog/google-consent-mode-v2-prepare-for-the-year-2024
I've a Stape business plan. My CMS is Shopify and I'm using custom event to enable datalayer instead of Stape's plugin. Will this work on theme independent datalayer? Also I don't see Google Ads cookie _gcl_aw in the cookie list. Should I add this cookie in the cookie keeper?
Yes, of course you can use your data layer without any restrictions.
_gcl_aw is a web conversion linker cookie, so it is used if you have Google ADS running in a web container.
When using Google ADS on a server container, the FPGCLAW and FPGCLGB cookies are used - they are in the list of standard Cookie Keeper cookies for Google ADS.
But of course you can add any other cookie you want to the list of cookies that Cookie Keeper restores. So if you want to use web tracking for Google ADS - you need to add _gcl_aw as a custom cookie.
Thank you so much @@Stape
Does this enable you to extend the 7 day click attribution window on facebook? Person A saw Facebook Ad and decides to purchase or fill out a form 14 days later? Does the extended cookie allow me to still send back a conversion event to facebook?
When the conversion process takes a long time, and most conversions occur more than 7 days after the initial click, we suggest comparing offline and standard conversions. Offline conversions have longer attribution periods than web conversions. Based on our test, Facebook's standard conversion tracking does not record conversions that happen more than 7 days after the initial click.
@@Stape help me understand, if someone does not want to be tracked and has says so through their opt out either via cookie banner or browser feature options, can i still force the use of 1st party cookies to track a campaign source , medium, name and content used?
@@mikehill8097 server-side tagging should comply with the user consent, similar to web tracking. So you can't force the use of cookies or tracking with the help of sst. We have this article on how to use consent in sGTM stape.io/blog/google-consent-mode-v2-prepare-for-the-year-2024