Ideal for customers wanting to integrate Mailmark Data into their systems
Mailmark Direct Data is an item level data set with fixed fields detailing key information on mail items. This information can be blended with other information held by the customer and used to:
- Enhance existing Customer Relationship Management systems
- Trigger additional customer action including programmatic mail and e-channels
- More efficiently manage the mail supply chain
- Measure the performance of important customer communications
- Integrate mail into multi channel customer communications strategy
Technical specification for the download of item level data- this document is to provide customers and interested parties guidance on: requesting Mailmark Direct Data; accessing data securely; and the CSV data format structure.
- Technical specification access and onboarding- the focus of this document is to provide the technical detail to support customers and software providers to enable: secure, customer specific, retrieval of data files; development of an external solution to deliver data in a format and medium requested by end clients; and data integration with external customer solutions.
If you have any comments or queries on the above technical specifications please feed these to your Account Director.
Please be advised that we are making the following amends to the Mailmark Direct Data reports:
| # | Summary | Description |
| 1 | Handover Date | Currently, we are taking the handover date from MEARS and populating the MDD file, leading to multiple blank entries in the Handover Date column. We have changed the report to take the handover date from EMHS instead and populate this in the MDD Files in the Handover Date column. |
| 2 | Column Renaming | We are renaming the columns in the MDD summary file to provide an additional spare column ??" from Docket volume to Spare 1, Spare 1 to Spare 2, Spare 2 to Spare 3 |
| 3 | Padding | The MDD files have padding in the last row which increases the size of the files. We will remove the additional padding from the files and therefore the overall size of the files. |
| 4 | Missorts | Currently for missorts, the Expected to be Seen Location and First Seen Location are showing the same location ??" which is incorrect. The logic has been changed to select the correct location from the appropriate data and show where the item was first seen. |
| 5 | Column Switching | Currently, the columns for Expected to be Seen and Not Expected to be Seen are showing data in the incorrect order. The logic for these columns is being repointed in the backend to put the data in the correct column. |
These changes are estimated to go live on 14 January 2021.