October 1, 2020
Transfer UTM Parameters From One Page To Another with GTM
Updated: October 1st, 2020.
I have completely redone this solution to support more cases and require less configuration. However, in some situations, the older version of this solution is recommended. If the destination URL contains a hashmark (#), you should try using the older version.
====
Imagine this. You’re running a promo campaign that brings traffic to a certain landing page (e.g. landingpage.com). After the visitor clicks the main Call-to-action button (e.g. GET YOUR DISCOUNT), he/she is redirected to another page (2ndpage.com) which asks a visitor to do the final action, install the app, fill in the form, sign up, etc.
When the conversion is completed, a Google Analytics event is fired. Unfortunately, when you look at your GA reports, what you’ll see is that all conversions are attributed to the landingpage.com. Technically, this is correct because all visitors landed on the 2ndpage.com from landingpage.com, but you’d like to see the original source which brought the visitor, wouldn’t you?
Normally, you’d need to implement cross-domain tracking here but in some cases that is not possible (I’ll explain them a bit later).
In this blog post, I’ll show you how to transfer UTM parameters (or basically any URL parameters) from the initial page landingpage.com to the subsequent one (2ndpage.com) if the cross-domain tracking cannot be implemented.
The problem explained
Say, that you’re promoting a product that is available in the App Store (for example, Shopify App Store). We’ll call it Lorem Appsum. Its App Store page isn’t sufficient to list all the benefits, cool features, etc. So you decided to create a separate landing page that you’ll drive traffic to. You have also marked all inbound links (stored on other websites/forums/etc.) that lead visitors to that landing page with UTM parameters.
That new landing page contains key selling points, descriptions of features, video, and a big GET APP NOW button (Call-to-action, a.k.a. CTA). Perfect. The visitor lands on the initial page, he clicks that CTA button, lands on the App Store page and installs the app. Heres’ the scheme of the entire visitor journey:
Notice that UTM parameters are lost after the visitor clicks an appstore.com link on loremappsum.com page.
The problem is that Google Analytics will attribute this conversion to loremappsum.com, although it would be more beneficial to see the values of the initial UTMs.
Why not implement GA cross-domain tracking?
In the case of app stores, usually, creators/developers are not allowed to edit Google Analytics tracking code, therefore cross-domain tracking cannot be configured properly.
This is what we faced with Omnisend (when I was working there) at Shopify Appstore. We were allowed to set Google Analytics Tracking ID, and that’s it. Unfortunately, in order to make cross-domain tracking work, we also needed to enable allowLinker option on the receiving domain (app store) but that was not possible.
So we had to improvise and this blog post is the solution to the problem.
The Solution – Overview
Update: This is version 2 of the solution. With it:
- you will be able to transfer any query parameters (not only UTMs)
- you will not need to create URL variables
- you can decorate links of multiple domains
- and query parameters that you want to transfer are optional (this means that if utm_campaign is not present in the URL, the solution will still work).
====
One of the solutions is to transfer UTM parameters from loremappsum.com and automatically add them to all links which redirect users to appstore.com/loremappsum. We’ll do this with Google Tag Manager and a custom script.
Important: if you notice that the script is not working in some situation, please let me know and I’ll see what I can do to fix it.
<script>
(function() {
var domainsToDecorate = [
'domain1.com', //add or remove domains (without https or trailing slash)
'domain2.net'
],
queryParams = [
'utm_medium', //add or remove query parameters you want to transfer
'utm_source',
'utm_campaign',
'something_else'
]
// do not edit anything below this line
var links = document.querySelectorAll('a');
// check if links contain domain from the domainsToDecorate array and then decorates
for (var linkIndex = 0; linkIndex < links.length; linkIndex++) {
for (var domainIndex = 0; domainIndex < domainsToDecorate.length; domainIndex++) {
if (links[linkIndex].href.indexOf(domainsToDecorate[domainIndex]) > -1 && links[linkIndex].href.indexOf("#") === -1) {
links[linkIndex].href = decorateUrl(links[linkIndex].href);
}
}
}
// decorates the URL with query params
function decorateUrl(urlToDecorate) {
urlToDecorate = (urlToDecorate.indexOf('?') === -1) ? urlToDecorate + '?' : urlToDecorate + '&';
var collectedQueryParams = [];
for (var queryIndex = 0; queryIndex < queryParams.length; queryIndex++) {
if (getQueryParam(queryParams[queryIndex])) {
collectedQueryParams.push(queryParams[queryIndex] + '=' + getQueryParam(queryParams[queryIndex]))
}
}
return urlToDecorate + collectedQueryParams.join('&');
}
// borrowed from https://stackoverflow.com/questions/831030/
// a function that retrieves the value of a query parameter
function getQueryParam(name) {
if (name = (new RegExp('[?&]' + encodeURIComponent(name) + '=([^&]*)')).exec(window.location.search))
return decodeURIComponent(name[1]);
}
})();
</script>
Once the visitor lands on loremappsum.com AND the Page URL contains utm_medium, utm_source, or any other URL parameter (that you’re interested in), the tag will fire. It will scan the entire page and look for links that contain the domain(s) of the final landing page, in this case, appstore.com.
If the script finds the link, it will:
- Fetch URL parameters (e.g. UTMs) from the browser’s address bar.
- And will add those parameters to that spotted link (which contains “appstore.com”).
So instead of appstore.com/loremappsum, all links on loremappsum.com will be automatically modified to appstore.com/loremapsum?utm_medium=referral&utm_source=promo &utm_campaign=blackfriday2017. Here’s the updated visitor flow:
This solution does not cover 100% of cases
There are situations where this solution will not work properly:
- If the URLs that you wish to decorate contain #, try using the older version of the solution
- If the URLs that you wish to decorate already contain query (a.k.a. URL) parameters from the Custom HTML tag, they will not be replaced. The script will append them to the URL (therefore, you will end up with duplicate parameters).
Notice more situations where the script does not work as expected? Let me know in the comments and I’ll see what I can do.
The Solution – Implementation in GTM
In Google Tag Manager, create a custom HTML tag and paste the JavaScript code that I provided in the previous chapter.
Now, we need to do some configuration.
Edit the list of domains
On line 3, you’ll see this domainsToDecorate array:
var domainsToDecorate = [
'domain1.com', //add or remove domains (without https or trailing slash)
'domain2.net'
],
Here you must enter the domain(s) of the final landing page(s). If a visitor lands on the intermediary landing page, the script will be looking for links that contain the domain(s) from the domainsToDecorate array.
In other words, if the journey is some website > loremappsum.com > appstore.com, then you must enter “appstore.com” in the domainsToDecorate array.
If you want to decorate URLs of just one domain, you can keep just one domain. If you want to add 4 domains, you can do that as well. Just make sure you don’t leave any typos, missing commas or apostrophes.
If you want to be more specific and decorate only some links, you can be even more specific. Instead of the appstore.com, you can enter appstore.com/your-app.
Here is an example with just one domain (obviously, you should replace that domain):
var domainsToDecorate = [
'appstore.com'
],
Add URL parameters you want to transfer
Next, you must edit the list of URL parameters you want to take from the page URL and transfer them to particular outbound (outgoing) links.
If for example, Page URL (where a visitor currently is) is https://www.loremappsum.com/?utm_medium….., then those parameters (e.g. utm_medium) will be added to all the URLs of the appstore.com, e.g. https://appstore.com/loremappsum/?utm_medium…
queryParams = [
'utm_medium', //add or remove query parameters you want to transfer
'utm_source',
'utm_campaign',
'something_else'
]
What’s cool with the recent update of this solution is that:
- You don’t have to create GTM variables for each parameter
- You can transfer any URL parameter (a.k.a. query parameter), not only UTMs
- The parameters you entered in the queryParams array are all optional. If Page URL does not contain, say, utm_campaign, the script will still work just fine
- UTMs can contain a “+” sign as well. It will be transferred just fine and will not be encoded to %2B.
Here’s an example of what the setup could be:
queryParams = [
'utm_medium',
'utm_source',
'utm_campaign',
'ref'
]
Save the tag. Now, it’s time for a trigger.
Trigger
You don’t want to fire this Custom HTML tag on every page. Instead, you should activate it only when the URL contains at least one of those query parameters that you want to transfer. Let’s continue our example where I entered these query parameters in the Custom HTML tag:
queryParams = [
'utm_medium',
'utm_source',
'utm_campaign',
'ref'
]
So, if any of these parameters are in the URL, the Custom HTML tag should fire. Every parameter in the URL should also contain an “equals” sign (=), therefore, our trigger’s condition should be like this:
- Trigger type: DOM ready
- Fire on some DOM Ready Events
- Page URL matches RegEx (ignore case) utm_medium=|utm_source=|utm_campaign=|ref=
What I did here is that I have added “=” after every parameter and then separated them with a pipe ( | ), which in Regular Expressions means “OR”. Of course, we could write a more optimized expression such as:
utm_(medium|source|campaign)=|ref=
or something even slimmer but even the first example will work just fine. If you don’t feel confident with regex, just enter all the query parameters you are interested in, add “=” after each one of them, and separate them with a |.
Save this trigger and assign it to the Custom HTML tag.
Let’s Test
Save all changes, enable Preview and Debug mode. Now head over to the page you’re working on. There are two situations we need to test:
- Make sure that is at least one of the query parameters (that you want to transfer) in the Page URL. In my case, the page URL is www.loremappsum.com?utm_medium=referral&utm_source=promo &utm_campaign=blackfriday2017
- Click the link which contains the domain name you have defined in that custom script I’ve shared in this blog post. In my case, it’s www.appstore.com/loremappsum
- After I’m redirected, the Page URL (appstore.com/loremappsum) should also contain those 3 UTM parameters. The final result in the browser’s address bar should be www.appstore.com/loremappsum?utm_medium=referral&utm_source=promo &utm_campaign=blackfriday2017
Also, do not forget to test the opposite situation when there are no UTMs (or other parameters) in the address bar. In that case, nothing should be appended to appstore.com links.
Oh, there’s also a third case to test, check at least a couple of other external links (unrelated to appstore.com), they should never contain UTM parameters.
Transfer UTM Parameters: Final words
In this blog post, I’ve explained how to transfer UTM parameters (or any other URL parameters) from one page to another. This is really useful when you have an intermediate landing page that you’re attracting visitors to, and then they have to proceed to the final page which is stored in another domain.
This is a plan B if you cannot implement Cross-domain tracking for some reason.
By default, you’d lose all attribution data and Google Analytics will display your intermediate landing page as the main referral.
With the script I’ve shared, you’ll be able to reuse UTM parameters of the initial landing page and decorate certain links with them.
However, keep in mind that obviously, navigation between the intermediary page and the final landing will start a new session (and the same person will still be treated as two different people in your GA reports).
The situation I’ve described is not a very common issue, but it occurs from time to time. Actually, one of my readers has recently asked a question related to this very same topic.
73 COMMENTS
This was great information to have for a pizza website I'm working with. Thank you!
Hi:
Thanks for publishing a wonderful article on UTM passing across URLs. I have been looking for a solution for the problem defined below:
- I provide a link with UTM parameters in emails we send. Whenever a user clicks, he lands on the landing page along with UTM parameters
- From here on, when the user clicks on any of the links within the landing page, he goes to the main website. We want the UTM parameters to be passed on to the main website URLs and from there on, to all the URLs within the website visited by the visitor, ultimately leading to acquiring the UTM values when a form is submitted. This will give us an accurate attribution.
I thought the solution you provided here will work for me. The UTM parameters are not being passed on to the links clicked. Can you please advise how to fix this?
Thanks
RK
Hey, what you need is cookies.
1. Set cookies that contain UTM parameters https://www.analyticsmania.com/post/cookies-with-google-tag-manager/
2. Insert values of those cookies with some simple JavaScript https://www.analyticsmania.com/post/enrich-form-submission-data-with-google-tag-manager/
I also want to use this solution for attributing affiliate conversions in Google Ads. However, wouldn't I need to also have the Google Analytics code on the second domain (appstore.com)?
Assuming that I have an HTML page, And I want that for every user that enter my page, I want to send his first UTM SOURCE,Using a custom dimension, to the GOOGLE ANALYTICS.
explanation:
On the HTML page i need to use a code that enables me to capture incoming traffic's first visit UTM_SOURCE, and send it to GA via custom dimension. than, i need to use a cookie to store the first occurrence of "utm_source" from the URL.
How can this be done?
important notice: i need to use a custom dimension in my html code at my solution ,
and as i said, i need to store it in a cookie.
i understand that i should use the gtag.js
Thank you very much for the help
1. You don't need gtag.js if you use GTM. Ever.
2. When a visitor lands on a page, create a URL parameter that reads utm_source. Here's the guide where you can learn it
3. Store the value of that urm_source in a cookie. Here's a guide how to create and read cookies with GTM
4. Send the value of the cookie as a custom dimension with GTM. Here's an example how it can be done.
hi julius, thank you very much for your quick and detailed answer!
i wanted to know, in which of the steps (1 to 4) should i take care of the
"capture incoming traffic’s first visit UTM_SOURCE"?
thanks again!
1st guide - Read the value of utm_source that is currently in the URL
2nd guide - how to save it in the cookie
Hello,
Thank you for this great article! Do you know if this works for AMP containers as well?
Unfortunately, no. AMP GTM containers do not allow to add custom JavaScript (including this script).
Hi Julius,
Very useful. We've been testing this for quite a while and passing the UTM through works fine. However when I started analyzing the data in Google Analytics we found out that there was a massive increase of bouncerates.
We use this for marketing automation purposes. So when someone visits our website via for example a LinkedIn ad, we can exactly track what this visitor does on our website from the ad with UTM.
Somehow this solution affects bouncerates badly. And the main reason I can think of is that every time a page is loaded with UTM parameters, Google Analytics is starting a new session. So even when a visitors visits a second page, it automatically counted as a bounce. Do you agree? And do you think there is a way to fix that?
Hope you can help me out!
Michiel
Yes, your observations are correct. If a visitor lands on your 1st website, does nothing (no events) and then clicks the link with UTM parameters that lead to the website #2, then a new session will start. This means that your previous session will be counted as a bounce.
An idea for you: track links clicks. So if a visitor on a website #1 clicks a link to the website #2, track it as an event and this will keep your bounce rate lower.
Thanks for outlining this solution.
You most likely already addressed this question in a comment above, but I'm curious if this solution would work if you only have access to the final domain in the process?
For example, I'm working on a project where we will most likely have 10 digital media campaigns for 10 different products. Those campaigns will drive to a Product Page (productdomain1.com, productdomain2.com, etc.)
Then in order to purchase Product1 --> productdomain1-10.com will drive to -- > ecommercedomain.com where you can purchase any number of products 1-10.
If I only manage Google Tag Manager for ecommercedomain.com will I be able to apply this solution to determine the UTMs that began the campaign journey?
Thanks!
Rob
Hey, Robert. The answer is no. You won't be able to apply this method.
Hello Julius,
This is almost working for me. In both Preview Mode and when published, I can see the UTM parameters being appended to the URL of a button when I hover over the button. If I copy the link address, it copies everything as you would expect.
But when I click on the button, the new page on my site opens and the UTM parameters are not in the address bar.
Any suggestions? I've pasted the URL with the UTM parameters below.
Best,
Mike
ps - I purchased your beginner GTM class, but haven't gotten very far in it yet. Maybe I should do that first! :-)
Hey Mike,
This topic is not covered in my Beginner course.
From your link I see that you are probably working with the AMP website, right? This solution is not tested and probably will not work with AMP.
Hi Julius
Thanks, this article is helpful.
I just wanted to ask, this definitely works if all my tracking links have all the UTMs identified e.g. medium, source, campaign. However, some of my tracking links have content and term and even gclid. Is there a way where it just picks up whatever is available?
For e.g. if i have utm_medium=xx&utm_source=xxx&utm_campaign=xxx,gclid=xxx
it will pick up that.
but at the same time if my next tracking link comes in as utm_medium=xx&utm_source=xxx&utm_campaign=xxx,utm_term=xxx
It will still pick it up
Since at the moment, the instructions is all the parameters need to be "does not equal" to "undefined"
I want it so, it picks up any parameters when available, not when all parameters are available.
Hope it makes sense.
Cheers
Steph
Yes, you just need to update the "utms" JS variable in the script. Currently, there are 3 utms in that array, but you can add more. This script currently only fetches those query parameters that are in the "urm" array.
I also want to use this solution for attributing affiliate conversions in Google Ads. However, wouldn't I need to also have the Google Analytics code on the second domain (appstore.com)?
I'm totally new to Google Tag Manager
Can I ask, what kind of tag types are these for the UTM parameters?
page: https://www.screencast.com/t/oaI4ThJdNf
Hey, I'm not sure I understand the question. UTM tags are not the same as GTM tags. "UTM tag" is just a name and it is a part of the page link. In GTM, tag is a tracking script that does something.
All in all, they are two different things. Very different.
Thank you so much for sharing this unique code. It worked great, however, what if in addition I want the UTM parameters in the URL to stick across pages on the same domain as well (like a multi-page quote system)?
Why would you possibly need that? It's fully enough for UTMs to appear on the page just once per domain per session. GA takes care of the traffic source attribution.
Hey Julius, this is really helpful. I have put main domain, we get traffic from different sources and we create landing pages as well. So, we need to see if visit is landed on landing pages, he/she came from homepage or directly from the source. With this implementation, I see UTM Parameters transferred from page to page and that's how we will see the source in GA for landing page. Correct me, if I am wrong.
Thanks
No, this solution should work only on landing pages. If you see UTMs on every page, this means that you have entered your own domain in the custom script. That's not how you should use the code.
Hi Julius,
I was wondering if you could help please.
I've followed your steps but the UTM codes are not tracking onto the final website.
So this is the journey in three simple steps:
1) Facebook Ads and Google Ads containing relevant UTM codes
2) links through to a dedicated product landing page and the UTM codes to follow through
3) click a submit button on dedicated product landing page and it takes you to a different domain
Thanks,
Tom
This solution works with links, not forms (and I'm guessing you're working here with forms). In that case, you would need to contact the developer of the form and implement a similar solution in form's code.
Hey,
Don't you think this would lead to inrease of bounce rate and number of sessions?
Thanks
The bounce rate can be easily manipulated even in this case (e.g. send an event when the link is clicked). The number of sessions will be affected.
Hi Julius, thanks a lot for this great tutorial.
I wonder if this method could be useful to transfer _GA variable (session ID) on an external domain (eg: paypal.com) in order to track and keep entire user journey across purchase process. Payment solutions website are really a challenge for Goggle analytics : most of them don't allow to add any tracker at all and generate urls dynamically..
Sending session to sites like paypal.com won't help because those website must accept and store your session info somewhere. And they usually don't do that.
Thanks Julius for your valuable advice.
So then, there is no way to track journey through paywall solution..to know where successful sessions are really coming from.
Either I keep Paypal (and others) among referrals sessions sources or
I exclude Paywalls through the Referral Exclusion List, but this will inflate Direct access sessions.
In any case sessions are broken, sessions numbers are artificially inflate and Source shares are incorrect: either a bigger % of "Referral" session or a bigger % of "Direct" access.
Is there anything I could trick to mitigate this situation, at least?
My sincere thank you
If the traffic is (direct), google analytics will attribute the conversion/sale to the previous non-direct traffic source, e.g. Organic.
Julius
Hi Julius, awesome solution. Does it work for payment gateway? If its so, should I check the utms parameters when I come back to order-received page or on the current PV payment gate?
thanks in advanced
It works for anything that is accessed via link click.
Hello Julius,
Thank you for this tutorial. Just wondering if this can work on ecomm process, say you direct a customer on a collection page with UTM, and they navigate through the website, then finally convert. Can I pass those parameters across all pages until they reach checkout and convert?
TA
You don't need that if this is happening on the same domain. GA will automatically keep the traffic source intact.
Hi Julius,
This article is a great find. Thanks for simplifying.
Just have a question as to whether this is best practice for tracking links that might cross multiple domains.
Example:
We are paying for media on a publisher's website, that link will drive to our owned social post, we then want to track whether we had any leads to our owned website from the original publisher's link.
Publisher > Facebook post (owned) > Website (owned) = will we be able to see that the referral came from Facebook but source was the publisher?
Hi, that is impossible to track because you would need to have some tracking code added to Facebook's interface.
Hi Julius
Thanks for the post. I've implemented the code but I'm having some troubles...
My goal is to transfer UTM parameters throughout the site in the following setup:
The visitors enter my website via this link:
mywebsite.com/test?utm_source=newsletter&utm_medium=mail&utm_campaign=062020
They than go to:
mywebsite.com/form/
The parameters aren't transferred from /test to /form when I've implemented the code.
Am I missing something?
Thanks in advance!
The parameters are only transferred if both conditions are met:
1. Link is decorated
2. The link is clicked
Regular navigation does not preserve the parameters. If one the page A, you see the parameters added to the link, then the redirect between the page A and page B is losing those parameters (and you should discuss the fix for that with you developers)
Hi Julius!
Great Post. Is there a way to transfer these UTM parameters from one url to other, in case of multiple redirections through tracker pages(when using third party trackers as well) between the source and the Landing Page?
Hi, no. Javascript in the browser (client-side) cannot help here.
If all the redirects were controlled by you, you could ask a developer/sysadmin to preserve those parameters somehow. But if the server-aide redirects happen and developer cannot help you, you are out of luck.
Ah ok! So I get this script needs to be part of each page that the UTM parameters needs to be transferred to, essentially like a passing the baton kind of situation.
Are there any other options?
Options for what? To overcome those redirects you mentioned? There are no javascript solutions for that (meaning that GTM cannot help). Talk this with your developers, maybe they can offer something on the backend.
First off - this is GREAT. I'm wondering how I address if one of the UTMs is missing? Right now, it will not move ANY over if they do not ALL Exist. I'm looking to pass over what I can vs an all or nothing situation.
Thanks!
I have just updated the code. Now it supports any number of parameters in the URL.
Hi thank you for posting this!
What I am doing is embedding a form into a landing page and using the main landing page to have the UTMS. But when I tried this code it still didnt seem to capture the UTMs. Any ideas?
Thank you!!
Hi, this solution is not built for iframes. Only links are supported.
I had to change one small thing to your script :
{ if (links[linkIndex].href.indexOf(domainsToDecorate[domainIndex]) > -1 && links[linkIndex].href.indexOf("#") === -1)
because it would decorate internal links in the page for example to activate the mobile menu
Good catch! I totally did not think about href with just #. I've updated the code.
Thanks!
How can we track with hash link i.e some link has example.com/#our-services
but these url are not tracking the same.
I also want to use this solution for attributing affiliate conversions in Google Ads. However, wouldn't I need to also have the Google Analytics code on the second domain (appstore.com)?
Thank you for the script Julius.
I have a few questions.
Does it work with subdomains?
Do I need to have that in the domain list at the top or just the root domain?
And I am linking to a checkout page where my links have variants.
store.mysite.com/product/product-name?variant_id=1234567
These links are not getting updated.
Thanks
Hello Julius,
Thanks for this method, I tried with a URL where all UTM params were named test. Then I landed on my main domain www.example.com with the UTM it was getting stored in GA
When I clicked on the button it navigated to my subdomain blog.example.com along with the UTM parameters.
However, all the traffic is going to direct/none not the source or medium and the campaign is getting captured in GA. Because when I check the report I a not seeing any source /medium with name as test
What could be possibly wrong?? I am getting UTM parameters when I navigate but in GA it is not getting captured.
Any suggestion!!!
Julius Fedorovicius,
I have implemented the most up to date version of the custom HTML. two problems have surfaced:
1. The URL generated is using encoding for all punctuation, how can I get around this?
2. The custom HTML is appending to more than just the two external links I coded, how can I limit this?
output of UTMs on external domain
%3Futm_campaign%3DFUN%26utm_medium%3DIS%26utm_source%3DThis
weirder yet is that the external link I didnt ask for to be UTM appended actually read
&utm_campaign=FUN&utm_medium=IS&utm_source=This.
Please help me fix the two problems, if possible.
thanks
chris
Hi!
I need to pass the utm tags on to all the pages on the same domain, can this solution work for that?
Because i have a form that collects that data (via hidden field), so we can know wich constumer came from wich channel, but i still get a lot of "blanks" or direct conversions.
I'll appreciate the help, thanks!!
Yup! This will solve that problem for you. Just remember though, The form they fill out might not be the form / page they entered on. So you'll need to account for that in your reporting.
Hi Julius,
thanks for this code. We've been using it for a month. However after analyzing Google Analytics data, some of the sessions don't pass queries. We thought it's because GTM loads the tag slow. that's why we injected the code before tag via a wordpress plugin. It works but it duplicates every parameter in the query. We made sure we paused the GTM tag. We don't know why it happens and thought maybe you have a solution/idea for it.
Thanks.
Hi Julius,
Been using your code for about a month now passing utm_source, utm_medium, etc. All is well, except:
"Advanced Search on site".
One of our pages has a advanced search feature. When a user selects his search requirements and clicks on search, the advanced search appends its own queries related to our website product and url changes to domain.com/page/?dimension1=2&dimension2=4
So we loose all queries passed through your code (i.e. utm_source, utm_medium, etc..)
Any ideas how to rectify?
Thanks/ AW.
Hi Julius!
That's a great workaround. Here's one scenario I noticed where the script doesn't work:
User lands on a page with the UTM parameters > Clicks on an internal link on that page > on this second page clicks on a URL that is supposed to be decorated.
As UTMs don't get passed on internally in the URL that probably causes this. And I assume it wouldn't make any sense to implement it internally either?
Best regards,
Heiman
Hi, The script was never meant to persist the data across the pages. You will have to use cookies to enhance the solution by yourself.
Hi Julius.
I found your article very useful and I would like to share the following snippet that allowed me to dynamically obtain all the query parameters.
function getParams() {
var params = [],
searchParams = new URLSearchParams(window.location.search.slice(1));
for(var pair of searchParams.entries()) {
params.push(pair[0]);
}
return params;
}
Best regards,
Amer
First of all, i will like to thanks you for this post, I followed the steps and finally i thought can work, but it only work in preview and debug mode. I don't know the reason why it only works in preview and debug mode but not working in actual.
anyway, i found a quick solution by a wordpress plugin (UTMs Carry Pages)
it will only carry UMT, if other reference, you might need self edit the plugin
If something works only in tpreview mode, it means that you have to publish your changes
Really good, well explained information. Thank you.
Hi Julius,
Thanks a lot for these very helpful instructions!
I have one follow-up question as I have a special use case:
It generally works now on my page but I have outgoing links that are not clearly visible to the script because they are contained in a Woomcommerce button (like an add-to-cart button but for outgoing links). So the script wasn't able to detect them and add the parameters to the links in these buttons.
Do you have an idea how I could modify the script to also look into these buttons to change links?
Kind regards,
Ben
I was debugging the page in question with google tag manager and I can see the UTMs being appended to the link in the browser but when I get to the new page the information gets lost. Unfortunately, the checkout page that i'm directed to can't have GTM. Only the direct integration with GA...
Can you help?
Thank you,
Adam
Sounds like that website is losing the UTMs so my guess would be for you to talk with a developer of that website and ask to persist those UTMs in the URL.