*This integration is supported for both SMB & Enterprise businesses.

Integrating BirdEye with DealerSocket CRM
User Manual

Introduction

Integration Requirements

Triggers Supported
Information from DealerSocket dashboard
Information from BirdEye dashboard

Integration Process

Business Integration Group

Create Integration Group (Curl Command)
Fetch information for all the triggers (Curl Command)
Update Trigger Information (Curl Command)
Find business integration group details (Curl Command)

Integration Mapping

Integration Mapping

Introduction

DealerSocket CRM is an automotive technology platform offering marketing, sales, service, customer experience, and data mining solutions to dealerships. Integrating DealerSocket CRM with BirdEye will automate the process of sending out review requests to customers on a daily basis.

Once DealerSocket CRM is integrated with BirdEye, BirdEye will pull customer information from DealerSocket CRM from the sales and service files. BirdEye collects the first name, last name, email address and phone number of your customers and automatically sends them review requests based on the preferences set within the BirdEye dashboard.

Integration Requirements:

Triggers supported

BirdEye allows you to fetch data from your CRM using some predefined triggers. You can choose any combination from the list of available triggers and inform the support team about your selection. Here are the supported triggers for DealerSocket CRM:

Trigger Name	Trigger Description
DealerSocket CRM Sales Trigger	This trigger is used to fetch the customer data based on the sales files received at BirdEye SFTP site.
DealerSocket CRM Service Trigger	This trigger is used to fetch the customer data based on the service files received at BirdEye SFTP site.

Information for the Integration with DealerSocket CRM

To set up the initial part of the integration with BirdEye, please reach out to the BirdEye technical support team @ 1-800-561-3357 Ext. 3 or email them at - support@birdeye.com with this form duly filled. Once the integration request is received, BirdEye will reach out to DealerSocket on your behalf to start the integration process.
For BirdEye to successfully complete the integration setup, you will have to notify BirdEye support after you have signed the agreements received from DealerSocket.

To initiate the integration, send an email to DCPInstallRequest@dealersocket.com , CC: support@birdeye.com / DealerSocket@birdeye.com with the details documented in the image aside. The interfaces in the case of DealerSocket CRM integrations will always be - SalesEventVehicles & ServiceEventVehiclesRO. After the integration has been initiated, DealerSocket CRM will send agreements to the business.

Once the business approves and signs the agreement, you will receive an email from DealerSocket CRM with the Site IDs for each dealership.

NOTE: You need to reach out to david.tulkin@birdeye.com in case you don’t receive the email within 7 days.

Details required from the client

Trigger details
DealerSocket CRM site ID

Details required from the BirdEye dashboard

Business ID
API Key

Information from BirdEye Dashboard

For single location SMB account - Business ID
For multi-location account - Enterprise ID and Business IDs of all locations
Enterprise ID

Business IDs of all locations

Integration process

Before you can integrate DealerSocket CRM with BirdEye, you will need to set up the following configurations:

1. Business Integration Group

A business integration group is a configuration that supports the business hierarchy of individual businesses on the BirdEye platform. The properties that are common for all business integrations are entered at the group level. Setting up a business integration group allows you to associate multiple business locations with the Enterprise account. Below is the list of curl commands that you will need to run to set this up.

a) Create Integration Group (Curl Command)

Copy this Curl Command

curl -X PUT https://common-services.birdeye.com/integration/add/businessintegrationgroup -H 'cache-control: no-cache' -H 'content-type: application/json' -d '{ "parentBusinessNumber" :151980725935863, "integrationSourceId":14,"integrationTriggers" : [39,40], "integrationGroupProperties" :[ { "propertyKey" :"api_key", "propertyValue" :"ZsmeBE0rUZjWPx0492wtfJZYQz89Xvo5", "isSecure" : true }] }'

151980725935863 - Business ID: This is Enterprise Id for multi-location account and Business Id for a single location SMB account
39,40 - Integration Trigger ID: Can be one or more triggers. Ask the client what trigger they would like to integrate with then run the curl command to fetch all possible triggers for DealerSocket CRM. Identify the trigger ID (s) and insert (use commas) in case of multiple trigger Ids.
ZsmeBE0rUZjWPx0492wtfJZYQz89Xvo5 - API Key: Copy this from client’s BirdEye account (Developer’s tab)

