Chatbot, Web Forms and Web Visitors cookies and other tracking technologies
When using Pipedrive lead generation features like Chatbot and Web Forms and our paid add-on Web Visitors, certain cookies are used to provide the best experience for you and your customers.
These cookies are essential and can’t be omitted.
Furthermore, in order to provide you with the engagement statistics on the dashboard and allow troubleshooting on our end, we track certain events for Chatbot and Web Forms via a tracking script.
What cookies are used when using our lead generation features?
Chatbot and Web Forms protection
Both Chatbot and embedded Web Forms load a single Cloudflare cookie __cf_bm. This helps to identify and mitigate automated traffic and protect our infrastructure.
This cookie is attached to Pipedrive’s domain.
Service creating the cookie | Chatbot and Web Forms |
Cookie name | __cf_bm |
Cookie type | Third-party |
Expiration | 1 hour |
Purpose | Set by Cloudflare – bot protection |
__cf_bm cookie in Cloudflare documentation here.Web Forms reCAPTCHA
When creating new Web Forms or editing the existing ones, you can choose whether the form is spam-protected or not.
When Spam Protection is enabled for Web Forms, we use Google reCAPTCHA, which adds a _GRECAPTCHA cookie to provide risk analysis.
Service creating the cookie | Web Forms |
Cookie name | _GRECAPTCHA |
Cookie type | Third-party |
Expiration | 179 days |
Purpose | Sent by Google reCAPTCHA when Web Forms spam protection is enabled. When spam protection is not enabled, the cookie won’t be loaded. |
_GRECAPTCHA cookie in Google’s FAQ here.Web Visitors
When adding a tracking script to your website to collect visitor information, Dealfront sets _lfa and _lfa_expiry cookie to track all website visits. In addition, if the Pipedrive/Dealfront customer has configured the consent manager it will create the _lfa_consent cookie to keep track of what the visitor has answered to the consent dialog.
The visitor might also see traces of the _lfa_test_cookie_stored as it’s used to check if cookies are enabled or not.
Service creating the cookie | Web Forms |
Cookie name | _lfa |
Cookie type | First-party |
Expiration | 1 year |
Purpose | Set by Dealfront script to track website visits |
Cookie name | _lfa_expiry |
Cookie type | First-party |
Purpose | Set by Dealfront script to track website visits. A local storage variable to store the duration for the Dealfront clientID stored in browser LocalStorage |
Chatbot and Web Forms event tracking
In order to provide you with the engagement statistics for Chatbot and Web Forms on the feature dashboard and to allow troubleshooting from our end, certain events and end users’ engagement with those features are tracked via a tracking script.
When doing so, the tracking script collects the following information: webformId, embedded (true/false), URL and type of interaction (viewed/interacted).
No information about the end user or their device is collected, except for User Agent which is, however, not used by us in any way, whether to identify end users or otherwise.
We also use the features’ engagement information for our own analytical purposes. Nonetheless, we do so only in aggregate form and not in a manner that would identify any end users.
The tracking script is always used with the Chatbot and Web Form features.
End users can block Java Script and tracking in most browsers. That said, the Chatbot and Web Form features can’t be used in such cases.
Was this article helpful?
Yes
No