How can I track into multiple accounts at the same time?
With Webtrekk you can track into several accounts at the same time. For example, you can track into an overall account and additionally into a country-specific account.
You have three options for this: by transferring several trackIds, by data profiles or up to version 4 of the pixel with a second pixel instance (not recommended).
Multiple trackIds in global configuration
Concerning the EverId there is one thing to keep in mind with this configuration for 1st party cookies: when requests are made to multiple accounts, the EverId is always taken from the account that was first.
In the 1st party EverId cookie (wt3_eid) no EverIds are entered for the other trackIds, which means: if they would be first on another page, another visitor would be measured in Webtrekk.
But we can easily transfer the EverId, which was assigned for the first trackId, to the cookie entries for the other trackIds.
The pixel method .setEverId() is available for this purpose.
Example: suppose we track into several trackIds and the second trackId is 463505768259296. We want to make sure that a user has the same EverId if he triggers track requests on pages only with this trackId.
To do this we need to execute the following method on the page with multiple trackIds:
In the wt3_eid cookie for the trackId 463505768259296, the EverId that is currently being used is written into it.
You can try this yourself in the following JSFiddle:
Mirroring track requests with data profiles
You can also let Webtrekk transfer tracking data without passing an additional trackId on your page with the pixel implementation. You can even limit yourself to individual parameters and filter them.
Technically, after activation, the incoming request from the source account is mirrored and the target account is "faked". After activation, only new data is received, historical data is not updated.
It should also be noted that only with 1st party cookies the EverIds remain identical, as the EverId is transmitted in the track URL (and the eid parameter is transmitted!).
With 3rd party cookies, the destination account generates a new EverId for each user that does not match the EverId of the source account.
You can activate the EverId in Webtrekk Q3. Go to "System configuration" in the configuration and select the tab "Data collection". Below you will find the setting options:
The possibility to track through several pixel instances into different accounts is only mentioned here for the sake of completeness and is not recommended from our side. Version 5 of the pixel does not support this method.
In the 3 and 4 pixel versions, you create a Webtrekk instance using the function constructor webtrekkV3:
wt = new webtrekkV3(pageConfig);
You can simply create another instance:
wt2 = new webtrekkV3(pageConfig);
If you now execute the sendinfo() methods from wt and wt2, then both requests get different EverIds. However, these can also be transferred via .setEverId() as described above.
You can see this in action on this page: http://184.108.40.206/teaser/instances.html