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:

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.

For all configuration levels, you will need to set up the event action and trigger and configure the rule. The following events are available in the system:

Event Tracking - 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.

    • [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.

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 that is 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.

Click the “Save rule” button to confirm.

Event Tracking - Form 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 that is 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 action that is 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.

Event Tracking - 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 “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 that is required for the rule setup. Enter the following fields based on the Call Criteria specs:

  • API Key

  • Appname

  • Scorecard

  • SESSION_ID

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.

  • Scope: The scope of the integration rule is applied to.

  • Event: The event that triggers the setup action.

  • Filter: The filter that is applied to the leads that fit the event description.

  • Integration ID: The integration type.

  • Params: The selected request method.

  • Created: The date and time the rule was created.

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.

  • Host: The name of the host website.

  • Scope: The scope the integration rule is applied to.

  • Event: The event that triggered the action.

  • Integration: The selected integration type.

  • 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.

Did this answer your question?