Customerlabs CDP Documentation
Zoho CRM is a cloud-based CRM solution that helps businesses across different industry verticals to manage their interactions with existing and potential customers. Key features include one-click phone, sales lead tracking, sales management, event tracking and more.
The CustomerLabs 1PD Ops + Freshsales integration will enable marketers to bring their Accounts, Leads, Contacts, Deals and all related data from Freshsales into Customerlabs 1PD Ops.ย
Marketing teams can use incoming Freshsales data to enrich existing user profiles, create targeted segments & sync them with other marketing tools to personalize engagement using CustomerLabs 1PD Ops.ย
1. How to Connect Zoho CRM with CustomerLabs
You can transfer data from Zoho CRM to CustomerLabs using a webhook. By setting up a webhook in Zoho CRM, the data will automatically be sent to CustomerLabs.
Step 1: Sign in to your Zoho CRM account.
Step 2: Create a webhook in your CRM account.
2.1To create the webhook, please do the following steps:
2.2 Go to Setup > Automation > Actions > Webhooks.
2.3 On the Webhooks page, click Configure Webhook.
2.4 In the URL to notify, paste the URL from the CustomerLabs source section.
2.5 SignIn CustomerLabsโ Navigate to the source sectionโ Choose a custom source and name it as Zoho CRM and paste the URL in the Zoho webhook section
2.6 Refer to the Zoho documentation and add the module parameters’ custom parameters per your requirements.
2.7 Click Save.
What is a Workflow?
A Workflow helps you to turn the raw data you receive from the source into specific event data based on the workflow configuration which includes filtering and modifying the parameters. You can create multiple workflows inside a Source. A workflow is a one-time setup that constantly receives customer data & updates user profiles in CustomerLabs 1PD Ops in real-time.ย
Once a Source platform is authenticated, users can build workflows without writing a single line of code.
How to build a Workflow?
Step 3: Setup the workflow
3.1 Name your workflow
Name the workflow according to your preference here we have named it โZoho Leadโ
This helps you quickly select relevant workflows โ just for internal purposes.
Example: If you want to receive the data of users whose stage is changed to โLeadโ in your CRM through this workflow, you can name this workflow โlead_updatedโ or โlead_createdโ.
3.2 Workflow Delay
Workflow delay is recommended when you have multiple workflows in a source.
The data coming into the source will be sent across the workflows at the same time if the workflow delay is not given. This may result in concurrency issues.
3.3 Choose sample data
To receive event samples, trigger an event in that particular Source. For example, if youโre setting up a workflow to receive contact information as and when it gets updated in your CRM. Update a test contact in your CRM to receive event information in CustomerLabs 1PD Ops.
You will be able to update up to 5 samples at once. Fetching sample data in a few source platforms might take time. In that case, please wait for some time before you try again.
You can view the incoming sample data and select the sample that suits your use case.
You can view the incoming sample data and select the sample that suits your use case.
Step 4: Event Configuration
Event configuration is the workflow setup’s final and most important step.
4.1. Event name
Assign the event name by selecting from the drop-down as shown below choosing the dynamic event and naming the event based on the lead status.
4.1. User Identity Mapping
You can choose up to 3 different identifiers including external IDs to map user information. These external IDs will be stored by CustomerLabs 1PD Ops to create an enriched user profile.
User traits: All user/contact/individual-related information can be added under user traits and a screenshot example is given below
Source Logs
Source Logs show a list of events received by the source webhook before being sent to the workflows for event processing. There may be a delay in displaying the events items of up to 10 minutes, which is currently optimized.
You can see the logs by clicking on โLogsโ from a particular source as shown below.
Every single message received by CustomerLabs 1PD Ops will have a unique message id and weโll be logging them so you can see how it is being processed in various workflows before appearing in the event manager.
Source โData inโ log
The below image shows the log data of the message received from that particular source and data variables in JSON format.
Source โData outโ log
The below image shows the log data of the message processed and sent to respective workflows along with a new message id.
Workflow Logs
Individual workflows will also have their own logs, and you can use them to see how the event is transformed including user traits, event attributes, group(account) traits, external ids, group(account) identities, and other attributes.
Few tips on workflow status messages in โData outโ
Youโll see the following messages in the workflows and the reasons are listed below.
a) Mapping not found โ When a workflow is in draft mode, the message as โMapping not foundโ is thrown.
b) Filter condition failed โ When a workflow filter condition is failed, this message is thrown.
c) User ID missing or Account ID is missing โ We assume every event should have User identity or account identity fields. When the data is missing weโll throw an error and the event wonโt be processed further.
d) Data not found โ This message means the data is still being processed, sometimes when there are lot of requests the systems will take up to 10 minutes to process the data.
Destination
Send incoming data to third-party apps to boost marketing effectiveness. Learn more about the destination tools we support.
You want to explore? Need a hand โ happy to help, always!
.
