New callback transaction id format

A callback's transaction id (TxId) is an unique identifier that allows publishers to deduplicate the callbacks they receive in order to prevent double booking. This has been the case for screenout & complete events up until now. In contrast, Reconciliation Callbacks reused the transaction id of their corresponding complete callbacks and Rewarded Qualification Callbacks did not contain any transaction id at all.

The new BitLabs update resolves these shortcoming by guaranteeing unique transaction ids for every callback. To make this possible, we had to change the transaction id format and logic for all callback types.

These are the changes happening internally on BitLabs:

• Transaction Ids are no longer only numeric but can contain letters in the future as well (example: 12345, o233, b11).
• Reconciliation Callbacks will contain unique TxIds for every reconciliation. There is no longer a connection to their related complete callback.
• Rewarded Qualification Callbacks will contain TxIds as well which are unique per user.
• A new callback parameter [%REF%] is now available in reconciliation callbacks which contains the transaction id of the complete callback that is being reconciled.

The format for screenout & complete callbacks will remain the same, so publishers only using these callback types have to change nothing. If publishers are using any other callback type or are planning to, they have to make sure that they support alpha-numeric transaction ids.