Thank you, this is helpful. I look forward to reading: "I will post
article about auto-tagging that we have implemented on our side using
#3, which I think is the best solution in terms future proofing your
We have been implementing several rules using a direct call of
satellites. Would it be better in launch to use the Core-click with a
css identifier? Is there a key difference in performance of the two?
I am following a similar post:
but it won't allow me to add a reply. One option provided there was to
download the library to view details in excel. Can someone point me in
the right direction on how to do this? Everything I am finding is
outdated and regards
I guess I should be more specific:If we have test-domain set up for dev
environment, staging-domain, set up for submitted/staging environment,
etc, does anyone see the need to set up a separate property that we test
rules through, or is that just redundant?
Currently we are running some analytics tests using our test-website
domain and we have it all in the same property for Tags/Launch as our
main domain. What are others finding to be best practice here? Do you
run analytics on your test-site? Do you try out new rules there first?
Do you keep this in the same property or a different property