Our AFL UTM Tracker plugin uses cookies to store data about the visitor visits. Since our plugin is not a full analytics server, we use quite a number of cookies to store various data so that your WordPress server does not need to fill the database of every visitors. We only read the data from the cookies only when a conversion happens or when Active Attribution is enabled.
You may need to register the cookies in your cookie consent banner website.
Sample Template for your Website Privacy Policy
AFL UTM Tracker is a conversion tracking and marketing attribution tool to help us understand how our visitors arrive at our website and which marketing efforts leads to a conversion.
What information do we collect:
- The tool captures a visitor’s first touch and last touch URLs including UTM parameters, click identifiers and timestamp of the visits.
Where is the information stored:
- The information is stored in the visitor’s browser cookies for ___ days.
- The information may be transmitted and stored on our server database or third-party servers (e.g CRM, newsletters systems) when a conversion event occurs.
We use this information to:
- Attribute website conversion activity (such as form submissions or purchases) to specific marketing campaigns.
NOTE:
Get the cookie expiry length from the plugin's Cookie Attribution Window setting.
Since AFL UTM Tracker is a self-hosted solution, your visitor's tracking data is never being send to Appfromlab servers.
This template does not constitute legal advice, please seek legal advice from your lawyer.List of Cookies
If your Cookie Consent Banner service allows you register cookies using a wildcard name:
| Cookie Name | Cookie Purpose |
| afl_wc_utm_* | Tracks the visitor’s first landing page, first website referrer, first/last touch URLs with or without UTM parameters, click identifiers URLs and timestamp of the visits. |
Individual Cookies
Otherwise here’s the list of cookies which our plugin generates:
| Cookie Name | Cookie Purpose |
| afl_wc_utm_main | Stores the timestamp of the last updated server-side communication, timestamps of various tracking URL, cookie expiry and the cookie consent type. |
| afl_wc_utm_sess_landing | Stores the visitor’s first landing page URL. |
| afl_wc_utm_sess_referer | Stores the visitor’s first website referral URL. |
| afl_wc_utm_utm_1st_url | Stores the visitor’s first touch URL visit containing the UTM parameter. |
| afl_wc_utm_utm_url | Stores the visitor’s last touch URL visit containing the UTM parameter. |
| afl_wc_utm_gclid_url | Stores the visitor’s last touch URL visit containing the gclid parameter. |
| afl_wc_utm_fbclid_url | Stores the visitor’s last touch URL visit containing the fbclid parameter. |
| afl_wc_utm_msclkid_url | Stores the visitor’s last touch URL visit containing the msclkid parameter. |
If you are tracking other click identifiers, then you can include them:
| afl_wc_utm_<click_identifier_parameter>_url | Stores the visitor’s last touch URL visit containing the <click_identifier_parameter> parameter. |
NOTE: The afl_wc_utm_main cookie was introduced in version 2.5.0 and the content was updated in version 2.14.0.Deprecated Cookies in Version 2.15.0
The following cookies are no longer generated since version 2.15.0.
| Cookie Name | Cookie Purpose |
| afl_wc_utm_cookie_expiry | Stores the number of days that the cookies should expire after the visitor’s last visit. |
| afl_wc_utm_sess_visit | Stores the visitor’s first landing page visit timestamp. |
| afl_wc_utm_utm_1st_visit | Stores the visitor’s first touch timestamp visit containing the UTM parameter. |
| afl_wc_utm_utm_visit | Stores the visitor’s last touch timestamp visit containing the UTM parameter. |
| afl_wc_utm_gclid_visit | Stores the visitor’s last touch timestamp visit containing the gclid parameter. |
| afl_wc_utm_fbclid_visit | Stores the visitor’s last touch timestamp visit containing the fbclid parameter. |
| afl_wc_utm_msclkid_visit | Stores the visitor’s last touch timestamp visit containing the msclkid parameter. |
WordPress Multisite
For sites under the Multisite Network, cookies will have a prefix:
Site 1
afl_wc_utm_1_
Site 2
afl_wc_utm_2_
Site 3
afl_wc_utm_3_