Feature requests

Bringing back the comment fields like in the past: some customers were using it

Currently, only visits tied to identifiable companies are surfaced, which creates a gap when clicks come from personal accounts or unidentifiable IPs. Request: Add the ability to display the total number of anonymous UTM clicks (without exposing any PII like IP addresses). Even if those clicks cannot be matched to a company, seeing that activity would provide valuable insight into campaign performance. This would help bridge the discrepancy between what platforms like LinkedIn report (all clicks) and what Leadfeeder shows (only identifiable company visits).

Previously you could edit the name of a company directly in Leadfeeder

A client has expressed a wish for a more secure way to access LeadFeeder. Currently, Leadfeeder's API is accessible only via a standard login/password, which they find somewhat outdated and limited from a security perspective. They highlighted that the general platform already offers more secure authentication options — for example, logging in via Google — and they would like to see something similar for Leadfeeder's API. Client’s reasoning: Stronger security compared to simple login/password Consistency with authentication options already available on the platform Alignment with best practices for enterprise-grade security Request: Please assess the feasibility of enabling more secure authentication methods for Leadfeeder's API, such as SSO or OAuth login options (e.g., Google login).

I often get leads that are out of our geographic range, are ISP / IT solution providers, or are vendors / parts suppliers. I'd love to be able to select all of these and hide them at one time. Currently I have to hide them one at a time. This would save a lot of time.

Previously it was possible for users to edit company information in LF, but this is no longer available with the new company profile

client EON would like to get ga session id from our leadfeeder api. He says that because we are collecting and showing ga_client_id we should have no problem to collect the ga session id as well and pass it through the api.