Google utm install#

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. Why not implement GA cross-domain tracking? The problem is that Google Analytics will attribute this conversion to, although it would be more beneficial to see the values of the initial UTMs. Notice that UTM parameters are lost after the visitor clicks an link on page. Heres’ the scheme of the entire visitor journey: The visitor lands on the initial page, he clicks that CTA button, lands on the App Store page and installs the app. 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. You have also marked all inbound links (stored on other websites/forums/etc.) that lead visitors to that landing page with UTM parameters. So you decided to create a separate landing page that you’ll drive traffic to. We’ll call it Lorem Appsum. Its App Store page isn’t sufficient to list all the benefits, cool features, etc. Say, that you’re promoting a product that is available in the App Store (for example, Shopify App Store). In this blog post, I’ll show you how to transfer UTM parameters (or basically any URL parameters) from the initial page to the subsequent one ( ) if the cross-domain tracking cannot be implemented. 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). Technically, this is correct because all visitors landed on the from, but you’d like to see the original source which brought the visitor, wouldn’t you? Unfortunately, when you look at your GA reports, what you’ll see is that all conversions are attributed to the. When the conversion is completed, a Google Analytics event is fired.

Google utm install#

GET YOUR DISCOUNT), he/she is redirected to another page ( ) which asks a visitor to do the final action, install the app, fill in the form, sign up, etc. After the visitor clicks the main Call-to-action button (e.g. You’re running a promo campaign that brings traffic to a certain landing page (e.g. If the destination URL contains a hashmark (#), you should try using the older version. However, in some situations, the older version of this solution is recommended.

I have completely redone this solution to support more cases and require less configuration.