System field shortcodes

To better help you routing your leads, Lead Prosper has created a few system fields that you can use in your payload sent to your buyers or in the webhooks.

Like the campaign fields, these shortcodes can be added to:

  • real-time and webhook payload builder, for both HTTP or Email delivery
  • direct post and ping/post URLs
  • direct post and ping/post headers

Available system fields

  • lp_ping_response: returns the full response body of a PING request that was sent to a buyer. Can only be used in PING/POST setups, and only in the POST payload or webhooks. Note: always sent JSON encoded
  • lp_ping_response:KEY: extracts a specific KEY from the response body of a PING request that was sent to a buyer. To read more about the KEY, please read this article regarding response parsing.  Can only be used in PING/POST setups, and only in the POST payload or webhooks.
  • lp_post_response: returns the full response body of a POST request that was sent to a buyer. Can only be used in webhooks. Note: always sent JSON encoded
  • lp_post_response:KEY: extracts a specific KEY from the response body of a POST request that was sent to a buyer. To read more about the KEY, please read this article regarding response parsing.  Can only be used in webhooks.
  • lp_date: returns the current UTC date. Example: 2020-01-15 16:34:56
  • lp_timestamp: returns the current UTC timestamp. Example: 1582315643
  • lp_campaign_id: the campaign id
  • lp_supplier_id: the supplier id
  • lp_buyer_id: the buyer id
  • lp_request_uuid: the internal UUID that Lead Prosper generates. This is the same that is returned back to your supplier in the response and also displayed in the logs
  • lp_status: the status of the buyer that processed a lead. Can only be used in webhooks.

Still need help? Contact Us Contact Us