Event Tracking Type: [PBX] Add to DNPL (API)

The Add to DNPL (API) tracking type allows you to add data to the existing PBX DNPL lists from the different components when the selected trigger event occurs.

Read more about the Event Tracking feature and its configuration in the “Event Tracking (LMS / Call Logic)” Knowledge Base article.

Read more about the DNPL feature in this Knowledge Base article.

The [PBX] Add to DNPL (API) tracking type can be configured on the Product, Publisher, Campaign, PBX operator, and E-delivery contact list levels.

Read more about the Event Tracking Configuration Levels in the Knowledge Base article.

To create this integration 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] Lead Rejected: The lead is not accepted by any Campaign.
[LMS] Campaign Sold: Lead has received "Buyer sold" status.
[LMS] Campaign Rejected: The Buyer rejected the lead. No matter the final status of the lead.
[LMS] Revenue Ping Back: Revenue Ping Back sent
[Preset] Send Lead To Email: Select to send the lead data to email.
[LMS] Lead Offer Received: The lead offer was received on a product ping.
[LMS] Amount Tracking: The amount tracking has been reached.
Note: Read More about the Amount Tracking feature in the Knowledge Base article.
[LMS] Publisher Earning Received: The trigger fires every time the Publisher gets earning (Direct Sold / Revenue Post-back).
[LMS] Disposition Updated: The Buyer Disposition has been updated.
[LMS] Disposition Updated: Buyer Disposition has been updated.
[LMS] Publisher Earning Adjusted: Lead Adjustment happened.
[LMS] Lead Return: Lead Return happened.
[LMS] Lead Partial Return: Lead Partial Return happens.
[LMS] Price Reject Sold: Lead Price Reject was sold.
[LMS] Price Reject Rejected: Lead Price Reject was rejected.
[LMS] Price Reject Registered: Lead price reject was registered.
[Call Logic] Lead Sold: The lead is sold through the Campaign.
[Call Logic] Lead Rejected: The lead was rejected by the Publisher.
[Call Logic] Campaign Rejected: The Campaign has rejected the lead.
[Call Logic] Campaign Accepted: The Campaign has accepted the lead.
[Call Logic] Campaign Sold: The lead was sold to the Campaign.
[Call Logic] Call Recorded: The call is recorded and ready to be downloaded.
[Call Logic] Buyer Response: The Buyer has answered the call.
[Call Logic] Publisher Earning Received: The trigger fires every time the Publisher gets earning (Direct Sold / Revenue Post-back).
[Call Logic] Amount Tracking: The amount tracking has been reached.Note: Read More about the Amount Tracking feature in the Knowledge Base article.
[Call Logic] Disposition updated: Buyer Disposition has been updated.
[Call Logic] Publisher Earning Adjusted: Lead Adjustment happened.
[Call Logic] Lead Return: Lead Return happened.
[Call Logic] Lead Partial Return: Lead Partial Return happened.

Action: Select the “[PBX] Add to DNPL (API)” option.

Once you select the preferable event, click the “Next” button 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 role and platform, the following filters for trigger settings are available:

Product: Select the Product.
Publisher: Select the Publisher.
Buyer: Select the Buyer.
Pingtree: Select the Pingtree.
Price Restrictions: Select the Price Restriction rule.
Please enter your email (for the [Preset] Send Lead To Email trigger only): Enter the email address.
Amount to fire ([LMS] Amount Tracking and [Call Logic] Amount Tracking only): Enter the amount to fire the trigger.
Method: Select the method (Post / Form).
Channel: Select the Publisher Channel.
Source: Select the Publisher Source.

The “Action Settings / [PBX] Add to DNPL (API)” block allows you to configure the action required for the rule setup:

Action: Select the action to perform (Add / Delete).
Expiration Type (Available for the “Add” action only): Set a specific date to delete the record from the DNPL list.
Select the “Relative” type of the date to set a period after which the record will be deleted from the DNPL as expired.
Expiration - Days: Enter the number of days before the expiration.
Expiration - Hours: Enter the number of hours before the expiration.
Expiration - Minutes: Enter the number of minutes before the expiration.
Expiration - Seconds: Enter the number of seconds before the expiration.
Select the “Absolute” type to set a particular day and time when the record will expire.
Expiration Date Format: Select the incoming date format. (If the format differs from the system default, it will be reformatted to YYYY-MM-DD HH:MM:SS).
Expiration Date: Enter the date of expiration.
Dnpl List Id: Enter the ID number of the DNPL list.
API Password: Enter the API Password taken from the DNPL List.
Value: Select the value to add/delete from the DNPL (you can set the value using the Available Placeholders by clicking on Show available placeholders).

Click the “Save Rule” button to proceed.