Skip to content

7.7 effects of the tracking veto

7.7 Effects of the tracking veto

By using the slider Tracking veto, you can determine whether or not a recipient should be tracked. You can control the Tracking veto with the database column sys_tracking_veto, for example when transferring data via a registration form.

The value 0 allows tracking, the value 1 prevents the tracking.

Note: If a user decides to activate the tracking veto, this has an effect on two more points:

Statistics

For recipients, that refuse the tracking, all openings and link clicks are no longer being measured and saved personally. The same goes for conversion measurement. In summarizing statistics, mail openings, link clicks and turnovers are still being displayed numeric. However, in target-group specific and in detail statistics, such as recipient reactions, the recipients without a mail opening, link clicks or individualized revenues, are still being listed. Due to that the number of openings, clicks and revenue is lower, since the tracking refuser are not getting listed.

Target groups

If you are using target groups like "mailings opened", "link clicked", or "revenue generated", the people who use the tracking veto, will be missing in those target groups. Since the system doesn't assign any openings, clicks or turnovers to people who are using the tracking veto, they are listed in the target groups "mailing not opened" or "link not clicked", even if they did react in some kind of way. Due to that, we recommend you to address those recipients separately. You can do that by using the target group definition "sys_tracking_veto" = 1.

Please also note: Since people who refuse tracking can not be differentiated in statistics, there is only one number for anonymous openings and clicks remaining. Unfortunately the system is not able to say how many people participated in that number.

You also have the possibility to disable recipient tracking completely, so that all of your mailings will initially be tracked anonymously. If you are interested in this, please contact our support.