Create Content

The Mapp Intelligence plugin provides basic tracking for WordPress and advanced e-commerce tracking for WooCommerce.

The plugin provides the following features:

  • loading the tiLoader, which is needed to start tracking page and action requests.
  • providing a data layer in a window._ti object
  • in WooCommerce, the plugin also fires trackrequests when adding an item to the cart.

If you want to use Google Tag Manager instead of Tag Integration, you can find all infos here: Google Tag Manager in conjunction with Wordpress / Woocommerce


Learn how to install the Mapp Intelligence plugin in your Wordpress instance.

Installation via the WordPress UI

Log in to Wordpress as admin and go to your dashboard. Then click "Plugins" and "Add New" and search for "Mapp Intelligence". Once found, click the "Install Now" button.

Manually Uploading the WordPress Plugin

Download the plugin from the WordPress plugin website and unzip its content in your WordPress plugin directory, e.g. wp-content/plugins.

Then, log in to WordPress as an admin, go to Plugins in the main menu and click "activate" under the Mapp Intelligence entry in Installed Plugins.


After activating the Mapp Intelligence plugin in WordPress, you find the entry "Mapp Intelligence" under "Plugins" in the main menu of your dashboard.

Mapp Intelligence Pixel VersionChose between V5 pixel (Tag Integration) and Smartpixel. Right now only V5 is available.
Tag Integration IDThe Tag Integration ID is provided by Mapp.
Tag Integration DomainFor better data quality, you can book a custom responder domain. If you use the default responder, keep "".
Exclude keysThe plugin will create a Javascript object in window context called _ti. You can find out more about the Datalayer section below. Here you can enter the name of keys you do not want to have in the _ti object. Separate multiple entries with a comma. By default, customFields is blacklisted - customFields stores the data provided by other plugins, so check carefully if you want to whitelist the entries in customFields by deleting the key from the text field.
Exclude usersActivate this checkbox if you do not want to track users who are logged in to the admin panel of your WordPress installation (e.g. to edit blog posts or product information). Traffic in the WordPress admin panel is never tracked. However, when previewing a page from there, tracking is activated by default.


The Mapp Intelligence Plugin creates an object called "_ti" in global context. In Tag Integration, you can map the keys in the parameter section.

For example, _ti.pageName stores the URL of the current page. To map this key as the name of the page, create a parameter like so:

Then, in  your Mapp Intelligence plugin, map it under "Page → Page name" like so:

Now all trackrequests will receive the name of the page from the _ti datalayer object.

The plugin automatically creates the following keys in the datalayer object.

General Wordpress data

pageNameURL without the http(s) protocol URL parameters
pageTitleTitle of the page.
languageLanguage code.
contentCategoryValues can be: page, post, product etc.
contentSubcategoryValues can be: single-page, single-post, category-post etc.
orderByOn archive pages only. "default" if no particular order is set.
pageNumberOn archive pages only.
internalSearchOn search result pages only: search term.
numberSearchResultsOn search result pages only: amount of search result as a string.
taxonomiesObject with taxonomies. By default, Wordpress comes with two taxonomies: category and tags. Categories are sorted from lowest to highest level, so if you'd want to map the lowest category level, you'd use "_ti.taxonomies.category[0]". If you'd want to map the second tag, you would use "_ti.taxonomies.post_tag[1]". Plugins and Themes might add additional taxonomies that will show up here if there are values available for the current post / page.
customerIdIn case the user is logged in, here is the md5 hash of the email address.
userRolesArray of user roles names.
customFieldsThis key is blacklisted by default. Here you can find data from your plugins and themes, and some of them might contain personnel data. That's why this key should only be whitelisted if you really need certain data from your plugins / themes in your datalayer.

Woocommerce product tracking

productNameHuman-readable title of the product.
productCostCost of the product.
productIdWoocommerce ID of the product.
productSKUProduct SKU.
currencyCurrency code (ISO 4217).
productQuantityAmount of products - only during order.
shoppingCartStatus"view" on single product page, and right before adding a product to basket from product lists. "add" when adding to basket, and "conf" after order.
productSoldOut'1' in case product is sold out.
productCategoryHighest level of product categories.
productSubCategory2nd level of product categories.
productCategoriesArray with all product category levels - in case you have more than two levels, you can use this. For example, if you want to map a level 3 category, you can do this with "_ti['productCategories'][2]". The Index is always one value lower than the level of the category.
Only for product variations: object with product variation data.
productsArray with all products from product lists. Each object hast the keys like a normal product (productName, productCost etc.).
pageRequestTypePopulated with value 'virtual' when adding a product to basket via AJAX (product lists, related products...). The first one is a product view, the second one the add-to-basket. This way you never have products added to basket without being viewed. Use this parameter to filter out views that have no 'real' view and just exist for the sake of data consistency.

Woocommerce order tracking

orderIdWoocommerce Order ID.
totalOrderValueOrder value, incl. tax and shipping.
subtotalOrderValueOrder value without tax and shipping.
taxValueTax of order.
couponValueValue of a coupon, if available.
shippingMethodName of the shipping provider.
shippingCostShipping cost for the order.
paymentMethodName of the payment provider.
  • No labels