I'm running an A/B test on a landing page using Google Analytics' Experiments feature (Universal Analytics). Is it possible to bypass the experiment and always show the original version of the page, though a query string added to the URL or some other similar method?
I'm imagining it being something like site.com/landing-page/?experiment=disabled, but I haven't come across anything in the documentation.
If you append the utm_expid code generated to the experiment page you want to view, it will bypass the redirect.
For example: www.example.com/index.html?utm_expid=121130413-11.qQUH2leXTuCxQsqdgxk9Rw.1 would always return the first page in the experiment.
Related
I've identified a discrepancy between Google Ads clicks and Analytics sessions in Paid Search (about twice more clicks than sessions). So I contacted Google Ads support and after a long conversation, they send me an email saying that my website structure uses redirections and it's making it lose parameters, and that I had to contact a developer to solve that problem because they don't give assistance on it. What exactly they told me to tell the developer was that:
Loss of parameters by redirection
The website trendotrends.com is not holding navigation parameters
because of the structure in which it was developed.
To verify this redirection, simply replicate the following steps: I
accessed the link
https://trendotrends.com/products/running-shoes?variant=15320930779194
After full site loading, I added the & gclid = Tester123 parameter to
the URL (in the browser, so the final URL was
https://trendotrends.com/products/running-shoes?variant=15320930779194&gclid=Tester123)
and hit Enter To understand if there is a redirect, the normal
behavior would be for the URL to remain the same (with & gclid =
Tester123 at the end), but in this case, the parameter disappears (and
hence the assignment) This link was just an example, which can be
verified in several other products of the site.
They also said I can't use manual tagging (UTMs) instead of automatic tagging in Google Ads because those redirections are also going to spoil the UTMs.
I don't use any redirections in my website and I have also tested with UTMs and there's also a discrepancy in google analytics data for that.
But before I contact a developer and invest on this fix, I would like to know if anyone had experienced that? If Googles answer fits this problem? And even if is there a way to fix it without being an expert.
Thanks in advance.
The issue here isn't really that there's a redirect (301), but a state change. There is javascript on the page that essentially rewrites the URL before the GA code can parse it.
Are you able to change to a different theme and test if this happens with that theme?
I'm currently running an experiment without redirect, using Google Analytics, but I'm running in some issues.
The case
I work for a company that has two websites, with two separate brands, selling the same product. Today, we are plaining a merge of the brands, one of the reasons being the low costs of maintanance.
To see how this would affect sales, we are doing an a/b test. The test consists of changing the logo of the sites, and displaying an information about the merge of brands in the variant. The original is the website without changes.
We have some requirements to do it:
We use a CMS that has no support to the Google Analytics Experiment tag (we get some errors when we install it to the , and are unable to run it)
We need to run it through all pages of our websites. We have also a subdomain in each site, that the user is redirected to place an order.
We doesn't have time to wait for the experiment to end for itself. So, we came up with the idea to track the rejection and sales using a duplicate pageview with "/variant" in the url and in the title.
To do that, I used the Content Experiments without redirects, with the Google Tag Manager.
Configuration of the Experiment
In Google Tag Manager, I load the Content Experiment Javascript API and define the choosenVariation variable in all pages of both websites and subdirectories.
I track the "gtm.load" event, to see when the page finished loading all elements and change the DOM in three ways: changing the logo, adding the content about the merge and add an item to the main menu. All of this, through Javascript.
Along with the changes of the DOM, I add a datalayer called VirtualPageView, and pass the corresponding url with "/variant" and the title with "Variant".
When the datalayer fires, I send a new Pageview with the variant information.
The problem
The experiment is running right, but when a user gets the B variant of the experiment and procceed to a subdomain of our websites to place an order, it seems that it's somehow running another test, and happens to the user get the A variation.
We are trying to persist the original session and the client Id through the domain and subdomain, in order to the user that saw the different logo, continue in his way to order.
I saw this page about Running Experiments across Subdomains, but its about the Classic Analytics and the classic experiment, and we are using the Universal Analytics with the Content Experiment without redirects.
I don't know if my explanation was clear enough, so if someone have doubts, please ask me. I don't have a profound knowledge of Google Analytics or the Content Experiments either. So, if you have a better way to do this, please, tell me.
I came up with a solution to our problem. We agreed to use the experiment only in the pages of the main domain, so I can change the content otherwise in the pages of the subdomain:
When a user visits our main domain, through Google Tag Manager, I created a cookie that says what the result of the variation chosen for the user (0 for the original and 1 for the variation).
When this user goes to our subdomain to place an order, still via GTM I check the cookie to see its value. If its equal to 1 (a variation), I change the logo and the menu, according to our previous configuration, and I send a virtual pageview to help us check the data.
Until now, this is working properly.
We have Google Analytics on our site. This site also uses Google Tag Manager (unsure whether this is causing the issue or not).
The issue is that within Google Developer on the Network tab it looks like Google Analytics is being called three times, therefore messing up the actual analytics side.
I have searched the web for this issue but most put it down to the page refreshes etc. This is not the case with ours. This happens when it is first loaded.
Each URL is different slightly. I looked through the site code hoping to find duplicate data (script for Google Analytics), sadly I haven’t. Neither have a found duplication when I 'View Source'.
At this moment in time I am puzzled as to why this is happening.
I have noted the parameters are slightly different between the three, I am thinking this is why it looks like its being called three times, why would it do this?
DP: Document location URL (The call which doesn't contain GTM, contains this)
GTM: Google Tag Manager (Two of the three
have this in the third doesn't)
CD1: ? (The call which doesn't contain GTM, contains this)
Z: Cache
Any ideas will be greatly appreciated.
Thanks,
Clare
Most definitely possible that GA and GTM both sending page views. If you are using GTM then you should remove ALL GA code from your pages as GTM replaces all GA.
General setting
I have a website, which uses regular and encrypted urls. Now I want to track the pageviews or all pages the same way.
I have regular URLs like this:
/library.dll?page=page12&arg1=0&arg2=some&session_id=7892734
and special pages like this:
/library.dll?page=specialpage&arg1=0&arg2=some&session_id=7892734&id=page13
aswell as encrypted URLs like this, which are also containing the session id:
/library.dll?page=encrypted&args=gYZEI7lnRAQLzVXdtdbcral8.cOoc6NDtMUGY2yep9wO3JM
So the interesting niformation is always the page, which is in this examples page12, page13 and page14 (where page14 is also part of the encrypted string).
Clarification
I can change the HTML and JS code only. I have no access to the Google Analytics interfaces at all. This will be administrated by multiple customers.
The GA code will be integrated within a template using a customer-specific code and their unique tracking id.
Problem description
I need to track the page argument, because this is basically the interesting part of the url. When tracking other url parameters I cannot accumulate the pageviews for a certain page, because Google Analytics shows them as separate pages.
In addition I don't see any way to track the pageviews with encrypted URLs, because I cannot set a generic name for them unless there is a way to utilize the method ga('send', 'pageview');
Solution idea
I read about overwriting the pageview attributes like this:
ga('send', 'pageview', '/my-overridden-page?id=1');
in the article on page tracking #Google Developers
Utilizing (event) triggers is in my opinion a pretty bad idea.
The question itself
Is there any smarter way to track this information? Is extracting the page-information and overwriting the pageview attributes the best way to do this?
I just started using GA and have kind of no idea how to do this any other way.
You could use filters (custom advanced filters) to rewrite the request url inside the google admin interface (admin->views->filters). This has the advantage that you do not need to change your site/application code.
However using filters will require multi-step-filters with heavy use of regular expressions, and you would have to test this in a "staging" view first (because a wrong filter will permanently mess up your data).
Passing a custom url to the pageview tracking is pretty straightforward and can be tested immediately via the real time view. In my opinion this is indeed the smartest way to do this.
Is there something special about tracking a google analytics experiment across subdomains?
I have an experiment set up in an account which tracks a top-level domain and several sub-domains. The experiment is implemented in javascript and the experiment Id and variation are set using
cxApi.setChosenVariation(chosenVariation, opt_experimentId)
which is placed above tracking code (included via google tag manager). When creating the experiment I gave two dummy urls as the page variations and chose the 'Insert code manually' option, (although I did not insert the code as advised at https://developers.google.com/analytics/solutions/experiments-client-side :"The Experiment ID is the only information needed to continue and implement the experiment. The JavaScript snippet is not used.").
The experiment tracking is working for the top-level-domain, but not any of the subdomains. This seems strange because the account in which this is set up records all other tracking data successfully for all sub-domains. Does anyone have any idea what I might need to do to get the experiment tracking working in the sub-domains as well?
Thanks