VERIFIED SOLUTION i

Questions on the USPS Scan Date offset value for EngageOne Inform

Product Affected:  EngageOne™ Inform(Previously EngageOne™ Delivery Audit and MAIL360 Data Manager™)



 
1. Can the offset date be edited to some bigger value(may be 80 days) in the stored procedure to stop going those scans to an unmatched table? 
  • It is not recommended to change the stored procedures of EngageOne™ Inform(Previously EngageOne™ Delivery Audit and MAIL360 Data Manager™)
     Database.
2. Can the Job mailing date be updated of the IMB with the date when the Mailpiece is actually shipped to USPS?
  • Since the USPS decreed the 45-day time period, EngageOne Inform only matches scan events that occur within 45-days of the mailing date. For example, if an ingested mail piece file having mailing date as November 1st, EngageOne Inform will only match scan events for those IMBs starting on Nov 1 through the 45-day period. Scan Events received dated after the 45 days period are sent to the unmatched table. So if the mailing actually goes out on Dec 20, none of the scan events received will be matched, because the 45-day period for those IMBs has past. 
  • The fix for this is to change the mailing date in the mail piece file(s) to the actual mailing date, then re-ingest the mail piece file. Then run the re-matching process. 

 
UPDATED:  April 26, 2019