Knowledge Base

Topics
What cookies are used when using our lead generation features?
Chatbot and Web Forms protection
Web Forms reCAPTCHA
Web Visitors

Chatbot, Web Forms and Web Visitors cookies

YS
Yssel Salas, April 2, 2024

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.


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
Note: You can find more information about __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.
Note: You can find more information about _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
Note: You can find more information about these cookies on Dealfront’s page here. According to Dealfront, customers who will have their existing Dealfront accounts connected have the ability to configure cookies on their settings page inside Dealfront.
Was this article helpful?

Yes

No

Related articles

Got any questions?

Contact us