Client-Side Tracking (JavaScript Tag)

Our JavaScript (JS) tag enables users to monitor sessions and clicks by placing a first-party cookie named ‘_wctrck’. This session cookie helps determine which interactions belong to the same session, which is essential for our integration features. It expires 4 hours after the visitor’s last interaction with the website. By default, no personal data is tracked. Google Client IDs are recorded if available. IP addresses are anonymized by default, ensuring they cannot be traced back to an individual unless full IP tracking is enabled by the user. IP tracking can also be entirely disabled in the website settings.

Server-Side Tracking (Clickout API)

Through our Clickout API, users can provide click data and metadata on the server side. Users have full control over the data they provide.

Server-Side Tracking (WordPress Plugin)

For users cloaking their outgoing URLs on WordPress websites using the wp_redirect function (as employed by plugins like Pretty Links, ThirstyAffiliates, Affiliate Links Lite, etc.), our WordPress plugin automatically utilizes our Clickout API to track outgoing clicks. By default, no personal data is collected at the click level. Google Client IDs are recorded if available. IP addresses are anonymized by default, ensuring they cannot be traced back to an individual unless full IP tracking is enabled by the user. IP tracking can also be entirely disabled in the website settings.

WordPress Plugin Referrer Cookies

When Referrer Cookies are enabled within the plugin settings, our WordPress plugin places two additional first-party cookies named ‘_wct_http_referrer_1’ and ‘_wct_http_referrer_2’. These cookies are used to retrieve the correct clickout_url and redirect_url. The placement of these cookies can be turned off within the plugin settings. Additionally, the JS tag placements can be turned off in the plugin settings.

WordPress Plugin & Consent Management Systems

Properly configured Consent Management Systems (CMS) should effectively manage the cookie placements of our JS tag. If users observe that their CMS does not handle cookie placements correctly, we recommend disabling the JS Tag injection option within our WordPress plugin settings and manually adjusting and placing our JS Tag. This approach provides more control and simplifies cookie management for the CMS.
Please note that if our JS tag is not loaded, it will not be able to track any session and click data, meaning conversions from these visitors cannot be attributed and integrated unless the clicks are tracked on the server side (via Clickout API or WordPress plugin). If you choose not to load our JS tag for users who did not provide consent but still wish to track anonymous click data, you can utilize our Clickout API or WordPress plugin for cloaked URLs. You need to ensure that the setup complies with Data Protection Regulations.

Responsibility

We are not in a position to provide legal or technical advice on data and consent management. As the data controller, the publisher (our customer) carries full responsibility and must define its actions toward data regulation compliance independently or by seeking legal advice from qualified professionals.
For questions on properly setting up consent management for our JS Tag, please reach out to the support team of your Consent Management Platform.