Using Baidu Jimuyu as the landing page of Baidu search ads can also automatically push the leads converted to the Jimuyu site into the CRM leads pool, and automatically associate Baidu advertising plans and keywords, so as to realize the placement of advertisements on the Baidu search ads landing on Jimuyu end-to-end delivery ROI analysis.
1. Introduction to Baidu Jimuyu E-Marketing Leads Push
Go to Baidu Marketing-Business Developer Center-Development Document-Leads Management-Leads Push Service to learn about the introduction to Baidu Jimuyu E-Marketing leads push.
2. Configure Leads Push Interface of Jimuyu E-Marketing
2.1 Configuration Description
Log in to the Baidu marketing background, access [Account Settings] - [Leads Receiving] - [API Export (Account)], and click [Push Interface Configuration] to enter the API configuration page.
2.2 Set Fields & Interface Type
2.2.1 Basic Information & Notification Interface Settings
- Rule Name: user can customize
- Notification URL: fill in the fixed address https://www.fxiaoke.com/marketing/adThridCallBack/recvData
- Signature parameter name, signature parameter value, and custom header are not required to fill in
2.2.2 Rule Effective Condition Settings
Customize the selection based on the current requirements that need to be synchronized, and configure the effective conditions of the enterprise according to the lead rules that need to be synchronized. For different component types (form\telephone\consulting), if field mapping has different requirements, it is recommended to create a separate push rule for each component type.
2.2.3 Mapping Relationship Settings
Configure the mapping relationship settings. Since the Jimuyu lead fields and the crm sales lead fields are not one-to-one correspondence (including name, type, etc.), it is necessary to match the Jimuyu lead fields with the crm sales lead fields of the enterprise by one-to-one mapping, so as to ensure that the information obtained by Jimuyu can be correctly stored in the corresponding fields of the CRM leads.
Standard Fields: Standard fields are the basic information provided by Baidu E-Marketing. Every enterprise is the same. After mapping the standard fields, when synchronizing sales leads, the configured information will be stored in the sales leads, among which the following clueId, keyword, and planName fields are required configuration items, and the mapping parameter names are fixed to correspond to English words. Other standard fields can be customized and added, and the mapping parameter names are filled with the apiName of the sales leads.
| original parameter name | map parameter name |
| ucid | ucid |
| clueId | clueId |
| keywords | keywords |
| planName | planName |
Form Field: The display name on the C-side of the form field is filled in the form display name on the landing page. If there are different names in multiple forms, they all need to be configured. For example, full name, name, and title are actually the name fields corresponding to the leads in CRM. If apiName is name, they all need to be listed, and the mapping parameter name is the apiName of the sales leads.
Custom Field Settings: Custom fields are used to map fixed fields enterprise account (ea), source (Source), advertising source (adSource), and some required fields of leads.
The specific configuration is shown in the table below:
| Field Name | Specific Value |
| ea | required. Funshare enterprise account, which can be obtained in the upper right corner of the management page |
| source | required. The specific option apiName of the "Source" field in the sales lead, here is the apiName of the headline advertisement option |
| adSource | required. Fill in the fixed value field "Baidu" |
| leads_pool_id | Not required. The specific option apiName of the "lead pool" in the sales lead, such as selecting a sales lead |
| funApiName | Not required. The function name of the mapping background configuration, the function can support multi-option related mapping |
| Other required fields apiName | Not required. Other required fields, such as: company is a required field in sales leads, but this field may not be found in Jimuyu leads. In order to ensure that leads are successfully saved to CRM sales leads, you can set a default value such as "unknown" |
2.3 Set Data Sending Format
Copy the data on the left and change it to the corresponding data format on the right:
The data format cannot use the default format and needs to be changed to a format with data. Among them, ucid, clueId, ea, planName, keyword, and adSource are not placed in data, and other parameters that need to be transferred are placed in data. For example:
{
"ucid": "88888888",
"clueId": "20082016933312218",
"ea": "Enterprise EA",
"planName": "Milk tea franchise business",
"keyword": "How much is the milk tea franchise",
"adSource": "baidu",
"data": {
"source": "cm8o5E3oz",
"field_v1gms__c": "example",
"name": "example",
"mobile": "13888888888"
}
}When testing data, you can modify the data value on the right, especially the mobile number, which needs to be updated to the mobile number format data. After the data sorting is complete, click Next to test the data, click Send Test Data, and check the pushed leads data in the CRM background sales leads after sending successfully. If the data is correct, click Edit to save.
There are many reasons for the unsuccessful push of leads, and the common ones are as follows:
- The format of the mobile number is wrong
- Required field is empty, and default value is not set
- Duplicate check rules are enabled for leads, duplicate leads cannot be inserted
- The clueId of the test data has been used, remember to modify the ID and test again
- Check whether the obsolete data is duplicated with the data
After the editing is completed, it is not enabled by default, please enable the push settings
Check the push history data structure. If there is a lead related to the advertisement, there will be a 20-minute delay, and other leads will be pushed in real time.
3. Matters for Special Situations
3.1 Complex Field Mapping
For the mapping of complex fields, such as: multi-select, or mapping with account logic, it needs to be implemented through custom functions in CRM.
Basic Principle: After E-Marketing receives the data of Jimuyu, it calls a custom function and re-maps the data to meet the conditions for leads storing in CRM.
Example 1: There is a field "Account Hobbies" in the account form, and there are four options, A, volleyball B, football C, badminton and D, table tennis. The leads submitted by each user have different values in the form. If user 1 selects A, B, C, then the value of the account hobbies field in the mapping rule is "A, B, C", but the "Account Hobbies" multi-option of the CRM sales leads does not accept "A, B, C", you need to do a map of option values;
At this time, it is necessary to map the "Account Hobbies" data to: [option1,2sy2dVjkh,T3KR33tVC] in the definition function.
3.2 Configure Custom Functions
After creating the custom function, you need to configure the apiname of the custom function in Jimuyu mapping, as follows:
Example of a custom function:
3.3 Required Fields for Sales Leads
If there is a required field in CRM sales leads, but there is no this field in Jimuyu leads, you can map a default value in the previous custom field mapping. For example: not filled. When writing a sales lead, "not filled" will be written into this required field; you can also map the required field in a custom function.