Pass Back mechanism allows passing specific Buyer responses back to the Publisher after the Post. If the Lead is sold exclusively, additional fields Redirect URL and Buyer Raw Response can be passed back.
When Publisher inserts PassBack="True" in the Lead, default parameters (Buyer Guid, Transaction ID and Sold=True/False) are passed back automatically. There are additional fields that can passed back from Exclusive Buyer Campaign to the Publisher if they are previously configured:
- Redirect URL is usually used by Publisher to redirect the consumer to the final step of the process or for any other internal purposes.
- Buyer Raw Response is used to pass the text response from Buyer to Publisher as is, for example, the reason why Buyer has not bought the Lead.
In the future, this can be any other response (Buyer Email, Buyer Phone, Unique discount code, etc.).
There are three main conditions that ensure successful Pass Back flow for Redirect URL and Buyer Raw Response parameters:
- Campaign should have exclusive buyer type.
- Inserted Lead must contain PassBack="True" parameter. Please see PX Vertical Specification.
- Redirect URL and/or Buyer Raw Response must be configured in API Builder for a Buyer Campaign.
Extended Pass Back Flow
The Pass Back flow for Redirect URL and Buyer Raw Response is the following:
- Publisher inserts the Lead to PX with a PassBack="True" parameter.
- PX processes the Lead.
- The Lead is posted to a Buyer.
- If the Lead is sold to a Buyer, Buyer returns Redirect URL and/or Buyer Raw Response in a success response for this Lead. If the Lead is not sold, no link is passed (however, Buyer Raw Response still can be sent if configured in API Builder).
- PX returns constant parameters Transaction ID, Sold=True/False, Buyer Guid along with Redirect URL and/or Buyer Raw Response (if configured) from a Buyer response to the Publisher that inserted the Lead.
Pass Back is supported in XML, JSON formats. For Publishers that send HTTP requests Pass Back flow is a bit different.
XML Buyer Response Example
Two examples below show the situation when both Redirect URL and Buyer Raw Response parameters are configured in API Builder.
XML code example when Lead is sold:
<?xml version="1.0" encoding="UTF-8"?>
<Response>
<Result Value="BaeOK">
<TransactionId>D956FAF6-6CB2-427B-A7AD-2C51715158F9</TransactionId>
<TotalCount>1</TotalCount>
<PassBack>
<RedirectURL>https://www.502011tr021731axxxsb.com/RedirectIn.aspx?tk=03348bcc-8408-4a40-a319-497695f8ddd3&vid=963192&isac=LF16776</RedirectURL>
<BuyerRawResponse>Some text response from Buyer</BuyerRawResponse>
<Sold>True</Sold>
<BuyerGUID>4A6F8EF1-CA41-48B7-A5F2-F2C4A2949B1F</BuyerGUID>
</PassBack>
</Result>
</Response>XML code example when Lead is not sold:
<?xml version="1.0" encoding="UTF-8"?>
<Response>
<Result Value="BaeOK">
<TransactionId>693D0183-9BC8-428C-83CC-9475EEB57A5E</TransactionId>
<TotalCount>1</TotalCount>
<PassBack>
<BuyerRawResponse>Some text response from Buyer</BuyerRawResponse>
<Sold>False</Sold>
</PassBack>
</Result>
</Response>JSON Buyer Response Example
Two examples below show the situation when both Redirect URL and Buyer Raw Response parameters are configured in API Builder.
JSON code example when Lead is sold:
{
"Result": "BaeOK",
"TransactionId": "8DF593E1-66CC-4F6C-B4FE-471108C86FAC",
"TotalCount": "1",
"PassBack": [{
"Sold": "True",
"BuyerGUID": "4A6F8EF1-CA41-48B7-A5F2-F2C4A2949B1F"
}],
"PassBack ": {
"RedirectURL": "https://www.502011tr021731axxxsb.com/RedirectIn.aspx?tk=03348bcc-8408-4a40-a319-497695f8ddd3&vid=963192&isac=LF16776",
"BuyerRawResponse": "Some text response from Buyer"
}
}JSON code example when Lead is not sold:
{
"Result": "BaeOK",
"TransactionId": "2A21A972-1A5F-423B-9E79-B7375732FD29",
"TotalCount": "1",
"BuyerRawResponse": "Some text response from Buyer",
"PassBack": [{
"Sold": "False"
}]
}PX is not responsible for the wrong, fraud or offensive data passed back to the Publisher because it is passed back transparently.
0 comments
Please sign in to leave a comment.