Transaction ID is a unique identifier of the lead that helps to track any lead in PX or any other platform.
Where transaction ID is formed
Some leads are inserted into PX with Transaction ID formed by tracking systems (HasOffers, etc.).
If there is no Transaction ID sent in the lead, the unique one is automatically formed by PX platform.
You can easily identify where Transaction ID was formed:
- Transaction ID formed by HasOffers always starts with 102 and contains lowercase letters and digits:
If you use HasOffers integration, you need to send Transaction ID formed by HasOffers in each of your leads in LeadData section.
- Transaction ID formed by PX contains uppercase letters and digits:
If you insert the lead with Transaction ID, make sure this ID is unique. Otherwise, it will be impossible to track such a lead in the system.
The only exception is when the lead from API publisher comes to PX with Transaction ID that already exists in the platform. In this case, new Transaction ID and Lead GUID are generated for this lead.
How to use transaction ID
You can find any lead and transaction in the platform using Transaction ID. For this purpose, use search lookups by Transaction ID on Lead overview page and in the following reports:
Follow our troubleshooting articles to see more examples of how Transaction ID can be used.
Transaction ID in ping post
Transaction ID parameter is highly important for ping post functionality.
If publishers use ping post for posting leads, they first send Ping request to PX. PX forms Transaction ID for this lead and sends it back to the publisher in Ping response.
When the publisher sends Post request, this Transaction ID is a mandatory field that will allow PX to link Ping and Post transactions to one lead.
Transaction ID of rerun leads
All leads that have been reprocessed via Rerun management, have "-r" symbols with additional characters and digits at the end of the lead Transaction ID:
Please sign in to leave a comment.