SaaS clients: Posting leads to PX

  • Updated on

This article is intended for owners of Private Exchange platforms.

The lead request must include all mandatory attributes according to the vertical specification, otherwise, it will be rejected by PX. Сheck if the field is mandatory in XML examples of each vertical specification (e.g., in General vertical).

If API publishers wish to post leads to your PX in HTTP format, API partner token must be used instead of login and password. For this purpose, partner token must be generated in publisher settings in advance.

Despite the fact that non-mandatory fields can be omitted, it is still recommended to include them in the lead request. The more data can be retrieved from a lead, the more valuable it becomes and the higher its quality score.

Vertical geography

PX supports any lead generation vertical in any geography.  The USA is a default country, but with the addition of ""ecountry=XX" (where XX is two-digit country code), you can configure a vertical to be specific to any other country.  Verticals are standardized in PX so that buyers and publishers are able to work with many PX clients easily.

Specifications

Below are the verticals that are enabled by default in PX along with sample specifications:

  • URLs provided in samples below are specific for the PX demo environment. To post directly into your PX, the proper sub-domain in the format "http://api.YOURPXNAME.px.com..." must be used.
  • Ensure that default publisher information (affiliate ID, offer ID, etc.) is properly updated that PX would accept the lead and fire the correct conversion post-back:

If there is no specification for the vertical you need, reach out to PX Support.  

Related articles

0 comments

Please sign in to leave a comment.

Related articles