The Export to Cloud PBX tracking type allows you to add the lead details to the selected dialing list in the Cloud PBX component when the selected trigger event takes place.
The Export to Cloud PBX tracking type allows you to export a lead along with all its data to the Dialing list requests on Cloud PBX, depending on the processing of certain events in your system so that the operator has the opportunity to contact these leads.
Read more about the Event Tracking feature and its configuration in the “Event Tracking (LMS / Call Logic)” Knowledge Base article.
This rule can be configured on Product, Campaign, and Publisher levels.
Read more about Tracking Rule setting up on the Product level in this Knowledge Base article.
Read more about Tracking Rule setting up on the Campaign level in this Knowledge Base article.
Read more about Tracking Rule setting up on the Publisher level in this Knowledge Base article.
To create this tracking rule, fill in the following fields in the “Add Rule” pop-up window:
- Trigger: Select the event that triggers the action:
- [LMS] Lead Sold: The lead is sold through the Campaign.
- [LMS] Post Reject: The post was rejected (for Ping-Post products only).
- [LMS] Campaign Rejected: The Campaign has rejected the lead.
- [LMS] Campaign Sold: The lead was sold to the Сampaign.
- [LMS] Lead Offer Received: The lead status changed to "Offer Received" after a successful ping (for Ping Post Products only).
- [Call Logic] Lead Sold: The lead was sold to the Publisher.
- [Call Logic] Campaign Accepted: The Campaign has accepted the lead.
- [Call Logic] Campaign Rejected: The Campaign has rejected the lead.
- [Call Logic] Campaign Sold: The lead was sold to the Campaign.
- [Call Logic] Buyer Response: The Buyer has answered the call.
- Action: Select the “Export to Cloud PBX” option.
Once you select the preferable event, click the “Next” button to proceed with the setup.
The “Add Rule” window allows you to set up additional filters for the selected event. The list of available filters may vary based on the user role, platform, and configuration level. The filter fields are optional. If no filters are set up, the action will be triggered for all the leads that fit the event trigger.
Depending on the user role, platform, and configuration level, the following filters for trigger settings are available:
- Method: Select the Method (POST/FORM).
- Publisher: Select the Publisher.
- Channel: Select the Channel.
- Source: Select the Source.
- Buyer: Select the Buyer.
- Campaign: Select the Campaign.
- Pingtree: Select the Pingtree.
- Price Restrictions: Select the Price restrictions (Price is greater than 0, Price is greater than a certain value, Price is greater than or equal to a certain value, Price is lower than a certain value, Price is lower than or equal to a certain value, Price range inclusive). Note: The “Price range inclusive” value is available only for the “Lead Sold” and “Campaign Sold” triggers.
- Price Restriction Value: Enter the price value.
- Min Price: Enter the minimum price value to trigger the rule by the price range (available only for the “Price range inclusive” value in the “Price Restrictions” field).
- Max Price: Enter the maximum price value to trigger the rule by the price range (available only for the “Price range inclusive” value in the “Price Restrictions” field).
The “Action Settings/Export to Cloud PBX” block allows you to configure the action required for the rule setup:
- Cloud PBX Call Group: Select the Call Group (created in the Cloud PBX component).
- Cloud PBX Campaign: Select the Campaign (availability depends on the Call Group) (created in the Cloud PBX component).
- Cloud PBX Dialing List: Select the Dialing List to which the record will be added when the trigger event takes place (created in the Cloud PBX component).
Click the “Save Rule” button to confirm.
