# Translation of Plugins - GTM4WP – A Google Tag Manager (GTM) plugin for WordPress - Stable (latest release) in English (UK) # This file is distributed under the same license as the Plugins - GTM4WP – A Google Tag Manager (GTM) plugin for WordPress - Stable (latest release) package. msgid "" msgstr "" "PO-Revision-Date: 2026-09-05 11:16:29+0000\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Generator: GlotPress/4.1.0\n" "Language: en_GB\n" "Project-Id-Version: Plugins - GTM4WP – A Google Tag Manager (GTM) plugin for WordPress - Stable (latest release)\n" #: src/Admin/SettingsPage.php:139 msgid "Please pause the blocker for the admin area of this site, or add an exception for it, and reload this page. If the screen still stays empty, please check the browser console for errors, check on the Network tab whether admin.js loads from the plugin folder, and verify that all plugin files were uploaded completely." msgstr "Please pause the blocker for the admin area of this site, or add an exception for it, and reload this page. If the screen still stays empty, please check the browser console for errors, check on the Network tab whether admin.js loads from the plugin folder, and verify that all plugin files were uploaded completely." #: src/Admin/SettingsPage.php:138 msgid "This screen is built in the browser by a JavaScript file loaded from the plugin folder (build/admin.js), and that file did not run. The most likely cause is an ad or privacy blocker: some filter lists block everything under the folder of this plugin, and that also blocks the file this screen is built from." msgstr "This screen is built in the browser by a JavaScript file loaded from the plugin folder (build/admin.js), and that file did not run. The most likely cause is an ad or privacy blocker: some filter lists block everything under the folder of this plugin, and that also blocks the file this screen is built from." #: src/Admin/SettingsPage.php:137 msgid "The GTM4WP settings screen could not start." msgstr "The GTM4WP settings screen could not start." #: src/Modules/WooCommerce/StoreApiData.php:152 msgid "GA4 ecommerce item data for the cart line, JSON encoded." msgstr "GA4 e-commerce item data for the basket line, JSON encoded." #: src/Modules/WooCommerce/StoreApiData.php:136 msgid "GA4 ecommerce item data for the product." msgstr "GA4 e-commerce item data for the product." #: src/Modules/WooCommerce/ListTracking.php:337 msgid "Product Collection" msgstr "Product Collection" #: src/Modules/WooCommerce/ListTracking.php:334 msgid "Cart Contents" msgstr "Basket Contents" #: src/Modules/WooCommerce/ListTracking.php:331 msgid "Products By Brand" msgstr "Products By Brand" #: src/Modules/WooCommerce/ListTracking.php:328 msgid "Products By Tag" msgstr "Products By Tag" #: src/Modules/WooCommerce/ListTracking.php:325 msgid "Product Category List" msgstr "Product Category List" #: src/Modules/WooCommerce/ListTracking.php:322 msgid "Handpicked Products" msgstr "Handpicked Products" #: src/Modules/WooCommerce/ListTracking.php:319 msgid "New Products" msgstr "New Products" #: src/Modules/WooCommerce/AdminSchema.php:427 msgid "WooCommerce 5.0 or newer needs to be installed and activated to use this module." msgstr "WooCommerce 5.0 or newer needs to be installed and activated to use this module." #. translators: 1: opening anchor tag linking to the CheckoutWC website. 2: #. closing anchor tag. #: src/Modules/WooCommerce/AdminSchema.php:407 msgid "Enable this if your store uses %1$sCheckoutWC%2$s, which replaces the standard WooCommerce checkout with its own multi-step template. The classic checkout markers the tracker relies on are not reliably present there, so the add_shipping_info and add_payment_info events are missed. With this on, the tracker also binds those events to CheckoutWC's own cfw_step_changed event." msgstr "Enable this if your store uses %1$sCheckoutWC%2$s, which replaces the standard WooCommerce checkout with its own multi-step template. The classic checkout markers the tracker relies on are not reliably present there, so the add_shipping_info and add_payment_info events are missed. With this on, the tracker also binds those events to CheckoutWC's own cfw_step_changed event." #: src/Modules/WooCommerce/AdminSchema.php:404 msgid "CheckoutWC compatibility" msgstr "CheckoutWC compatibility" #: src/Modules/WooCommerce/AdminSchema.php:396 msgid "When a user clicks on a product in a list, the select_item event uses a callback function with Google Tag Manager (GTM). This ensures that GTM can fire all related tags before the browser navigates to the product detail page. You can customize a timeout period (in milliseconds). This timeout only comes into play if a tag fails to fire within the specified time for some reason. Set this to 0 to open the product immediately without waiting for GTM: the select_item event is still pushed to the data layer, but the click is no longer held back. Use 0 (or a lower value than 2000) if product links feel slow to open - for example when a consent tool blocks GTM so the callback never returns." msgstr "When a user clicks on a product in a list, the select_item event uses a callback function with Google Tag Manager (GTM). This ensures that GTM can fire all related tags before the browser navigates to the product detail page. You can customise a timeout period (in milliseconds). This timeout only comes into play if a tag fails to fire within the specified time for some reason. Set this to 0 to open the product immediately without waiting for GTM: the select_item event is still pushed to the data layer, but the click is no longer held back. Use 0 (or a lower value than 2000) if product links feel slow to open - for example when a consent tool blocks GTM so the callback never returns." #: src/Modules/WooCommerce/AdminSchema.php:368 msgid "If your theme or another plugin shows the order confirmation on a custom page instead of the standard WooCommerce order received endpoint, select it here so the purchase event fires on it. The order is resolved from the current browser session." msgstr "If your theme or another plugin shows the order confirmation on a custom page instead of the standard WooCommerce order received endpoint, select it here so the purchase event fires on it. The order is resolved from the current browser session." #: src/Modules/WooCommerce/AdminSchema.php:367 msgid "Custom order received (thank-you) page" msgstr "Custom order received (thank-you) page" #: src/Modules/WooCommerce/AdminSchema.php:358 msgid "Turn this on if some purchases are missing. When the customer lands on a heavily customized thank-you page, or on the order-pay page instead of the order received page, the purchase event is emitted on the next page they view in the same browser session instead. The order tracked flag and browser cookie still prevent double counting. Note: this cannot capture orders where the buyer pays via an asynchronous gateway and never returns to the site - that case needs server side tracking." msgstr "Turn this on if some purchases are missing. When the customer lands on a heavily customised thank-you page, or on the order-pay page instead of the order received page, the purchase event is emitted on the next page they view in the same browser session instead. The order tracked flag and browser cookie still prevent double counting. Note: this cannot capture orders where the buyer pays via an asynchronous gateway and never returns to the site - that case needs server side tracking." #: src/Modules/WooCommerce/AdminSchema.php:357 msgid "Reliable purchase tracking" msgstr "Reliable purchase tracking" #: src/Modules/WooCommerce/AdminSchema.php:347 msgid "The purchase event is sent when an order first reaches one of these statuses, i.e. at order placement - not when payment physically clears. This is why Cash on Delivery (Processing) and bank transfer (On hold) orders are tracked at checkout even though the money arrives later. Leave Failed, Cancelled and Pending payment unchecked so unpaid orders are not counted as sales." msgstr "The purchase event is sent when an order first reaches one of these statuses, i.e. at order placement - not when payment physically clears. This is why Cash on Delivery (Processing) and bank transfer (On hold) orders are tracked at checkout even though the money arrives later. Leave Failed, Cancelled and Pending payment unchecked so unpaid orders are not counted as sales." #: src/Modules/WooCommerce/AdminSchema.php:346 msgid "Order statuses that trigger the purchase event" msgstr "Order statuses that trigger the purchase event" #: src/Modules/WooCommerce/AdminSchema.php:329 msgid "Text to prepend to the transaction_id sent with the purchase event, for example to tell several stores apart in one GA4 property or to match the order id format of another system. Leave this empty to send the WooCommerce order number unchanged. Only the purchase event is affected: the order number in the orderData variable and the duplicate tracking guards of the plugin keep using the raw order number." msgstr "Text to prepend to the transaction_id sent with the purchase event, for example to tell several stores apart in one GA4 property or to match the order id format of another system. Leave this empty to send the WooCommerce order number unchanged. Only the purchase event is affected: the order number in the orderData variable and the duplicate tracking guards of the plugin keep using the raw order number." #: src/Modules/WooCommerce/AdminSchema.php:328 msgid "Transaction ID prefix" msgstr "Transaction ID prefix" #: src/Modules/WooCommerce/AdminSchema.php:292 msgid "Enable this to add all order attributes into the data layer on the order received page regardless and independently from ecommerce tracking" msgstr "Enable this to add all order attributes into the data layer on the order received page regardless and independently from e-commerce tracking" #: src/Modules/WooCommerce/AdminSchema.php:274 msgid "Enable this option to include the content of the cart in the data layer on each page. Especially useful for site personalization tools." msgstr "Enable this option to include the content of the basket in the data layer on each page. Especially useful for site personalisation tools." #: src/Modules/WooCommerce/AdminSchema.php:264 msgid "When a visitor clicks a product in a list, remember which list it was (item_list_name / item_list_id) in a first-party cookie and carry it onto the later view_item, add_to_cart, begin_checkout, add_shipping_info, add_payment_info and purchase events, so GA4 can attribute the whole funnel to the originating list. On a product page the list is merged in by the browser rather than by the server, so the attribution also works when the page is served from a full-page cache. Only enable this if you are NOT already doing the same with custom JavaScript in Google Tag Manager, otherwise the attribution would be set twice." msgstr "When a visitor clicks a product in a list, remember which list it was (item_list_name / item_list_id) in a first-party cookie and carry it onto the later view_item, add_to_cart, begin_checkout, add_shipping_info, add_payment_info and purchase events, so GA4 can attribute the whole funnel to the originating list. On a product page the list is merged in by the browser rather than by the server, so the attribution also works when the page is served from a full-page cache. Only enable this if you are NOT already doing the same with custom JavaScript in Google Tag Manager, otherwise the attribution would be set twice." #: src/Modules/WooCommerce/AdminSchema.php:263 msgid "Persist product list attribution across the funnel" msgstr "Persist product list attribution across the funnel" #: src/Modules/WooCommerce/AdminSchema.php:172 msgid "Choose this option if you would like to track e-commerce data with GA4 ecommerce tracking." msgstr "Choose this option if you would like to track e-commerce data with GA4 e-commerce tracking." #: src/Modules/WooCommerce/AdminSchema.php:145 msgid "(use the standard WooCommerce order received page)" msgstr "(use the standard WooCommerce order received page)" #: src/Modules/WooCommerce/AdminSchema.php:139 msgid "Failed" msgstr "Failed" #: src/Modules/WooCommerce/AdminSchema.php:138 msgid "Refunded" msgstr "Refunded" #: src/Modules/WooCommerce/AdminSchema.php:137 msgid "Cancelled" msgstr "Cancelled" #: src/Modules/WooCommerce/AdminSchema.php:136 msgid "Completed" msgstr "Completed" #: src/Modules/WooCommerce/AdminSchema.php:135 msgid "On hold" msgstr "On hold" #: src/Modules/WooCommerce/AdminSchema.php:134 msgid "Processing" msgstr "Processing" #: src/Modules/WooCommerce/AdminSchema.php:133 msgid "Pending payment" msgstr "Pending payment" #: src/Modules/WooCommerce/AdminSchema.php:101 msgid "(not used)" msgstr "(not used)" #: src/Modules/WooCommerce/AdminSchema.php:89 msgid "Purchase tracking" msgstr "Purchase tracking" #: src/Modules/WooCommerce/AdminSchema.php:88 msgid "Data layer content" msgstr "Data layer content" #: src/Modules/WooCommerce/AdminSchema.php:87 msgid "Product data" msgstr "Product data" #. translators: 1: anchor element linking to GA4 Ecommerce docs. 2: closing #. anchor element. 3: anchor element linking to GTM4WP setup guide for Google #. Analytics 4. 4: closing anchor element. #: src/Modules/WooCommerce/AdminSchema.php:68 msgid "Track e-commerce data using %1$sGA4 ecommerce tracking%2$s. Use the plugin's %3$sofficial guides%4$s to setup your Google Tag Manager container. WooCommerce 5.0+ is required to use this integration." msgstr "Track e-commerce data using %1$sGA4 e-commerce tracking%2$s. Use the plugin's %3$sofficial guides%4$s to setup your Google Tag Manager container. WooCommerce 5.0+ is required to use this integration." #: src/Modules/VisitorData/AdminSchema.php:81 msgid "Enable this if your site uses full-page caching and you want to avoid leaking one visitor's data (IP, logged-in user email/username/role, WooCommerce customer and cart) to another visitor through the cached HTML. When on, these visitor/session values are kept out of the cached HTML and delivered in the browser instead, under the same data layer variable names, so your Google Tag Manager tags keep working: the referrer and search term are computed by the browser itself; the visitor IP, Cloudflare country and logged-in user data come from a first-party endpoint that returns only the current visitor's own data (the IP/country fetched once per session, the user data only when the login state changes, so anonymous visitors never fetch it); and the WooCommerce customer and cart ride WooCommerce's own cart-refresh request, adding no extra page request. Because the values now arrive after the page view, point the tags that read them at the matching Custom Event trigger: gtm4wp.visitorData for the visitor and logged-in user variables, gtm4wp.customerData for the WooCommerce customer variables and gtm4wp.cartData for the cart content. Each of the three fires only when its own data changed, and only when you have the option that produces it enabled. The two WooCommerce one-shot events (an add_to_cart after the cart \"Undo\" and the reliable-purchase fallback) are delivered client-side too, each fired exactly once. Off by default." msgstr "Enable this if your site uses full-page caching and you want to avoid leaking one visitor's data (IP, logged-in user email/username/role, WooCommerce customer and basket) to another visitor through the cached HTML. When on, these visitor/session values are kept out of the cached HTML and delivered in the browser instead, under the same data layer variable names, so your Google Tag Manager tags keep working: the referrer and search term are computed by the browser itself; the visitor IP, Cloudflare country and logged-in user data come from a first-party endpoint that returns only the current visitor's own data (the IP/country fetched once per session, the user data only when the login state changes, so anonymous visitors never fetch it); and the WooCommerce customer and basket ride WooCommerce's own basket-refresh request, adding no extra page request. Because the values now arrive after the page view, point the tags that read them at the matching Custom Event trigger: gtm4wp.visitorData for the visitor and logged-in user variables, gtm4wp.customerData for the WooCommerce customer variables and gtm4wp.cartData for the basket content. Each of the three fires only when its own data changed, and only when you have the option that produces it enabled. The two WooCommerce one-shot events (an add_to_cart after the basket \"Undo\" and the reliable-purchase fallback) are delivered client-side too, each fired exactly once. Off by default." #: src/Modules/VisitorData/AdminSchema.php:80 msgid "Enable cache-safe data layer" msgstr "Enable cache-safe data layer" #: src/Modules/VisitorData/AdminSchema.php:55 msgid "On sites with full-page caching (LiteSpeed, WP Rocket, Varnish, Cloudflare APO), the HTML built for one visitor is served to everyone. Any visitor-specific value baked into the data layer would then leak to other visitors. This mode keeps those values out of the cached HTML." msgstr "On sites with full-page caching (LiteSpeed, WP Rocket, Varnish, Cloudflare APO), the HTML built for one visitor is served to everyone. Any visitor-specific value baked into the data layer would then leak to other visitors. This mode keeps those values out of the cached HTML." #: src/Modules/VisitorData/AdminSchema.php:46 #: src/Modules/VisitorData/AdminSchema.php:65 msgid "Cache-safe data layer" msgstr "Cache-safe data layer" #: src/Modules/UserEvents/AdminSchema.php:89 msgid "Check this option to push gtm4wp.formElementLeave only for a field that was empty when the visitor entered it and holds a value when they leave it, so that tabbing through a form without typing no longer produces an event for every field. Text inputs, textareas and dropdowns are checked this way; checkboxes, radio buttons and buttons are always reported, because they carry no \"empty\" state. A field that was already filled in when the visitor entered it, for example one your theme pre-fills, reports nothing when they leave it unchanged. gtm4wp.formElementEnter is never affected and keeps firing for every field." msgstr "Check this option to push gtm4wp.formElementLeave only for a field that was empty when the visitor entered it and holds a value when they leave it, so that tabbing through a form without typing no longer produces an event for every field. Text inputs, textareas and dropdowns are checked this way; checkboxes, radio buttons and buttons are always reported, because they carry no \"empty\" state. A field that was already filled in when the visitor entered it, for example one your theme pre-fills, reports nothing when they leave it unchanged. gtm4wp.formElementEnter is never affected and keeps firing for every field." #: src/Modules/UserEvents/AdminSchema.php:88 msgid "Only report fields the visitor filled in" msgstr "Only report fields the visitor filled in" #: src/Modules/UserEvents/AdminSchema.php:80 msgid "Check this option to include a Tag Manager event when a visitor moves between elements of a form (comment, contact, etc). Each event describes the field in inputID, inputName and inputClass and its form in formID, formName and formClass, and also populates Google Tag Manager's built-in Form variables: Form ID, Form Classes, Form URL (the form's action, resolved to an absolute URL) and Form Target. Google publishes no built-in Form Name variable, so the form's name attribute stays available on formName only. Note that the keys behind those built-ins are the ones Google Tag Manager's Clicks category reads, so on these events Click ID and Click Classes resolve to the form as well. No field value is ever included." msgstr "Check this option to include a Tag Manager event when a visitor moves between elements of a form (comment, contact, etc). Each event describes the field in inputID, inputName and inputClass and its form in formID, formName and formClass, and also populates Google Tag Manager's built-in Form variables: Form ID, Form Classes, Form URL (the form's action, resolved to an absolute URL) and Form Target. Google publishes no built-in Form Name variable, so the form's name attribute stays available on formName only. Note that the keys behind those built-ins are the ones Google Tag Manager's Clicks category reads, so on these events Click ID and Click Classes resolve to the form as well. No field value is ever included." #: src/Modules/UserEvents/AdminSchema.php:79 msgid "Form fill events" msgstr "Form fill events" #: src/Modules/UserEvents/AdminSchema.php:45 msgid "User events" msgstr "User events" #: src/Modules/PageVariables/AdminSchema.php:442 msgid "The IP addresses or CIDR ranges of the reverse proxies, load balancers and CDNs that sit in front of this site - one per line, or comma separated. This is what makes the custom header above trustworthy: with it set, an X-Forwarded-For list is read from the right (skipping your own hops) and a single-value header such as CF-Connecting-IP is only used when the request really did arrive through one of these addresses. Leave it empty if nothing sits in front of your site. Cloudflare publishes its ranges at cloudflare.com/ips; for a load balancer inside your own network the address is usually a private range such as 10.0.0.0/8." msgstr "The IP addresses or CIDR ranges of the reverse proxies, load balancers and CDNs that sit in front of this site - one per line, or comma separated. This is what makes the custom header above trustworthy: with it set, an X-Forwarded-For list is read from the right (skipping your own hops) and a single-value header such as CF-Connecting-IP is only used when the request really did arrive through one of these addresses. Leave it empty if nothing sits in front of your site. Cloudflare publishes its ranges at cloudflare.com/ips; for a load balancer inside your own network the address is usually a private range such as 10.0.0.0/8." #: src/Modules/PageVariables/AdminSchema.php:441 msgid "Visitor IP - Trusted proxy addresses" msgstr "Visitor IP - Trusted proxy addresses" #: src/Modules/PageVariables/AdminSchema.php:421 msgid "By default, the plugin will check the so called REMOTE_ADDR system variable for IP addresses. In some cases, this might not include the correct address. You may specify a custom header to read the IP address from. Important: an HTTP header is sent by the visitor, so on its own it is a claim and not a fact - anyone can put any address in it. Fill in the trusted proxy addresses below to make this header trustworthy. Without them the plugin keeps reading the header the way it always has, but the value can be chosen by the visitor, so do not use it for anything but analytics." msgstr "By default, the plugin will check the so called REMOTE_ADDR system variable for IP addresses. In some cases, this might not include the correct address. You may specify a custom header to read the IP address from. Important: an HTTP header is sent by the visitor, so on its own it is a claim and not a fact - anyone can put any address in it. Fill in the trusted proxy addresses below to make this header trustworthy. Without them the plugin keeps reading the header the way it always has, but the value can be chosen by the visitor, so do not use it for anything but analytics." #: src/Modules/PageVariables/AdminSchema.php:367 msgid "Check this option to include the role of the logged in user in the visitorType data layer variable. Roles are reported by their slug, a user with several roles reports them comma separated, and a visitor who is not logged in reports visitor-logged-out." msgstr "Check this option to include the role of the logged in user in the visitorType data layer variable. Roles are reported by their slug, a user with several roles reports them comma separated, and a visitor who is not logged in reports visitor-logged-out." #: src/Modules/PageVariables/AdminSchema.php:358 msgid "Check this option to include whether there is a logged in user on your website, in the visitorLoginState data layer variable. The value is either logged-in or logged-out." msgstr "Check this option to include whether there is a logged in user on your website, in the visitorLoginState data layer variable. The value is either logged-in or logged-out." #: src/Modules/PageVariables/AdminSchema.php:340 msgid "Check this option to include the language code of the current page, detected from WPML or Polylang and falling back to the site locale. Useful to segment behavior on multilingual sites." msgstr "Check this option to include the language code of the current page, detected from WPML or Polylang and falling back to the site locale. Useful to segment behaviour on multilingual sites." #: src/Modules/PageVariables/AdminSchema.php:339 msgid "Page language" msgstr "Page language" #: src/Modules/PageVariables/AdminSchema.php:331 msgid "Check this option to include the primary category of the current post as chosen in Yoast SEO or Rank Math (falls back to the first assigned category). This adds two data layer variables: pagePrimaryCategory holds the category slug and pagePrimaryCategoryName holds its display name. Useful as a single content grouping dimension." msgstr "Check this option to include the primary category of the current post as chosen in Yoast SEO or Rank Math (falls back to the first assigned category). This adds two data layer variables: pagePrimaryCategory holds the category slug and pagePrimaryCategoryName holds its display name. Useful as a single content grouping dimension." #: src/Modules/PageVariables/AdminSchema.php:330 msgid "Primary category" msgstr "Primary category" #: src/Modules/PageVariables/AdminSchema.php:322 msgid "Check this option to include whether the current post is marked as sticky." msgstr "Check this option to include whether the current post is marked as sticky." #: src/Modules/PageVariables/AdminSchema.php:321 msgid "Sticky post" msgstr "Sticky post" #: src/Modules/PageVariables/AdminSchema.php:313 msgid "Check this option to include the parent post ID and the depth of the current post in the page hierarchy (0 for top level pages)." msgstr "Check this option to include the parent post ID and the depth of the current post in the page hierarchy (0 for top level pages)." #: src/Modules/PageVariables/AdminSchema.php:312 msgid "Page hierarchy" msgstr "Page hierarchy" #: src/Modules/PageVariables/AdminSchema.php:304 msgid "Check this option to include whether the current post has a featured image set." msgstr "Check this option to include whether the current post has a featured image set." #: src/Modules/PageVariables/AdminSchema.php:303 msgid "Featured image presence" msgstr "Featured image presence" #: src/Modules/PageVariables/AdminSchema.php:295 msgid "Check this option to include the template file assigned to the current post or page (returns \"default\" when no custom template is used). Useful to segment behavior by page layout." msgstr "Check this option to include the template file assigned to the current post or page (returns \"default\" when no custom template is used). Useful to segment behaviour by page layout." #: src/Modules/PageVariables/AdminSchema.php:294 msgid "Page template" msgstr "Page template" #: src/Modules/PageVariables/AdminSchema.php:286 msgid "Check this option to include the number of comments on the current post and whether commenting is open or closed." msgstr "Check this option to include the number of comments on the current post and whether commenting is open or closed." #: src/Modules/PageVariables/AdminSchema.php:285 msgid "Comment count" msgstr "Comment count" #: src/Modules/PageVariables/AdminSchema.php:277 msgid "Check this option to include the number of days elapsed since the current post was published. Useful to segment engagement by fresh versus evergreen content." msgstr "Check this option to include the number of days elapsed since the current post was published. Useful to segment engagement by fresh versus evergreen content." #: src/Modules/PageVariables/AdminSchema.php:276 msgid "Content age in days" msgstr "Content age in days" #: src/Modules/PageVariables/AdminSchema.php:268 msgid "Check this option to include the last modified date of the current post. This will include the same set of date variables as the post date option (full date, year, month, day, day name, hour, minute, ISO and Unix timestamp)." msgstr "Check this option to include the last modified date of the current post. This will include the same set of date variables as the post date option (full date, year, month, day, day name, hour, minute, ISO and Unix timestamp)." #: src/Modules/PageVariables/AdminSchema.php:267 msgid "Last modified date" msgstr "Last modified date" #: src/Modules/PageVariables/AdminSchema.php:259 msgid "Check this option to include the estimated reading time of the current post in minutes (based on 200 words per minute, adjustable with the gtm4wp_reading_time_wpm filter)." msgstr "Check this option to include the estimated reading time of the current post in minutes (based on 200 words per minute, adjustable with the gtm4wp_reading_time_wpm filter)." #: src/Modules/PageVariables/AdminSchema.php:258 msgid "Estimated reading time" msgstr "Estimated reading time" #: src/Modules/PageVariables/AdminSchema.php:250 msgid "Check this option to include the number of words in the current post content. Useful to normalize scroll depth and engagement metrics against the length of the content." msgstr "Check this option to include the number of words in the current post content. Useful to normalise scroll depth and engagement metrics against the length of the content." #: src/Modules/PageVariables/AdminSchema.php:249 msgid "Content word count" msgstr "Content word count" #: src/Modules/PageVariables/AdminSchema.php:219 msgid "The names of the custom fields you actually want in the data layer - one per line, or comma separated. Leave it empty to keep publishing every custom field whose name does not start with an underscore and is not otherwise protected or skipped, which is what the option above does on its own. Filling it in is the safer way to use that option: your Google Tag Manager container only ever needs a handful of keys, and naming them means a field added later by a plugin, a theme or an editor cannot start appearing on your public pages without you deciding it. Protected fields and the gtm4wp_post_meta_in_datalayer filter still apply on top of this list, so naming a field here cannot publish one that is held back for those reasons - a name starting with an underscore is never published however you list it. A field name that contains a comma cannot be listed at all, because commas separate the entries." msgstr "The names of the custom fields you actually want in the data layer - one per line, or comma separated. Leave it empty to keep publishing every custom field whose name does not start with an underscore and is not otherwise protected or skipped, which is what the option above does on its own. Filling it in is the safer way to use that option: your Google Tag Manager container only ever needs a handful of keys, and naming them means a field added later by a plugin, a theme or an editor cannot start appearing on your public pages without you deciding it. Protected fields and the gtm4wp_post_meta_in_datalayer filter still apply on top of this list, so naming a field here cannot publish one that is held back for those reasons - a name starting with an underscore is never published however you list it. A field name that contains a comma cannot be listed at all, because commas separate the entries." #: src/Modules/PageVariables/AdminSchema.php:218 msgid "Post custom fields - publish only these keys" msgstr "Post custom fields - publish only these keys" #: src/Modules/PageVariables/AdminSchema.php:210 msgid "Check this option to include the custom fields (post meta) of the current post in the pagePostTerms.meta data layer variable. Read this before enabling it: this publishes EVERY custom field whose name does not start with an underscore, together with its value, into the data layer of the public page, where any visitor can read it. That includes fields created by other plugins and themes - Advanced Custom Fields stores its values this way - so it may expose internal notes, ids, prices or contact details you did not intend to make public. Review your custom fields first, and use the key list below to name only the ones you need (or the gtm4wp_post_meta_in_datalayer filter to exclude individual keys in code). Custom fields that hold a structured value rather than plain text are skipped: plugins store those in a packed internal format that no Google Tag Manager variable can read. Fields that a plugin or your own site marks as protected are skipped too. Until 2.0 this data was sent as part of the \"Post Terms\" option above; if you had that enabled, this option was turned on for you during the upgrade so your Google Tag Manager setup keeps working." msgstr "Check this option to include the custom fields (post meta) of the current post in the pagePostTerms.meta data layer variable. Read this before enabling it: this publishes EVERY custom field whose name does not start with an underscore, together with its value, into the data layer of the public page, where any visitor can read it. That includes fields created by other plugins and themes - Advanced Custom Fields stores its values this way - so it may expose internal notes, ids, prices or contact details you did not intend to make public. Review your custom fields first, and use the key list below to name only the ones you need (or the gtm4wp_post_meta_in_datalayer filter to exclude individual keys in code). Custom fields that hold a structured value rather than plain text are skipped: plugins store those in a packed internal format that no Google Tag Manager variable can read. Fields that a plugin or your own site marks as protected are skipped too. Until 2.0 this data was sent as part of the \"Post Terms\" option above; if you had that enabled, this option was turned on for you during the upgrade so your Google Tag Manager setup keeps working." #: src/Modules/PageVariables/AdminSchema.php:209 msgid "Post custom fields (meta)" msgstr "Post custom fields (meta)" #: src/Modules/PageVariables/AdminSchema.php:201 msgid "Check this option to include taxonomy values associated with a given post, in the pagePostTerms data layer variable. Custom fields are a separate option below." msgstr "Check this option to include taxonomy values associated with a given post, in the pagePostTerms data layer variable. Custom fields are a separate option below." #: src/Modules/PageVariables/AdminSchema.php:192 msgid "Check this option to include the format of the current post in the postFormat data layer variable. The format is reported by its slug (aside, gallery, video and so on), and posts with no format set report standard." msgstr "Check this option to include the format of the current post in the postFormat data layer variable. The format is reported by its slug (aside, gallery, video and so on), and posts with no format set report standard." #: src/Modules/PageVariables/AdminSchema.php:156 msgid "Check this option to include the date of the current post. This will include 9 dataLayer variables: full date, year, month, day, day name, hour, minute, ISO 8601 date and Unix timestamp. On date based archive pages only the parts the archive covers are included." msgstr "Check this option to include the date of the current post. This will include 9 dataLayer variables: full date, year, month, day, day name, hour, minute, ISO 8601 date and Unix timestamp. On date based archive pages only the parts the archive covers are included." #: src/Modules/PageVariables/AdminSchema.php:147 msgid "Check this option to include the display name of the author on the current post or author page in the pagePostAuthor data layer variable. On a post with several authors (PublishPress Authors) the full list is added as pagePostAuthors as well." msgstr "Check this option to include the display name of the author on the current post or author page in the pagePostAuthor data layer variable. On a post with several authors (PublishPress Authors) the full list is added as pagePostAuthors as well." #: src/Modules/PageVariables/AdminSchema.php:138 msgid "Check this option to include the ID of the author on the current post or author page in the pagePostAuthorID data layer variable. On a post with several authors (PublishPress Authors) the full list is added as pagePostAuthorIDs as well." msgstr "Check this option to include the ID of the author on the current post or author page in the pagePostAuthorID data layer variable. On a post with several authors (PublishPress Authors) the full list is added as pagePostAuthorIDs as well." #: src/Modules/PageVariables/AdminSchema.php:129 msgid "Check this option to include the tags of the current post in the pageAttributes data layer variable. Tags are listed by their slug (for example black-friday), not by their display name." msgstr "Check this option to include the tags of the current post in the pageAttributes data layer variable. Tags are listed by their slug (for example black-friday), not by their display name." #: src/Modules/PageVariables/AdminSchema.php:118 msgid "Check this option to also add the parent (ancestor) categories to the pageCategory data layer variable. When off, only the categories directly assigned to the current post or archive are listed. Requires the \"Category list of current post/archive\" option above to be enabled." msgstr "Check this option to also add the parent (ancestor) categories to the pageCategory data layer variable. When off, only the categories directly assigned to the current post or archive are listed. Requires the \"Category list of current post/archive\" option above to be enabled." #: src/Modules/PageVariables/AdminSchema.php:117 msgid "Include parent categories in the category list" msgstr "Include parent categories in the category list" #: src/Modules/PageVariables/AdminSchema.php:109 msgid "Check this option to include the categories of the current post or archive page in the pageCategory data layer variable. Categories are listed by their slug (for example news-and-events), not by their display name." msgstr "Check this option to include the categories of the current post or archive page in the pageCategory data layer variable. Categories are listed by their slug (for example news-and-events), not by their display name." #: src/Modules/PageVariables/AdminSchema.php:84 msgid "Site data" msgstr "Site data" #: src/Modules/PageVariables/AdminSchema.php:83 msgid "Visitor data" msgstr "Visitor data" #: src/Modules/PageVariables/AdminSchema.php:81 msgid "Content & engagement data" msgstr "Content & engagement data" #: src/Modules/PageVariables/AdminSchema.php:80 msgid "Post data" msgstr "Post data" #: src/Modules/PageVariables/AdminSchema.php:61 msgid "Page variables" msgstr "Page variables" #: src/Modules/MediaEvents/AdminSchema.php:211 msgid "By default the media trackers on the Media players tab only wire players that are present when the page loads. Check this option to also track players inserted after page load — e.g. opened in a popup/lightbox or loaded via AJAX — by watching the page for new embeds. This adds a single shared MutationObserver on the page, which has a small per-change cost, so leave it off unless your site injects media players at runtime." msgstr "By default the media trackers on the Media players tab only wire players that are present when the page loads. Check this option to also track players inserted after page load — e.g. opened in a pop-up/lightbox or loaded via Ajax — by watching the page for new embeds. This adds a single shared MutationObserver on the page, which has a small per-change cost, so leave it off unless your site injects media players at runtime." #: src/Modules/MediaEvents/AdminSchema.php:210 msgid "Track dynamically inserted players" msgstr "Track dynamically inserted players" #: src/Modules/MediaEvents/AdminSchema.php:201 msgid "Check this option to include a Tag Manager event when a visitor interacts with a Twitch stream or video embedded on your site. Each event also populates Google Tag Manager's built-in Video variables. Note: current time and duration are only available for videos (VODs), not live streams." msgstr "Check this option to include a Tag Manager event when a visitor interacts with a Twitch stream or video embedded on your site. Each event also populates Google Tag Manager's built-in Video variables. Note: current time and duration are only available for videos (VODs), not live streams." #: src/Modules/MediaEvents/AdminSchema.php:200 msgid "Twitch events" msgstr "Twitch events" #: src/Modules/MediaEvents/AdminSchema.php:191 msgid "Check this option to include a Tag Manager event when a visitor interacts with a Spotify track, episode or playlist embedded on your site. Each event also populates Google Tag Manager's built-in Video variables. Note: the Spotify embed only reports periodic playback updates, so play, pause and finished states are derived from those updates, and it reports no title at all - the title is read from the embed on the page, and only when the embed carries none is it looked up once from Spotify's public oEmbed endpoint." msgstr "Check this option to include a Tag Manager event when a visitor interacts with a Spotify track, episode or playlist embedded on your site. Each event also populates Google Tag Manager's built-in Video variables. Note: the Spotify embed only reports periodic playback updates, so play, pause and finished states are derived from those updates, and it reports no title at all - the title is read from the embed on the page, and only when the embed carries none is it looked up once from Spotify's public oEmbed endpoint." #: src/Modules/MediaEvents/AdminSchema.php:190 msgid "Spotify events" msgstr "Spotify events" #: src/Modules/MediaEvents/AdminSchema.php:181 msgid "Check this option to include a Tag Manager event when a visitor interacts with a VideoPress (Jetpack/WordPress.com) video embedded on your site. Each event also populates Google Tag Manager's built-in Video variables." msgstr "Check this option to include a Tag Manager event when a visitor interacts with a VideoPress (Jetpack/WordPress.com) video embedded on your site. Each event also populates Google Tag Manager's built-in Video variables." #: src/Modules/MediaEvents/AdminSchema.php:180 msgid "VideoPress video events" msgstr "VideoPress video events" #: src/Modules/MediaEvents/AdminSchema.php:171 msgid "Check this option to include a Tag Manager event when a visitor interacts with a JW Player video embedded on your site. Each event also populates Google Tag Manager's built-in Video variables." msgstr "Check this option to include a Tag Manager event when a visitor interacts with a JW Player video embedded on your site. Each event also populates Google Tag Manager's built-in Video variables." #: src/Modules/MediaEvents/AdminSchema.php:170 msgid "JW Player video events" msgstr "JW Player video events" #: src/Modules/MediaEvents/AdminSchema.php:161 msgid "Check this option to include a Tag Manager event when a visitor interacts with a Wistia video embedded on your site. Each event also populates Google Tag Manager's built-in Video variables." msgstr "Check this option to include a Tag Manager event when a visitor interacts with a Wistia video embedded on your site. Each event also populates Google Tag Manager's built-in Video variables." #: src/Modules/MediaEvents/AdminSchema.php:160 msgid "Wistia video events" msgstr "Wistia video events" #: src/Modules/MediaEvents/AdminSchema.php:151 msgid "Check this option to include a Tag Manager event when a visitor interacts with a Cloudflare Stream video embedded on your site. Each event also populates Google Tag Manager's built-in Video variables." msgstr "Check this option to include a Tag Manager event when a visitor interacts with a Cloudflare Stream video embedded on your site. Each event also populates Google Tag Manager's built-in Video variables." #: src/Modules/MediaEvents/AdminSchema.php:150 msgid "Cloudflare Stream video events" msgstr "Cloudflare Stream video events" #: src/Modules/MediaEvents/AdminSchema.php:141 msgid "Check this option to include a Tag Manager event when a visitor interacts with a Mixcloud show embedded on your site. Each event also populates Google Tag Manager's built-in Video variables." msgstr "Check this option to include a Tag Manager event when a visitor interacts with a Mixcloud show embedded on your site. Each event also populates Google Tag Manager's built-in Video variables." #: src/Modules/MediaEvents/AdminSchema.php:140 msgid "Mixcloud events" msgstr "Mixcloud events" #: src/Modules/MediaEvents/AdminSchema.php:130 msgid "Optional. The ID of the player configuration to load, found in the Players tab of your Dailymotion Studio account. Leave it empty to use Dailymotion's default player, which needs no account. Filling it in is also what removes Dailymotion's \"initialized without a player id\" console warning. If an embed code already names a player of its own, that one is used for that embed regardless of this setting." msgstr "Optional. The ID of the player configuration to load, found in the Players tab of your Dailymotion Studio account. Leave it empty to use Dailymotion's default player, which needs no account. Filling it in is also what removes Dailymotion's \"initialised without a player ID\" console warning. If an embed code already names a player of its own, that one is used for that embed regardless of this setting." #: src/Modules/MediaEvents/AdminSchema.php:129 msgid "Dailymotion player ID" msgstr "Dailymotion player ID" #: src/Modules/MediaEvents/AdminSchema.php:120 msgid "Check this option to include a Tag Manager event when a visitor interacts with a Dailymotion video embedded on your site. Each event also populates Google Tag Manager's built-in Video variables. Note: Dailymotion no longer lets any script listen to a video it did not create itself, so tracking works by rebuilding each embed with Dailymotion's current player. The video keeps the size WordPress gave it and plays as before, but the player your visitors see is the one Dailymotion builds - see the player ID setting below. If the player library cannot be loaded, the embed is left exactly as it was and simply goes untracked." msgstr "Check this option to include a Tag Manager event when a visitor interacts with a Dailymotion video embedded on your site. Each event also populates Google Tag Manager's built-in Video variables. Note: Dailymotion no longer lets any script listen to a video it did not create itself, so tracking works by rebuilding each embed with Dailymotion's current player. The video keeps the size WordPress gave it and plays as before, but the player your visitors see is the one Dailymotion builds - see the player ID setting below. If the player library cannot be loaded, the embed is left exactly as it was and simply goes untracked." #: src/Modules/MediaEvents/AdminSchema.php:119 msgid "Dailymotion video events" msgstr "Dailymotion video events" #: src/Modules/MediaEvents/AdminSchema.php:110 msgid "Check this option to include a Tag Manager event when a visitor interacts with a native HTML5