VERIFIED SOLUTION i
X

Learn the recommendations to rematch events in EngageOne Delivery Audit

UPDATED: August 30, 2017


Rematching is required due to scans/event corresponding to a mailpiece(s) going into 'unmatched' tables due to failed/missed ingestion of mailpiece file.
After same Job (mailpiece file) is ingested successfully, Rematching is required to update the table used in mailpiece tracking.

Since rematch is a quite time consuming process, it is recommended to start with rematch interval of 1-2 days and this range can be increased in subsequent run depending on the rematch performance.

Refer Engage One Delivery Audit Operations Guide fro detailed steps on Events rematch. Topic is 'Managing Unmatched Postal Events'.

Downloads

  • No Downloads