b) Fetch information for all the triggers available for DealerSocket CRM (Curl Command)

Copy this Curl Command

curl -X GET https://common-services.birdeye.com/integration/trigger/integrationtriggers/sourceid/14 -H 'cache-control: no-cache' -H 'content-type: application/json'

Sample response: A sample response like this would appear after you run the curl command. The response will have the trigger name, description and the ID. This trigger Id will be utilized while creating the integration group. An integration can have one or more triggers. To use more than one trigger, enter comma separated values while creating the integration group.

[
{
"id": 39,
"integrationSourceId": 14,
"triggerService": "dealerSocketSalesTriggerService",
"displayName": "DealerSocket Sales Trigger",
"description": "This trigger is used to fetch customer data based on sales files received at BirdEye SFTP site",
"active": true,
"integrationSourceName": "DealerSocket",
"integrationTriggerType":[{"id":1,"name":"JOB"}]
},
{
"id": 40,
"integrationSourceId": 14,
"triggerService": "dealerSocketServiceTriggerService",
"displayName": "DealerSocket Service Trigger",
"description": "This trigger is used to fetch customer data based on service files received at BirdEye SFTP site",
"active": true,
"integrationSourceName": "DealerSocket",
"integrationTriggerType":[{"id":1,"name":"JOB"}]
}
]

39 & 40 - Trigger ID

c) Update Triggers Information (Curl Command)

Copy this Curl Command

curl -X POST 'https://common-services.birdeye.com/integration/update/businessintegrationgroup?replaceTriggers=true' -H 'cache-control: no-cache' -H 'content-type: application/json' -d '{ "groupId": 14,"integrationGroupTriggers":[{"triggerId":39,"triggerTypeId":1}]}'

replaceTriggers=true - To replace existing trigger(s), enter the value for replaceTriggers as To add new trigger(s) to the existing list, the value for replaceTriggers should be false
14 - The Group ID that was returned in the previous step will be entered here.
39 - Enter the Trigger Id (s) which need to be added or updated to the integration.

d) Find business integration group details (Curl Command)

Copy this Curl Command

curl -X GET https://common-services.birdeye.com/integration/businessintegrationgroup/149451644517222 -H 'Cache-Control: no-cache'

149451644517222 - Business ID: Enter the Business ID here to get the integration group details for a business.

[
{
"groupId":3,
"integrationSourceType":{
"id":14,
"integrationSource":"DEALERSOCKET",
"sourceCategory":"Automotive"
},
"integrationTriggers":[
14
],
"oauthEnabled":true
}]

3 - Group ID: A group Id will be returned in the sample response with the details of the existing triggers for a business.

2. Integration Mapping:

Once the Integration Group is created, the next step is to create the Integration Mapping.

Copy this Curl Command

curl -X PUT https://common-services.birdeye.com/integration/add/businessintegrationmapping -H 'cache-control: no-cache' -H 'content-type: application/json' -d '{ "businessNumber": 151810587563907, "integrationGroupId" : 11, "active": true, "integrationProperties":[ { "propertyKey" :"dealer.socket.site.id", "propertyValue" :"2332" } ] }'

151810587563907 - Business Number: Enter the Business number here
11 - Group ID: Enter the Integration Group ID which was returned when the Integration group was created.
2332 - DealerSocket CRM Site ID: The DealerSocket CRM Site ID corresponding to different BirdEye locations are shared by Dealersocket in the email after the business signs the agreement.

Troubleshooting

The files are sent as zip with name starting as yyyymmdd_*.zip. Download the zip file and open it to find the feed files for different clients.

Note:

There could be multiple zip files for any day.
The feed files within a zip file start with the site id corresponding to each client.

Following is an example screenshot of feed files sent for 15th September 2020:

Restriction Reason

Restriction reason is used to identify the contacts which have been opted-out(restricted) from sending a review request. This reason can be fetched from Kibana for contacts that are checked-in already.

Possible restriction reasons for DealerSocket CRM are: