I just discovered something interesting about the Google Analytics module, and I'm wondering if someone can give me some insight.
We decided to use 4-Tell for product recommendations, so I unassigned the related_products item from my PROD page template since it's unnecessary. However, once I did that, my Google Analytics code stopped working. Specifically, the variable l.settings:ga_tracking:google_id_unencoded quit working. I pulled up the LSK to check the code and sure enough, the Google Analytics module initialization function stops if related_products isn't assigned and enhanced ecommerce tracking is enabled. Aside from just putting my Google ID directly into the template code, is there a way around this? Also, why does this function that way?
On a related note, the l.settings:product_link_prefix variable is returning a non-SEO-friendly URL that has no relationship to my URI settings. I guess it's set up to work with the old SEO URL settings? Should that just be replaced with the canonical URI to the current page?
Thanks,
Josh
We decided to use 4-Tell for product recommendations, so I unassigned the related_products item from my PROD page template since it's unnecessary. However, once I did that, my Google Analytics code stopped working. Specifically, the variable l.settings:ga_tracking:google_id_unencoded quit working. I pulled up the LSK to check the code and sure enough, the Google Analytics module initialization function stops if related_products isn't assigned and enhanced ecommerce tracking is enabled. Aside from just putting my Google ID directly into the template code, is there a way around this? Also, why does this function that way?
On a related note, the l.settings:product_link_prefix variable is returning a non-SEO-friendly URL that has no relationship to my URI settings. I guess it's set up to work with the old SEO URL settings? Should that just be replaced with the canonical URI to the current page?
Thanks,
Josh
Comment