Custom Endpoints Overview
The term "endpoint" at it's highest level, is a URL generated by an external server which can be used to facilitate data transfer, updates, or execute similar actions from web browsers and other applications referred to as "clients". In Pingtree's case, the "custom endpoint" casts a wide net when it comes to use-case, functionality and capabilities.
Below are a few common examples for how custom endpoints are used in Pingtree.
Lead Buyers: Sending lead data to buyers will generally be facilitated through a custom endpoint (Advertiser would be the alternative which would provide the buyer with their own advertiser portal)
CRMs: Sending lead data to your own CRM or the CRM of a third party is a common use-case.
Databases/Data Lakes: Another potential use-case would be any sort of data warehouse or visualization tool where lead data may be stored.
Dialers: Similar to CRMs, dialers can also be a common practice for Pingtree users to facilitate lead data transfers.
Custom Endpoints are at the heart of the lead distribution segment of your campaign, so needless to say it's an important.
Now that we've touched on common examples of how custom endpoints can be used in practice, below you find some of the different features and capabilities custom endpoints have and what will be covered in the following articles.
Lead Routing/Click Routing
Field Mapping
Transformer Tool
API Request Formats & Languages
Posting Formats
Endpoint CAPs, Filters & Plugins
Dynamic Response Mapping
Testing Endpoint Feature
Minimum Pricing
Click Listings
Click Listing Build
Click Listing Filters & Routing
Cloning Endpoints
Parent Endpoints
Price Settings