- 2 Minutes to read
- Print
- DarkLight
init
- 2 Minutes to read
- Print
- DarkLight
Overview
Value | Description | Data type | Default value | Required |
---|---|---|---|---|
trackId | Enter your Track ID here. It is under Mapp Q3 >Configuration > System Configuration > Data Collection. If the request should be sent to several accounts, you can add multiple Track IDs separated by a comma. |
| Yes | |
trackDomain | Enter the domain to which the data should be sent. If you are using a Mapp Intelligence track domain, you will find it in the setup information sent to you via email. |
| Yes | |
domain | Decide which domains are excluded from the referrer analysis. By default, the domain where the Smart Pixel is located is excluded. You can override this setting and add (sub)domains. (e.g., payment providers, etc.). Enter as a comma-separated list of domains and subdomains. You can use regular expressions and wildcards ( *).
|
|
| - |
cookie | Decide how Mapp Intelligence sets cookies to recognize a (returning) user. You can choose whether to set the cookie via the browser or the server. 1: First-Party Tracking Find more details below. |
|
| - |
Further information
cookie
When using first-party cookies, your website will set all cookies client-side. With third-party cookies, Mapp Intelligence sets the cookie server-side.
Acceptance of first-party cookies is generally higher than for third-party cookies. The disadvantage of first-party cookies is that they only are valid for one domain. Hence, when you use them, visits on websites distributed across multiple domains (e.g., www.website.com and www.website-special.com) cannot be tracked as a continuous visit. Tracking switches between sub-domains (e.g., www1.website.com and www2.website.com) or HTTP/HTTPS are supported.
We only recommend using server-side cookies if you use a custom Track Domain and the Track Domain is the same as your web domain. This allows first-party tracking and the highest data quality.
Implementation Example
This is how Mapp Intelligence can be implemented in a main.js
project file. You import the plugin. When executing Vue.use()
with it, you need to add your global configuration, webtrekkConfig
in this example:
import Vue from "vue";
import VueRouter from "vue-router";
import WebtrekkSmartpixelVue from "@webtrekk-smart-pixel/vue";
import App from "./App.vue";
import Home from "./views/Home.vue";
Vue.use(VueRouter);
const routerInstance = new VueRouter({
mode: "history",
base: process.env.BASE_URL,
routes: [
{
path: "/",
name: "home",
component: Home
},
{
path: "/about",
name: "about",
component: () => import("./views/About.vue")
}
]
});
const webtrekkConfig = {
trackId: "111111111111111",
trackDomain: "analytics01.wt-eu02.net",
domain: "sub.domain.tld",
cookie: "1"
};
Vue.use(WebtrekkSmartpixelVue, webtrekkConfig);
new Vue({
router: routerInstance,
render: h => h(App)
}).$mount("#app");
<template>
<div>Example</div>
</template>
<script>
export default {
name: "example",
mounted() {
this.$webtrekk.init({
trackId: "111111111111111",
trackDomain: "analytics01.wt-eu02.net",
domain: "sub.domain.tld",
cookie: "1"
});
}
};
</script>