Hi, @Mirza. Opening up a case with HubSpot Support is likely your most direct path to resolution. Assuming there's nothing wrong with the configuration in setting up the connector, common reasons for not seeing new records in Salesforce after completing the integration:
1) Setting up the integration doesn't automatically sync records. You may need to resync a list, or make changes to contact property values, to see them in Salesforce.
2) If you set up an inclusion list, it may not yet have records meeting that list's criteria. If no inclusion list exists, HubSpot contacts with a lifecycle stage of Subscriber do not sync by default.
3) The integration user - the Salesforce user whose credentials are stored in HubSpot - does not have the ability to create leads in Salesforce.
4) The integration user is successfully creating leads, but assigned to users in Salesforce you're unable to see.
HubSpot will be able to more closely investigate these with you.
Brad Mampe, Salesforce Analyst, Fidelity I'm probably wrong. I may not be right about that.
Hi, @Mirza. Opening up a case with HubSpot Support is likely your most direct path to resolution. Assuming there's nothing wrong with the configuration in setting up the connector, common reasons for not seeing new records in Salesforce after completing the integration:
1) Setting up the integration doesn't automatically sync records. You may need to resync a list, or make changes to contact property values, to see them in Salesforce.
2) If you set up an inclusion list, it may not yet have records meeting that list's criteria. If no inclusion list exists, HubSpot contacts with a lifecycle stage of Subscriber do not sync by default.
3) The integration user - the Salesforce user whose credentials are stored in HubSpot - does not have the ability to create leads in Salesforce.
4) The integration user is successfully creating leads, but assigned to users in Salesforce you're unable to see.
HubSpot will be able to more closely investigate these with you.
Brad Mampe, Salesforce Analyst, Fidelity I'm probably wrong. I may not be right about that.