The following table shows the different tracking options with the resulting data quality.
Browser | Server | |||||
|---|---|---|---|---|---|---|
Standard | Custom Track domain (C-NAME) | Custom Track domain (A-RECORD) | Proxy | Server-to-Server | Hybrid Server-to-Server | |
Description | Tracking data is sent to the default track domain | Tracking data is forwarded from a custom domain via C-name entry to the default track domain. Further Information | Tracking data is forwarded from a custom domain via A-record entry to the default track domain. | The own server receives tracking data and forwards it directly from the server to the standard track domain. | Tracking data is generated by own server and sent to the default track domain. | The own server receives Event tracking data and forwards it directly from the server to the standard track domain. Remaining tracking data is generated by own server and sent to the default track domain. |
Track domain | Default track domain provided by Mapp | Custom Subdomain | Custom Subdomain | Custom Subdomain | Default track domain provided by Mapp | Event tracking: Custom Subdomain Remaining tracking: Standard (Webtrekk) |
Available Data quality resulted from tracking blockers. Without (with) activated obfuscation1. | 1 (1) | 2 (3) | 3 (4) | 3 (4) | 5 (-) | Event tracking: 3 (4) Remaining Tracking: 5 (-) |
Complexity of integration 1-low, 5-high | 1 | 2 | 2 | 3 | 4 | 5 |
Supportability and Debugging | easy | easy | easy | medium | impossible | limited (Event Tracking only) |
Tracking options | Events: Remaining Tracking: | |||||
1 By using tracking obfuscation, it becomes more difficult for tracking blockers to prevent data collection. This is possible by dynamically adjusting the request URL and the included tracking parameters.