Event Tracking allows you to track the various events in the system (e.g., lead sold, lead rejected, etc.) and set the actions to be automatically triggered by them. The Event Tracking configuration is available on the different setup levels according to the scope and the user system role.
Configuration Levels:
Event Tracking Types
Reporting
Configuration Levels
Product
The Product Tracking configuration is available for the Global Admin, LMS Admin, Call Logic Admin, and Support system roles.
To access the feature, go to the System Management > Products section, select the product from the list, and click the “Settings” button in the “Actions” column. Select the “Tracking” tab on the Product Setup page.
Campaign
The Campaign Tracking configuration is available under the Global Admin, LMS Admin, Call Logic Admin, Buyer Agent, Buyer Editor, and Support system roles.
To access the feature, go to the Client Management > Setup > Campaigns section, select the campaign from the list, and click the “Configure” button in the “Actions” column. Select the “Tracking” tab on the Campaign Setup page.
Publisher
The Publisher Tracking configuration is available under the Global Admin, LMS Admin, Call Logic Admin, Publisher Agent, Compliance Publisher, and Support system roles.
To access the feature, go to the Publisher Management > Publishers section, select the publisher from the list, and click the “View” button in the “Actions” column. Select the “Tracking” tab on the Publisher Setup page.
Event Tracking Types
You will need to set up the event action and trigger and configure the rule for all configuration levels. The following events are available in the system:
Ping URL
The Ping URL allows you to send a GET or POST request to the third-party server when the selected trigger event takes place.
To create this integration rule, fill in the following fields in the “Add Rule” pop-up window:
Action: Select the “Ping URL” option.
Trigger: Select the event that triggers the action:
[LMS] Lead Sold: The lead is sold through the redirect campaign.
[LMS] Lead Rejected: The lead isn’t accepted by any redirect campaign.
[LMS] Campaign Rejected: The buyer has rejected the lead.
[LMS] Campaign Accepted: The buyer has accepted the lead.
[LMS] Publisher Earning Received: The Publisher has received earnings.
[LMS] Campaign Sold: The lead has received the “Buyer Sold” status.
[LMS] Revenue Ping Back: The revenue pingback has been sent.
[Call Logic] Lead Sold: The lead has received the “Publisher Sold” status.
[Call Logic] Lead Rejected: The lead has received the “Publisher Rejected” status.
[Call Logic] Campaign Rejected: The buyer has rejected the lead.[Call Logic] Campaign Accepted: The buyer has accepted the lead.
[Call Logic] Campaign Sold: The lead has received the “Buyer Sold” status.
[Call Logic] Publisher Earning Received: The Publisher has received earnings.
Once you select the preferable event, click the “Config Rule” to proceed with the setup.
The “Trigger Settings” block allows you to set up additional filters for the selected event. 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 Restriction Value: Enter the value.
The “Action Settings / Ping Url” block allows you to configure the action required for the rule setup:
Method: Select the request type (GET/POST);
URL: Enter the request URL as provided in the example using the required placeholders. To view, click the “Show available placeholders” button.
Ignore SSL Certificate: Select the checkbox to ignore the SSL certificate.
Click the “Save rule” button to confirm.
Pixel
The Pixel allows you to inject JS code into Phonexa’s forms when the selected trigger event takes place.
To create this integration rule, fill in the following fields in the “Add Rule” pop-up window:
Action: Select the “Pixel” option.
Trigger: Select the event that triggers the integration action.
[LMS] Lead Sold: The lead is sold through the redirect campaign.
[LMS] Lead Rejected: The lead isn’t accepted by any redirect campaign.
[Call Logic] Lead Sold: The lead has received the “Publisher Sold” status.
[Call Logic] Lead Rejected: The lead has received the “Publisher Rejected” status.
Once you select the preferable event, click the “Config Rule” to proceed with the setup.
The “Trigger Settings” block 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.
The “Action Settings” block allows you to configure the action required for the rule setup:
Tracking Code: Enter the code that will be posted back into the form as provided in the example using the required placeholders. To view, click the “Show available placeholders” button.
Click the “Save rule” button to confirm.
Google Ads Conversions from Clicks
The Google Ads Conversions from Clicks allows you to track LMS/Call Logic conversions from clicks in the Google Ads account. Additional configurations might be required depending on the use case.
To create this integration rule, fill in the following fields in the “Add Rule” pop-up window:
Action: Select the “Google Ads Conversions from Clicks” option.
Trigger: Select the event that triggers the integration action.
[LMS] Lead Sold: The lead is sold through the redirect campaign.
[LMS] Lead Rejected: The lead isn’t accepted by any redirect campaign.
[Call Logic] Lead Sold: The lead has received the “Publisher Sold” status.
[Call Logic] Lead Rejected: The lead has received the “Publisher Rejected” status.
The “Trigger Settings” block 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. In case no filters are set up, the action will be triggered for all the leads that fit the event trigger.
The “Action Settings” block allows you to configure the action required for the rule setup:
Customer ID: Enter your Google Ads customer ID.
Label: Fill in the label.
Conversion Name: The name of the conversion with Google Ads.
Password: The Google Ads password.
Click the “Save Rule” button.
Call Criteria
The Call Criteria allows you to ping the Call Criteria service when the call recording is available for download.
To create this integration rule, fill in the following fields in the “Add Rule” pop-up window:
Action: Select the “Call Criteria” option.
Trigger: Select the event that triggers the integration action.
[Call Logic] Call Recorded: The call is recorded and ready to be downloaded.
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. In case no filters are set up, the action will be triggered for all the leads that fit the event trigger.
The “Action Settings / Call Criteria” block allows you to configure the action required for the rule setup. Enter the following fields based on the Call Criteria specs:
API Key: Enter the API Key.
Appname: Enter the appname.
Scorecard: Enter the scorecard.
SESSION_ID: Enter the session ID.
The “Data Map” block allows you to add additional filters such as Agent Information, Call information, and Other Data Items.
Enter the following fields as provided in the example using the required placeholders:
AGENT: Enter the Agent placeholders.
AGENT_GROUP: Enter the Agent Group placeholders.
AGENT_NAME: Enter the Agent Name placeholders.
CAMPAIGN: Enter the Campaign placeholders.
LIST_NAME: Enter the List Name placeholders.
Lead ID: Enter the Lead ID placeholders.
Lead Phone: Enter the Lead Phone placeholders.
Call Datetime: Enter the Call Datetime placeholders.
Call Timestamp: Enter the Call Timestamp placeholders.
Other Data Items: Enter Other Data Items placeholders.
To view, click the “Show available placeholders” button.
Click the “Save Rule” button to confirm.
Reporting
All Integration Rules
To view all of the integration rules in the system, go to the References > Reports > All Integration Rules section.
To narrow down the search results, use the following filters:
Tracking: Select the scope the rule is applied to.
Trigger: Select the event that triggers the action.
Action: Select the integration action.
Author: Select the user that set up the rule.
The report contains the following information:
ID: The ID number of the record.
Tracking: The scope of the integration rule is applied to.
Trigger: The event that triggers the action.
Trigger Settings: Settings of the scope of the integration rule are applied to.
Action: The integration applied for the rule.
Action Settings: Settings of the rule.
Status: The status of the rule.
Created At: The date and time the rule was created.
Author: The user that set up the rule.
Tracking Log
To monitor the tracking performance and access the tracking log, go to the System Management > Logs > Tracking Log section.
To narrow down the search results, use the following filters:
Date: Select the date range.
Host: Enter the name of the host.
Entity: Select the preferable entity (Lead / Call).
Tracking: Select the scope the integration rule is applied to.
Trigger: Select the event that triggers the action.
Action: Select the integration applied for the rule.
The report contains the following information:
Date: The date and time the record was created in the system.
Entity: The Lead ID.
Host: The name of the host website.
Tracking: The scope the integration rule is applied to.
Trigger: The event that triggered the action.
Action: The integration applied for the rule.
Response status: The response received from the host.
To view a detailed log and response to the event, click the “Log” button in the “Action” column.