Tracking codes and scripts (Google Analytics, Meta, Clarity)

Tracking codes (Google Analytics 4, Google Tag Manager, Meta Pixel, Microsoft Clarity, Hotjar) are short snippets of code that the tool needs in the head of every page. Magento has one field for them.

Tracking codes may only run once the customer has consented to analytics and marketing cookies. Code entered directly into the page head is loaded straight away, without consent. That is why we recommend that we add tracking codes for you through the consent module, which switches them on only after the customer has made their choice. Use the steps below only for code that does not need consent (for example site ownership verification for Search Console).

Before you start

the code the tool gave you (it starts with <script> or <meta>),
the shop language or languages it should apply to.

Where the code goes

Content › Design › Configuration

In the list, find the row with the store view (the Store View column, for example Slovenian) and click Edit. If the code should apply to all languages, edit the website row (the Website column filled in, Store View empty).

Edit on a store view row: settings for one language.
Expand Other Settings and then HTML Head.
Paste the code into the Scripts and Style Sheets field. If the field is locked, first untick Use Default Value to the right of it. Do not delete the existing content; add the new code below it.

Scripts and Style Sheets - this is where code the tool needs in the page head goes.
Click Save Configuration and flush the cache (how).

Code that the tool wants "before the closing body tag" (for example some chat widgets) goes into the Footer › Miscellaneous HTML section on the same page.

Check that the code works

Open the shop in your browser, accept cookies and check the live data in the tool (in Google Analytics, Reports › Realtime).
If there is no data, check that you saved the code in the right store view and flushed the cache.

Tracking purchases

The code on its own measures page visits. For purchase data (order value, products, checkout funnel), the shop has to send events from the cart and checkout to the tool. We set this up for you with a tracking module; just send us your measurement ID (GA4 G-..., Meta Pixel ID).

Common problems

After adding the code, the page is blank or broken

The code is incomplete (a closing tag is missing) or was changed while copying. Open the field, remove the code, save, and email the code to us.

Analytics shows visits but no purchases

Purchase events have not been set up. See the Tracking purchases section.

The code only works in one language

It was entered for the store view of one language. Enter it for the other language too, or at website level.

Was this article helpful?

Where to edit which textContent and design Pages: about us, terms, deliveryContent and design Blocks: notices and page sectionsContent and design SEO basics: meta data, robots.txt and the sitemapContent and design Address redirects (301) and URL rewritesContent and design

Cookie name	Cookie purpose
PHPSESSID	Preserves the visitor's session state across page requests.
magelan_geo	Remembers that the visitor closed the suggestion of the other language version of the store, so it is not shown again.
form_key	Protects visitor's data from Cross-Site Request Forgery Attacks.
guest-view	Stores the Order ID that guest shoppers use to retrieve their order status. Used in “Orders and Returns” widgets.
login_redirect	Preserves the destination page the customer was loading before being directed to log in.
mage-banners-cache-storage	Stores banner content locally to improve performance.
mage-cache-sessid	The value of this cookie triggers the cleanup of local cache storage.
mage-cache-storage	Local storage of visitor-specific content that enables ecommerce functions.
mage-cache-storage-section-invalidation	Forces local storage of specific content sections that should be invalidated.
mage-messages	Tracks error messages and other notifications that are shown to the user, such as the cookie consent message, and various error messages. The message is deleted from the cookie after it is shown to the shopper.
private_content_version	Appends a random, unique number and time to pages with customer content to prevent them from being cached on the server.
section_data_ids	Stores customer-specific information related to shopper-initiated actions such as display wish list, checkout information, etc.
user_allowed_save_cookie, cookie_consent	Stores the user's cookie consent state for the current domain.
X-Magento-Vary	Configuration setting that improves performance when using Varnish static content caching.

Cookie name	Cookie purpose
product_data_storage	Stores configuration for product data related to Recently Viewed / Compared Products.
recently_compared_product	Stores product IDs of recently compared products.
recently_compared_product_previous	Stores product IDs of previously compared products for easy navigation.
recently_viewed_product	Stores product IDs of recently viewed products for easy navigation.
recently_viewed_product_previous	Stores product IDs of recently previously viewed products for easy navigation.
_fbp	This cookie is installed by Facebook to store and track visits across websites.

Cookie name	Cookie purpose
dc_gtm_*	Throttles request rate when Google Analytics is deployed with Google Tag Manager.
_ga, _gat, _gid, _ga_, _gat_	This cookie is installed by Google Analytics. They are used to collect information about how visitors use our website. We use the information to compile reports and to help us improve the website. The cookies collect information in a way that does not directly identify anyone.

Tracking codes and scripts (Google Analytics, Meta, Clarity)

Where the code goes

Check that the code works

Tracking purchases

Common problems

Related

Cookie preferences