Overview
Close CRM is built specifically for inside sales teams, emphasizing speed and efficiency in outbound prospecting. Unlike broader CRM platforms, Close integrates calling, email sequences, and SMS directly into the CRM interface, reducing context switching for sales representatives. When deployed on a website, Close's primary client-side function is capturing inbound leads through embedded forms.
What This Script Does
Close's client-side scripts embed lead capture forms on websites to funnel visitor information into the CRM's sales pipeline. Scripts are loaded from close.com or related CDN domains.
Lead Capture Forms
The embedded forms collect contact information — typically name, email, phone number, and company — and create new lead records in Close's CRM automatically. Form submission events are tracked and timestamped.
Source Attribution
The script sets cookies to track how leads arrived at the form:
_close_src— stores the referring URL and UTM parameters at the time of first visit_close_vid— persistent visitor identifier for matching form submissions to previous anonymous visits
Behavioral Signals
The script may record which pages the visitor viewed before submitting the form, providing sales reps with context about the prospect's interests. This pre-submission browsing history is attached to the lead record in the CRM.
Data is transmitted to Close's API endpoints. The script does not inject visual elements beyond the forms themselves and does not perform retargeting pixel functions.
Consent & Compliance
Close CRM is classified as marketing. While the forms themselves serve a lead generation purpose, the accompanying visitor tracking, source attribution cookies, and pre-submission behavioral monitoring go beyond functional necessity. The persistent visitor identifier enables cross-session profiling of prospects.
Under GDPR and the ePrivacy Directive, the tracking cookies require prior consent. The lead capture form itself could potentially operate without cookies, but Close's implementation bundles behavioral tracking with form functionality.
Under CCPA/CPRA, the visitor behavior data flowing into the CRM constitutes personal information collection that requires disclosure. If lead data is shared with third-party services or used for cross-context outreach, it may constitute "sharing" under CPRA.
Should You Block This Without Consent?
Yes. Close CRM scripts perform visitor tracking and behavioral profiling for sales and marketing purposes. They should be blocked until the user consents to marketing cookies. If you need a simple contact form without tracking, consider a standalone form implementation that does not set attribution cookies.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
close.comMarketingFrequently Asked Questions
Does Close CRM require visitor consent under GDPR?
Yes. Close CRM scripts set _close_vid (a persistent cross-session visitor identifier) and _close_src (UTM attribution cookie), and record pre-submission browsing behavior that feeds into the CRM pipeline. These marketing-purpose tracking elements require prior consent under GDPR and the ePrivacy Directive.
What does Close CRM track?
Close CRM sets _close_src (referring URL and UTM parameters at first visit) and _close_vid (persistent visitor identifier for cross-session matching). The script also records which pages a visitor viewed before submitting a form, attaching that browsing history to the lead record in the CRM.
How does ConsentStack detect Close CRM?
ConsentStack classifies Close CRM as marketing and blocks its scripts until marketing consent is granted. This prevents the _close_vid visitor identifier from being set and stops pre-submission browsing history from being captured and transmitted to the CRM pipeline before the visitor has opted in.
Related Vendors
Manage consent for Close CRM
ConsentStack automatically detects and manages Close CRM trackers so your site stays compliant with global privacy regulations.
