Q: Why are admins only able to see Leadfeeder visit details in our Salesforce? The rest of my team cannot view the visit details.

A: What might have happened is that when someone on your team installed the Leadfeeder package into your Salesforce organization that person clicked on the option to only allow it for admins.

STEP 1: Your Salesforce admin should uninstall the Leadfeeder package from your Salesforce. This will delete all of Leadfeeder’s custom entities and any customizations made on top of it.

STEP 2: Reinstall the Salesforce package from the Leadfeeder integration page; make sure Install for All Users or Install for Specific Profiles is chosen.

Select Reconnect:

Select Reinstall from the new window:

STEP 3: Read this Salesforce support article and act accordingly. We suggest the option to create custom permissions set and then assign that set to any number of users.

Q: I'm setting up my Salesforce integration but there isn't a field for email or other contact info, just an Opportunity name, First Name, and Last Name where does the email go?

A: Contact information isn't sent to the Salesforce CRM. We give the opportunity to put in default names in case they are required by your set up, however even if these fields are used contact information will not port over. 

Q: I see I can connect a Leadfeeder Contacts name and contact details as a new Lead in Salesforce, why is it not sending the contact information?

A: Leadfeeder allows you to populate these fields with Leadfeeder contact names for your convenience, however we are unable to share the contact information with your CRM. Any contact details will need to be input into your CRM manually.

Q: Why don't you send contact information to my CRM

A: Due to our commitment to privacy and our GDPR compliance we can't allow the export of this data. While we can show and process it, the data is not ours to share en masse. Our current agreements allow it to be shown within Leadfeeder alone.

Q: Why aren't the visits sending to Salesforce?

A: The issue may be that your integration is set up in such a way that you are trying to connect a lead as both and 'Account' and a 'Lead'. Visit data can only be sent to an 'Account' OR a 'Lead'.

Did this answer your question?