Introduction
Delacon’s integration with Zapier gives you access to over 750 app integrations including Salesforce, Microsoft Dynamics, Mail Chimp, WordPress, Gmail, Facebook and more.
By using our integration, you can create Zaps for as many apps as you require – allowing our call data to be used by multiple platforms.
Please note that Delacon does not control what data the other Apps can receive. We simply push our call data into those apps using the Zapier integration.
Currently Delacon’s Zapier integration is in Beta Mode. In order to connect to Delacon you will need to be invited by Delacon. Please contact Delacon support to get the most recent invite link.
Setup Guide
1. Linking Delacon and Zapier
- Contact Delacon Support for the Zapier invite link.
- Click on the link or paste the URL into your web browser. Log in to your Zapier account if prompted.
- Click on ‘Accept Invite & Build a Zap’ button.
On the next screen, click on the ‘Create this Zap’ button.
2. Creating a Zap
In order to use Delacon’s call tracking solution with Zapier, you will need to create a ‘Zap’ between Delacon and the app you are integrating with.
Zaps are Workflows that connect apps so they can work together. They start with a trigger (such as a phone call) or an event that kicks off your workflow.
To create a Zap:
Step 1 - Click on the ‘Create Zap’ button:
Step 2 - Find the Delacon App by searching for ‘Delacon’ in the search bar.
Step 3 - Select the Delacon trigger ‘New Calls’ and click ‘Continue’:
Step 4 - Select your Delacon Account by clicking on ‘Connect a New Account’:
Please note if you have previously linked a Delacon account, you can select an existing account from the drop-down menu and skip to step 7.
Step 5 - A ‘Connect Account’ pop up box will open. Enter your Delacon account details and press ‘Yes, Continue'.
Please note, this will need to be the login details of the main account holder (MID level login). The integration will not work when authorised with any other login type (agency login, user login).
Step 6 - Once your account is connected, click ‘Continue’:
Step 7 - Click into the Service ID field and select the Delacon services that you want to connect.
Note, it may take a minute to load all services in the drop down menu as this information is collected from Delacon in real-time. Continue the process until you have added all relevant Delacon services. Then, click ‘Continue’.
Step 8 - Click on "Test Trigger".
Please note that due to the method we use to push data, testing on the Delacon trigger doesn't work at the moment. Skipping the test is required to proceed with building the Zap at this point in time. It won't impact the functionality of the Zap.
Please continue by clicking on ‘Skip Test’.
Step 9 - Once the test is skipped, click ‘Continue’ to complete the first part of the integration that connects Delacon to Zapier. Continue with Step 3 to set up an action.
3. Setting up an Action
You will now need to setup the action/s you want your Zap to perform. Often this will simply be the App you are pushing Delacon data to. The target app might provide more guidance on how to connect a zap to their platform. At the bottom of the article under "Related Articles", you can find step by step guides to integrate further with Zoho, Hubspot, Pardot and Facebook.
Step 1 - Search for the App
Type the App name in the search bar and click on it to continue:
Step 2 - Set Up App Action
Select the App Action. This is specific for each App you are setting up. For example if connecting the Delacon Zap to a CRM, the Action might be ‘Create a lead’ or ‘Create a Contact’.
Once you have selected your action, you will need to connect to your App Account. Once connected, select ‘Save + Continue’.
Step 3 - Setting up a Template
Once you have set up your action and connected your account, you will need to set up a template. Again this is specific to each App that you connect to.
Once completed, click on ‘Continue’.
4. Turning Zap on
In order for your Zap to work and the integration to be completed, you need to make sure you turn your Zap on. Simply click the ‘on’ button to turn it on.
Your Zap is now turned on and you are ready to start receiving call data. It is important to make sure you test the data coming through is accurate and correct.
5. Example of data fields
The below information is available in the Zapier Delacon trigger:
Delacon data | Field key | Explanation |
Call Recording URL | callRecording | The link to the call recording file |
Call ID | call_id | This is the unique ID of the call in the Delacon system |
IVR Description | dtmf__description | The corresponding name of the selected IVR option |
Date of Call | info__call_date | Date of Call |
Call Date Since Linux Epoch (ms) | info__call_date_epoch | |
Call Length (ms) | info__call_length | Length of the call |
Status of Call (answered/unanswered) | info__call_status |
This is the eventual status of the call. This indicates if the call was answered or busy tone was received a = answered call b = unanswered call with a voicemail c = busy call with a voicemail d = unanswered call without a voicemail e = busy call without a voicemail |
Caller Phone Number | info__caller | The caller's phone number |
Number dialed by caller | info__dialed_number | The tracking number dialed |
Termination Point | info__termination_point | This is the termination number to which the call is terminated to by Delacon system |
Time of Call (currently unavailable) | info__time_of_call | |
Was a voicemail left | info__voicemail_left | The status on any left voicemails (yes/no) |
City | location__city | The location of the caller |
Exchange | location__exchange | The location of the caller |
State | location__state | The location of the caller |
Service Category | service__service_category | The service details as per Delacon portal |
Service Id | service__service_id | The service details as per Delacon portal |
Service Name | service__service_name | The service details as per Delacon portal |
Survey Outcome | survey__outcome | This is the outcome of the call. This determines what type of call it was. For ex (sales / enquiry / followup / complaint ). This is only available if customer feedback feature is enabled for the campaign being tracked |
Survey Value | survey__value | This is the sale value generated from the call if the call was treated as a sale. This is only available if customer feedback feature is enabled for the campaign being tracked. |
Call Converted Status | webInfo__converted | This indicates if the call conversion was successfully lodged in the target system |
Device | webInfo__device | This is the device used by the user where the call tracking number was shown |
Extra Tracking Info | webInfo__extra_tracking | |
Google Client Id | webInfo__googleClientId | |
IP Address | webInfo__ip | This is the internet location of the user’s web browser where the web page was visited from |
ISP | webInfo__isp | This is the ISP provider of the internet connection that was used for visiting the web page |
Keywords (if manual tagging in use) | webInfo__keywords | This is the keywords which were searched for in the search engine which resulted in the call being made |
Landing Page | webInfo__landing_page | This is the full and complete version of the web page from where the tracking number was shown and the call was made |
Page Called From | webInfo__page_called_from | |
Referral | webInfo__referral |
This is the referrer web page from where the user came to the landing page on which the tracking number was shown |
Search Engine | webInfo__search_engine | This is the search engine which was used for searching the keyword |
Search Type | webInfo__search_type |
For more information on each of the fields and their description, please review the Delacon Glossary.
Below is an example of sample testing data:
Sample:
{
"info": {
"termination_point": "02912345679",
"call_date": "13/12/2017",
"call_length": 0,
"call_status": "answered",
"dialed_number": "1300000001",
"caller": "02912345678",
"time_of_call": null,
"call_date_epoch": 1513163488000,
"voicemail_left": false
},
"callRecording": "https://pla.delaconcorp.com/site/webui/jsp/downloadRecording_rt.jsp?file_name=filename.mp3",
"webInfo": {
"search_engine": "Google",
"googleClientId": "1111111.1111111",
"landing_page": "https://www.sample.com.au/?param=value",
"ip": "111.111.111.111",
"isp": "Internet Service Provider",
"extra_tracking": null,
"search_type": "paid",
"device": "android sm-g920i",
"converted": "Y",
"page_called_from": "https://www.samplepage.com.au/calledfrom",
"keywords": "+sample",
"referral": "https://www.sample.com.au/?param=value"
},
"service": {
"service_id": 1234,
"service_category": "Test Category",
"service_name": "Test Service"
},
"dtmf": {
"keys": null,
"description": null
},
"call_id": 0,
"survey": {
"outcome": null,
"value": 0
},
"location": {
"city": "SYDNEY",
"state": "NSW",
"exchange": "SYDNEY"
}
}
Troubleshooting
Issue: Authentication error when entering Delacon login details in Zapier (step 2.5)
Solution: Use the correct login details. Only the Master login to the Delacon account will be able to authenticate the access with Zapier. Using any other login will not work.
Related Articles:
- Zapier-Zoho integration
- Zapier-Hubspot integration
- Facebook Offline conversion via Zapier
- Pardot integration
Comments
0 comments
Please sign in to leave a comment.