united states postal service technical specification · technical specification: mail.dat® for...

TECHNICAL SPECIFICATION: MAIL.DAT® FOR INFORMED DELIVERY® VIA POSTALONE!®

United States Postal Service

®

Technical Specification

Mail.dat® for Informed Delivery

® via

PostalOne!®

Last Updated: May 4, 2018


Table of Contents

PREFACE ................................................................................................................................................... 3

1 INFORMED DELIVERY OVERVIEW ........................................................................................... 4

2 POSTALONE! ONBOARDING AND CONTACT INFORMATION ........................................... 5

3 MAIL.DAT VERSIONS SUPPORTED ........................................................................................... 6

4 CAMPAIGN CONFIGURATIONS – MID | IMB SERIALIZED | PERSONALIZED ............... 7

5 MAIL.DAT CAMPAIGNS WITH EDOC PRESORT DATA ..................................................... 14

6 MAIL.DAT MAILING SCENARIOS WITH EDOC PRESORT DATA .................................... 17

7 MAIL.DAT CAMPAIGNS WITHOUT EDOC PRESORT DATA ............................................. 28

8 FEATURE(S) SLATED FOR FUTURE RELEASES .................................................................. 31

9 LEGAL TERMS ............................................................................................................................... 32

APPENDIX – MAIL.DAT SPECIFICATION LISTS .......................................................................... 34


PREFACE This comprehensive technical specification outlines the steps and criteria for submitting an Informed Delivery interactive campaign through the Mail.dat file format via PostalOne! Electronic Documentation (eDocs). The intended audience for this document is a business mailer, marketer, or Information Technology (IT) staff member who uses mailing data to prepare or produce business mailings via PostalOne!. Therefore, this audience will already be familiar with the PostalOne! system, Mail.dat data communication options, and the Idealliance® Mail.dat specification. Please reference the USPS® Technical Specifications for Mail.dat and Mail.xml® and the Idealliance Mail.dat resources to review information about the PostalOne! environment. This technical specification provides an overview of the Informed Delivery feature, as well as file specifications and programmatic requirements for submitting an Informed Delivery interactive campaign via PostalOne!. USPS owns the following trademarks: Informed Delivery®, Intelligent Mail®, IM®, IMb®, PostalOne!®, Postal Service™, The Postal Service®, Standard Mail®, United States Postal Service®, USPS®, and ZIP Code™. The International Digital Enterprise Alliance owns the following trademarks: Idealliance®, Mail.XML®, and Mail.dat®.

For questions and comments related to this document please email USPS Informed Delivery eDoc Support Team at [email protected]

https://postalpro.usps.com/mailing/techspecs


https://www.idealliance.org/mail-dat

mailto:[email protected]


1 Informed Delivery Overview Informed Delivery is an optional, free feature that gives residential consumers the ability to digitally preview their mail and manage their packages arriving soon. Participating mailers can conduct an Informed Delivery “interactive campaign” by providing USPS supplemental content: a Representative Image, Ride-along Image, and target URL. The optional Representative Image is a color image chosen by the mailer that is used in lieu of a Flat image or in place of a grayscale Letter image. The required Ride-along Image is a color image that is clickable/interactive for the user through the provided target URL. This supplemental content allows an Informed Delivery user to take immediate action on a mailpiece and helps bridge the gap between physical and digital worlds.

1.1 Informed Delivery Consumer View Informed Delivery users can view grayscale images of Letter mail processed through automation equipment and supplemental content from participating mailers via email notification, online dashboard, or mobile app. With Informed Delivery, consumers can see what is coming to the mailbox—anytime, anywhere—even while traveling.

Figure 1: Informed Delivery Consumer View

1.1.1 Important Mailpiece Shape Information for Informed Delivery Campaigns A mailpiece must be automation compatible and scanned through USPS automation equipment in order to be presented to an Informed Delivery user.

USPS digitally images the address side of every Letter mailpiece that runs through automation equipment and shares those digital images with Informed Delivery users. When conducting an interactive campaign on Letter mailings, mailers can use eDocs to submit a Representative Image (optional), Ride-along Image (required), and target URL (required).

Flats are not scanned through USPS automation equipment in the same fashion as Letter mail, which results in limited visibility into campaigns on Flats. When conducting an interactive campaign on Flat mailings, USPS requires that mailers provide a Representative Image.


1.2 Informed Delivery Campaign Elements Please visit the Informed Delivery for Business Mailers website to learn more about the feature and campaign requirements. All mailers must review these materials prior to conducting an Informed Delivery campaign. The following campaign creation resources are available on the website:

Informed Delivery Overview

Interactive Campaign Guide

Campaign Image Requirements

Interactive Campaign FAQs

User and Household Data

1.3 Informed Delivery Campaign Reports At this time, only the Post-Campaign Summary Report is available for campaigns entered via PostalOne!. This report, depicted in the Interactive Campaign Guide noted above, provides the general results of an individual campaign, including information on the number of physical mailpieces processed, the number of users/mail recipients that were sent an email, the email open rate, and the number of click-throughs. Mailers must request this report upon completion of the campaign by emailing the Informed Delivery Program Office (IDPO) at [email protected].

2 PostalOne! Onboarding and Contact Information Before conducting a PostalOne! Campaign, please review the materials on the Informed Delivery for Business Mailers website as outlined in Section 1.2. Mailers can then direct technical questions and onboarding support regarding Mail.dat to the Informed Delivery eDoc Team.

2.1 Getting Started Follow the steps outlined below to set up your Customer Acceptance Testing (CAT) Business Customer Gateway (BCG) account and conduct an Informed Delivery campaign using PostalOne!:

Email the Informed Delivery eDoc team at [email protected] stating initial intent to start testing Informed Delivery Campaigns using PostalOne!. Please provide the following information:

o Point of contact name o Phone number

Coordinate with USPS to determine if the mailer submitting the campaign has participated in PostalOne! Customer Acceptance Testing (CAT) in the past.

• If the organization has not previously participated in PostalOne! CAT, follow the steps outlined in Section 2.2 to request a BCG account.

• If the organization has participated in PostalOne! CAT, please acquire the PostalOne! CAT credentials below, then proceed to step 3 of Section 2.2 below. These credentials will allow the organization to create a Mail.dat eDoc job for an Informed Delivery campaign.

• Username • Password • Customer Registration ID (CRID) • Mailer ID (MID) • Permit account number • ZIP Code™ related to the Permit

http://www.usps.com/informeddeliverycampaigns


https://www.usps.com/business/informed-delivery.htm


https://gateway-cat.usps.com/eAdmin/view/signin




2.2 Set Up Your PostalOne! CAT Account with Permit 1. Visit the USPS BCG CAT environment. 2. Create a BCG account:

a. Click on “Register for Free” b. Choose a username and password c. Provide security information d. Provide phone and email contact information e. Provide company name, information, and address

i. A BCG Business Account will be granted upon completion of these fields. The user will be automatically assigned a mailer CRID and MID. Those credentials appear on-screen within the application and will be sent to the registered email address on file.

3. Email the Informed Delivery eDoc team the following information: a. CRID b. MID c. Company name, address, and point of contact

4. Request that a Permit Imprint Postage Payment Account be created and activated. a. Note: The Permit should be funded with a large test balance amount so that Mail.dat

jobs with postage and campaign data can be submitted. 5. Once the CAT BCG account has been created, the CAT office will link the newly created Permit to

the mailer test CRID. 6. The CRID, MID, and Permit Account Number information can now be used to prepare and

submit Mail.dat jobs with Informed Delivery campaigns to PostalOne! CAT. 7. The PostalOne! CAT Mail.dat client can be downloaded from the PostalOne! BCG CAT page after

logging in. 8. The Informed Delivery eDoc team will validate the eDocs data and provide feedback if data

needs to be corrected to be eligible for production environment.

Any questions or information related to PostalOne! or the process outlined above can be sent to the Informed Delivery eDoc team. All general campaign questions related to supplemental content specifications, reporting, etc., can be directed to the IDPO.

3 Mail.dat Versions Supported

The following Mail.dat versions support the creation of Informed Delivery Campaigns

Mail.dat Version Support Starts Changes

17-2 January 8, 2017

18-1 April 7, 2018 Increased RMR value from 90 characters to 250 characters

Increased RMB Value from 90 characters to 250 characters

Removed RMR Start date and End dates (unused fields that were moved to RMS

Table 1 - Technical Specification Version Support




4 Campaign Configurations – MID | IMb Serialized | Personalized

This section documents the various ways in which an Informed Delivery campaign can be created and applied. The information described below further outlines how campaign elements make a campaign unique (distinguishable from other campaigns), how campaign treatments are applied to pieces/IMbs, and the various ways to configure a campaign.

4.1 Campaign Elements (Unique Campaign Definition):

A campaign consists of dataset that can be applied to one or more pieces/IMbs. The unique combination of these data elements make a campaign unique. A unique campaign can be applied to a set of pieces/IMbs or to an individual piece/IMb. A unique campaign dataset consists of the following data elements:

Campaign Title

Campaign Code

Campaign Start Date

Campaign End Date

Campaign Display Name

Campaign Ridealong Image (URL)

Campaign Ridealong Target (URL)

Campaign Representative Image (URL)

4.2 Campaign Image and URL Requirements

The campaign materials submitted to Informed Delivery via PostalOne! must adhere to the requirements listed below:

All Ride-along (.rmr/.rmb type of A) and Representative (.rmr/.rmb type of C) images hosted on mailer/submitter server must be in JPG format

All images must be hosted on a web server and must be accessible via http or https protocol o All image URLs must start with http:// or https://

Color mode of images can only be RGB (CMYK, or other color mode supported)

For Representative/Replacement image the dimensions are required to be within 500 pixels high x 780 pixels wide

For Ride-along image the dimensions are required to be within 500 pixels high x 500 pixels wide (though the recommended size is 200 pixels high x 300 pixels wide)

All images must not exceed a file size of 200 KB

All Target URLs (.rmr/.rmb type of B) must start with http:// or https://

4.3 Campaign Treatment Application Process

Campaign treatment is defined as the set of images (Ride-along Image and Representative Image) and URL (Target URL) that are applied to a mailpiece/IMb. Upon receipt of the scan and/or image data from Mail Processing Equipment (MPE), the Informed Delivery application matches the IMb barcodes and applies the associated campaign treatment to the pieces for the consumer view.


4.4 Campaign Configurations

Mail.dat supports nine configurations for Informed Delivery campaigns. The configurations are divided into three categories: MID Campaigns, IMb Serialized Campaigns, and Personalized Campaigns. These three categories are further subdivided into the nine configurations displayed below.

Note: The RMS “Campaign Serial Grouping” is one of the central configuration data elements, (additional details are documented below as part of the configuration options). For Serialized campaigns where the URLs are the same across a set of pieces the “Campaign Serial Grouping” must be set to C = Continuous and must not be left Blank. If the “Campaign Serial Grouping” is left Blank, it causes the Informed Delivery application to process the campaign as a piece level campaign, which results in each mailpiece to be linked with a separate campaign record, increasing processing time and impacting campaign creation. Mailers interested in testing Personalized campaigns must make a formal request to the eDoc team.

MID Campaigns IMb Serialized Campaigns Personalized Campaigns



4.4.1 Campaign Configuration Details

Campaign configurations depicted in Section 0 are further described in detail with the Mail.dat job make-up in the table below.


Definition: A Campaign applied to all IMbs/Pieces (Flats or Letters), that use a given MID in the IMbs. Campaign applied to all pieces with given MID in the IMb for a limited duration.

Definition: A Campaign applied to a set of Pieces/ IMbs.

Definition: A unique Campaign applied to a Pieces/IMb. Each Piece/IMb receives its own campaign treatment.

Applies to: Jobs with Presort Data

Applies to: Jobs with Presort Data Jobs without Presort Data

Applies to: Jobs with Presort Data Jobs without Presort Data

Configuration 1A - Presort Job contains: • A standalone CPT, with no

links to a Mailpiece Unit/Component record (MCR)

• CPT contains all required fields and “Mailer ID of Mail Owner”

• RMR only contains 1 set of URLs

• RMR is linked with RMS and the standalone CPT

Configuration 2A – Presort Job contains: • RMS contains Campaign

summary information and Campaign Serial Grouping is set to C = Continuous

• CPT links to MCR • RMR contains a set of URLs • RMR is linked with RMS and

CPT • CPT is linked with a set of

pieces in either PDR or PBC Configuration 2B – Presort Job contains: • RMS contains Campaign


• RMR contains a set of URLs

Configuration 3A – Presort Job contains: • RMS contains Campaign

summary information and Campaign Serial Grouping is set to Blank = Non Continuous

• RMR contains a set of URLs for each Mailpiece/IMb

• RMR is linked with RMS • RMR is linked with each

piece in PDR Configuration 3B – Presort Job contains: • RMS contains Campaign




• RMR is linked with RMS • RMR is linked with a set of

pieces in PDR Configuration 2C – Presort Job contains: • RMS contains Campaign


• RMR contains a set of URLs • RMR is linked with RMS • RMR is linked with a set of

pieces in PBC Configuration 2D – Non-Presort Job contains: • RMS contains Campaign


• RMB contains a set of URLs repeated for a set of pieces/IMbs within the RMB

• RMB is linked with RMS

• RMR contains a set of URLs for each Mailpiece/IMb

• RMR is linked with RMS • RMR is linked with each

piece in PBC Configuration 3C – Non-Presort Job contains: • RMS contains Campaign


• RMB contains a set of URLs for each Mailpiece/IMb

• RMB is linked with RMS

Table 2 - Campaign Configuration Details

4.4.2 IMb Serialized Campaign Key Data Combination

Informed Delivery uses the combination (composite key) of the following eight data elements to group and identify an IMb Serial Number range that belongs within a campaign.

1. Campaign Serial Grouping (RMS type of C) 2. MID from IMb on mailpiece (PDR/PBC/RMR) 3. Campaign Start Date (CSM/RMS) 4. Campaign End Date (CSM/RMS) 5. Ride-Along Image URL (RMR type of A) 6. Ride-Along Target URL (RMR type of B) 7. Replace Image URL (RMR type of C) 8. Replace Image Target URL (RMR type of D)

Notes: Replace Image refers to the “Representative Image” in the PostalOne! environment and throughout this guide.

Using the data elements identified above, Informed Delivery then determines the lower and upper IMb Serial Number range for the given unique set(s) of campaign data. The Informed Delivery application applies the same campaign treatment (image(s) and target URL) to all mailpieces within the IMb Serial Number range in the eDoc. As mailers submit new eDocs with previously submitted campaign elements, the Informed Delivery application updates the IMb


Serial Number range as needed (i.e., if the new mailpieces fall outside of the previous Serial Number range). The RMS “Campaign Serial Grouping” is one of the central configuration data elements. For Serialized campaigns where the URLs are the same across a set of pieces the “Campaign Serial Grouping” must be set to C = Continuous and must not be left Blank. If the “Campaign Serial Grouping” is left Blank, it causes the Informed Delivery application to process the campaign as a piece level campaign and results in each mailpiece to be linked with a separate campaign record, increasing processing time. Mailers interested in testing Personalized campaigns must make a formal request to the eDoc team.

4.4.2.1 Application of a Campaign to Parts of an IMb Serial Number Range

When a mailer applies the same Informed Delivery campaign to mailpieces in different Serial Number ranges, the Informed Delivery application creates one campaign within the whole IMb Serial Number range. Mailers are able to exclude the mailpieces between the two Serial Number ranges from the campaign by creating two separate campaigns instead of one single campaign. Mailers can create two campaigns by making any of the seven fields different between the two sets of data (e.g., copying the Ride-Along Image URL and using the original in the first set and a copy in the second set). See the table below for an example.

Table 3: Removing Serial Number Range of Pieces Not Included in Campaign

4.5 PostalOne! Validations PostalOne! validates all data fields as part of the campaign submission process. The following business rules must be followed when submitting an Informed Delivery campaign using PostalOne!:

Mailers can also provide Campaign Start and End Dates as part of the Container Summary (CSM or .csm file) record or data set for the pieces in a container; the Campaign Start and End Dates in the CSM take precedence over those provided in the RMS record.

When using the PDR or PBC linkage, the Container Quantity (CQT) Database ID is required as part of the RMR data set. This CQT Database ID in RMR allows mailers to bypass the referential integrity validations for the RMS and RMR parent-child relationship. This step transmits a sub-set of RMRs with the Mail.dat job, which usually takes place when a mailing is being mailed across multiple days.

Campaign data in the RMR data set can be updated until the associated Containers (CSM Container Status records) are set to “R” for Ready-to-Pay (USPS Processing Due (UPD) status). This option is presented when generating or updating the Mail.dat file.


If RMR and RMS files are submitted as part of the original eDoc submission, these files do not need to be submitted again when the containers’ statuses in CSM are set to “R” for Ready-to-Pay.

Note: With regard to updating or deleting a campaign, PostalOne! uses the container status of Ready-to-Pay to transmit the Informed Delivery campaign data to the Informed Delivery application. Updates can only be made to the container prior to or during Ready-to-Pay status. Ready-to-Pay submission of eDocs is the only time campaign data is pushed to the Informed Delivery application.

4.6 Informed Delivery Validations The Informed Delivery application validates all data fields as part of the campaign submission process. The following business rules must be followed when submitting an Informed Delivery campaign using Mail.dat with eDoc presort data:

Campaign Start Date cannot be in the past.

Campaign End Date cannot be in the past.

Campaign End Date must be at least one day after the Campaign Start Date.

The Serial Number must be the proper length: either 6 digits or 9 digits, depending on whether a 6-digit or 9-digit MID is used.

The target URL must be valid and must use a lower-case “http” (as opposed to upper-case “HTTP”).

The Ride-along and Representative Images must be in the Joint Photographic Experts Group (JPEG or JPG) format. The images must adhere to the image requirements outlined in the Campaign Image Requirements on the Informed Delivery for Business Mailers website.

The campaign cannot overlap with an existing Active campaign.

Intelligent Mail package barcode (IMpb) campaigns are not supported at this time.

4.7 Mail.dat Receipt Data from Informed Delivery Informed Delivery shares the results of campaign creation process with PostalOne! this data can be retrieved as part of Mail.dat Enhanced XML Receipt files. Below is a list of Warnings that

Warning Code

Warning Description

4830 For an Informed Delivery Campaign, a start date is required.

4831 For an Informed Delivery Campaign, an end date is required.

4832 For an Informed Delivery Campaign, a serial number within the barcode is required.

4833 For an Informed Delivery Campaign, a campaign code is required.

4834 For an Informed Delivery Campaign, a campaign title is required.

4835 For an Informed Delivery Campaign, a mailer ID within the barcode is required.

4836 For an Informed Delivery Campaign, the start date cannot be in the past.

4837 For an Informed Delivery Campaign, the end date cannot be in the past.

4838 For an Informed Delivery Campaign, the end date cannot be before the start date.

4839 For an Informed Delivery Campaign, the end date cannot be the same as the start date.

4840 For an Informed Delivery Campaign, the serial number length must be valid within the barcode.

4841 For an Informed Delivery Campaign, the end serial cannot be before the start serial.

4842 For an Informed Delivery Campaign, the target URL must be formatted properly



Warning Code

Warning Description

(http://www.url.com).

4843 For an Informed Delivery Campaign, the campaign cannot overlap with an existing campaign for the barcode MID.

4844 For an Informed Delivery Campaign, the campaign code must be unique for the barcode MID.

4845 For an Informed Delivery Campaign, the campaign serial grouping was invalid. A continuous campaign with the same Campaign Code has a different value for one of the below fields:

MID from IMb

Start Date of Campaign

End Date of Campaign

Ride-Along Image URL

Ride-Along Target URL

Replace Image URL Replace Image Target URL

4846 For an Informed Delivery Component Campaign, the mail owner MID is required.

4847 For an Informed Delivery Campaign, a display name is required.

4848 For an Informed Delivery Campaign, the replacement URL must be formatted properly (http://www.url.com).

4849 For an Informed Delivery Campaign, the ride along image max file size is 200KB and the pixel max size is 300 X 200. This error code is generated if one of the following fails:

File type other than JPG (only JPG are supported)

Color mode can only be RGB (no CMYK, no other color mode supported)

URL must start with http:// or https://

Height 500 pixels (recommended less than or equal to 200 pixels)

Width 500 pixels (recommend less than or equal to 300 pixels)

File size cannot be more than 200 KB Note: The dimensions documented above only apply to campaigns submitted via PostalOne! (Campaigns entered through the Mailer Campaign Portal allow slightly different dimensions).

4850 For an Informed Delivery Campaign, the replacement image max file size is 200KB and the pixel max size is 780 X 500. This error code is generated if one of the following fails:

File type other than JPG (only JPG are supported)

Color mode can only be RGB (no CMYK, no other color mode supported)

URL must start with http:// or https://

Height cannot be more than 500 pixels

Width cannot be more than 780 pixels

File size cannot be more than 200 KB Table - Warning Codes from Informed Delivery

http://www.url.com/

http://www.url.com/


5 Mail.dat Campaigns with eDoc Presort Data Informed Delivery campaigns can be submitted as part of the Mail.dat eDoc presort data submission to PostalOne!. A Mail.dat file using presort data includes, but is not limited to, the following data sets related to the mailing:

Mail Sort Plan

Mail Entry Plan

Handling Unit and Container Nesting Information

Payment Account Information

Postage calculation details

Special Services Requested

Mailpiece Level Data such as Barcodes Shapes, or Weights

Mail.dat files using presort data can also include additional Informed Delivery campaign data in the form of Summary and Detail data sets. Informed Delivery now includes two additional data sets:

Referenceable Mail Summary Record (RMS)

Referenceable Mail Record (RMR) Mail owners can provide additional information through the Container Summary Record (CSM).

Note: PostalOne! supports Informed Delivery campaigns for Mail.dat version 17-2. Mail.xml support is slated for a future release.

5.1 Mail.dat Informed Delivery Campaign Data Linkage Options Mailers can use both the client user interface and batch processing modes in the submission process. Additional data sets—RMS and RMR—are available in Mail.dat version 17-2 and can be used in one of the following three combinations:

Figure 2: Campaign Data Linkage Options

Note: PostalOne! and Idealliance require mailers to submit additional data sets as part of presort data. Please reference the USPS Technical Specifications for Mail.dat and the Idealliance Mail.dat resources to review information about the PostalOne! environment.

Together, the RMS and RMR files provide campaign summary data from the PostalOne! system, which sends this data to the Informed Delivery application. Each file also plays a pivotal role in Informed Delivery in its own way:


https://www.idealliance.org/mail-dat


The RMS file aggregates metrics and provides a reference for the campaign within mailer systems. The fields in the RMS include:

Campaign Title

Campaign Code

Brand Display Name

Campaign Start and End Dates The RMR file provides linkage to the PDR or PBC files, both of which contain piece barcodes. The fields in the RMR include:

Ride-along Image

Target URL

Representative Image

CQT database ID to support mailpieces with Informed Delivery campaign

Links to the CPT, PDR, or PBC files

5.2 Mail.dat Version 17-2 File Descriptions and Informed Delivery Campaign Data Sets

The table below identifies the Mail.dat file naming convention and the corresponding Idealliance and USPS standards for the Informed Delivery application.

File Definition Header File name .hdr/HDR

The HDR file introduces the entire Mail.dat. It identifies who created the file, the Idealliance standard version used (ensuring compatibility with other users), and when the file was created. Most importantly, it identifies the total file record count for each file type. The Header also provides information such as the type of presort software used and the history of who has touched the Mail.dat file. The first indication that a file is incomplete is if the Header record displays a different number of records than received; an incomplete file is invalid. RMS Record Count – Required data field added to transmit/store the count for the file RMS

Record.

RMS Status – Required data field added to transmit/store the status for the RMS Record.

RMR Record Count – Required data field added to transmit/store the count for the RMR Record.

RMR Status – Required data field added to transmit/store the status for the RMR Record.

User Option Field – Note that character spaces from the User Option Field were repurposed to support the addition of the data fields enumerated directly above.

“Mail.dat presentation category” is one of the Key fields in HDR for Informed Delivery. Informed Delivery campaigns with Presort data can use values such as P, M, N, C, E, and T. Informed Delivery campaigns without Presort data must use the value of “I”.

Component File name .cpt/CPT

The CPT file is used to define those parts of a mailpiece unit (MPU) by the mail class for which they qualify (e.g., a magazine is in the Periodicals mail class). However, the publisher may decide to attach a mailpiece that is ineligible for Periodical rates to the front of the magazine, making this ineligible mailpiece a Standard Mail® piece. Each of these parts would be identified with a separate CPT record that is linked to the appropriate MPU. This file can drive the campaigns by each CPT record by linking with an RMR file or by linking to physical piece records in the PDR or PBC files.

Container Summary File name .csm/CSM

The CSM file identifies each container’s level, destination, point of entry, and contents in terms of rates, copies, pieces, and weight. The Container Types can be pallets, sacks, tubs, trays, and hangers. There will be one CSM record per container. Mailers also have the option of providing the Campaign Start and End Dates at the container level, which will override all campaign dates provided in the RMS record.

Piece Detail File name .pdr/PDR

The PDR file is used as a requirement for full service and mixed service mailings and helps identify actual mailpieces for multiple full-service and Seamless Acceptance program compliance requirements. PDR files also can be used to:

1. Identify individual wasted or shortage pieces in a mailing. 2. Support mixed service mailings with full service pieces that lack sequentially numbered

IMbs. 3. Support all pieces in a single Informed Delivery mailing. Informed Delivery applies

campaigns by Serial Number. Therefore, all pieces within the Serial Number (serialization)


File Definition range in the IMb are included in the campaign.

Note: Either the PDR file or PBC file is required to conduct an Informed Delivery campaign. If used in the file set, the PDR is required to conduct a campaign and must include the mailer’s IMbs, Serial Numbers, and MIDs in the IMbs.

Piece Barcode File name .pbc/PBC

PBC files are used as an alternative to the PDR file. Informed Delivery applies campaigns by Serial Number. Therefore, all pieces within the Serial Number (serialization) range in the IMb are included in the campaign. Note: Either the PDR file or PBC file is required to conduct an Informed Delivery campaign. If used in the file set, the PDR is required to conduct a campaign and must include the mailer’s IMbs, Serial Numbers, and MIDs in the IMbs.

Referenceable Mail Record File name .rmr/RMR

The RMR file provides linkage to CPT, PDR, or PBC files for campaigns, which creates the Representative Image, Ride-along Image, and target URL. The following fields comprise the RMR file:

Job ID – Field to identify the Job ID. Foreign key as well as the master key that links all files in a job with each other and with the Header.

RMR ID – Key field, same data/value as the key fields for the CPT, PDR, or PBC records that this record should be linked to. One of the following three values can be used: PBC - PBC Unique, right justify and zero fill; PDR – Piece ID; CPT – CPT ID (zero fill prior to numeric, if numeric only). o Validations 4714 and 4715 will appear as errors:

4714 – When the RMR ID Type is B = PBC, the RMR ID must correspond to a PBC Unique ID in the PBC file.

4715 – When the RMR ID Type is P = PDR, the RMR ID must correspond to a Piece ID in the PDR file.

RMR ID Type – Field links to a piece through PDR, PBC, or CPT. Field values are P = PDR, B = PBC, and C = CPT. These values denote the type of record (CPT, PDR/PBC) that the RMR (this record) represents. When RMR ID Type is “C”, the linkages from CPT are traversed down to IMbs in PDR or PBC.

RMS ID – Foreign key refers to the RMS ID of the RMS Record.

RMR Content Type – Field to capture the type of RMR content. RMR content can either be a URL of a media image that is supported by browsers or a target URL that will be placed as a hyperlink for the media/image. All of the following values are supported and passed to the Informed Delivery application: o A = Content Type A – Required Ride-along Image URL (URL for the image source location,

this image is displayed alongside the grayscale mailpiece image or Representative Image). ( o B = Content Type B – Required Ride-along Image Target URL (a hyperlink for the

media/image. o C = Content Type C – Replace Image URL (URL for the image source location. This image is

used in lieu of a Flat image or in place of a grayscale Letter image. o D = Content Type D – Representative Target URL (Does not need to be populated because

the URL does not appear to in Informed Delivery consumers in email messages or on the consumer dashboard).

o O = Content Type O, Opt Out – Not supported by the Informed Delivery application.

CQT Database ID – This data field is the CQT Database ID from the .cqt file. It is used in the RMR and supports the identification of a group of mailpieces (IMbs) with similar characteristics in PDR or PBC that are being mailed on a given day. o Note: Required for RMR type of B = PBC and P = PDR.

RMR Value – This field contains the 90-character URLs of associated campaign material: URL for Ride-along Image (identified by Content Type A), URL for the target page (identified by Content Type B) to which consumers will be directed, URL of the Representative Image (identified by Content Type C), and URL of the Representative target (identified by Content Type D). o Note: The URL for the Representative target is currently used only to compare the set of

URLs for grouping of mailpieces under the one campaign. This field is not used in Informed Delivery to display or link to any marketing materials. It is recommended that Content Type D not be provided as part of the Mail.dat job.

Start Date – With Mail.dat version 17-2, this data element is daggered (marked with a dagger icon) and is to be filled with blank spaces. The campaign Start Date in RMS should be used.

End Date – With Mail.dat version 17-2, this data element is daggered and is to be filled with blank spaces. The campaign End Date in RMS should be used.

Referenceable Mail Summary File name .rms/RMS

The RMS file is used to provide campaign names and Start and End Dates, as well as link campaign information with the RMR record.

Job ID – Field to identify the Job ID. Foreign key refers to the Header record.

RMS ID – Key field to identify each unique RMS Record.

Campaign Title – Title of the Informed Delivery campaign. Displays internally on the USPS Informed Delivery Administrative console.


File Definition Campaign Code – The Campaign Code must be unique for every campaign. If the same campaign

Code is used across multiple jobs, the Informed Delivery application will treat the jobs as the same campaign.

Campaign Serial Grouping – This field is used to identify if the IMbs can be grouped together under an IMb Serial Number range. This field is used to identify one of the two types of campaigns:

o Blank = IMbs not in continuous Serial Number range. This option should create single-piece campaigns. This option should be used when the campaigns are personalized and/or the IMbs are not in continuous Serial Number range. As of publication of this document, personalized campaigns are not available. At this time, the PostalOne! application ignores any information inputted in this field.

o C = IMbs in continuous Serial Number range with non-personalized campaigns.

Display Name – Display Name of the mail owner or brand that appears in consumers’ email notifications and Informed Delivery dashboard views.

Date Start – Start Date when the Referenceable Mail Content can be used.

Date End – End Date by when the Referenceable Mail Content can be used.

RMS Record Status – Used to denote the status of the record as O = Original, D = Delete, I = Insert, or U = Update.

Table 4: Mail.dat 17-2 File Names and Descriptions

6 Mail.dat Mailing Scenarios with eDoc Presort Data

USPS designed the PostalOne! Mail.dat database to be flexible and support an organization’s mailing needs. This section explains each Mail.dat file with eDoc presort data by scenario and unique set-up processes. Each mailer or Mail Service Provider (MSP) has the choice to drive their campaigns through CPT or through physical piece (PDR or PBC) data. For each scenario, the CPT is linked to RMR. RMS originates the campaign while RMR represents the details of that same campaign.

The CPT-driven scenario will link to PDR or PBC, which are tied with RMR for the Representative Image, Ride-along Image, and target URL.

The RMR is tied with RMS to manage the Campaign Title, Start and End Dates, and display fields for campaigns.

Each process outlined in the following sections creates the Representative Image, Ride-along Image, and target URL that the user sees in their notification, on their dashboard, or on the mobile app.

6.1 Conventional/Single Campaign Presentation at Component Level (.cpt) The Conventional/Single Presentation scenario applies to Letter and Flat mailings with one campaign at the CPT file-type level. This scenario serves a single address list for single versions that run through the presort process, thus generating a single CPT record.

The creation of a campaign from a Conventional/Single Mail.dat file using CPT as the campaign driver includes the following presort data configuration and processes:

All mailpiece versions (CPT) for Figure 3: Scenario Driven by Component Level


mail owners are tied to a specific campaign.

Campaign records are included in the RMS and RMR with the following information: o Campaign Title o Campaign Code o Campaign Start and End Dates o Representative Image (optional for Letter mailings and

required for Flats) o Ride-along Image o Target URL

Campaigns are tied to physical pieces with IMb barcodes. These pieces are located in PDR or PBC records. The campaign data in RMS-RMR is tied to the PDR or PBC piece records by using the relationship from CPT to PDR or CPT to PBC.

Campaign Start and End Dates provided in a CSM file will override Start and End Dates provided in the RMR file.

Campaign data from PostalOne! is transmitted to Informed Delivery when mail containers are marked with a Ready-to-Pay status (CSM Container Status is “R”). Informed Delivery processes the campaign data and creates unique campaigns based on the campaign data from PostalOne!.

Upon receipt of the image data from Mail Processing Equipment (MPE), the Informed Delivery application matches the IMb barcodes and applies the associated campaign treatment to the pieces for the consumer view.

6.1.1 Sample Data The tables below represent sample data and relationships between CPT, RMR, and RMS files. They also depict key fields for Conventional/Single Presentation at the CPT level. Note: The component ID must have a corresponding MCR record. PostalOne! does not support updates of this field—the application only inserts new records that are supported for the key fields.

Job with a single Campaign Conventional/Single Presentation (.cpt level with .pdr)

CPT Job ID Component ID Component Description Weight Source Status Class Shape

C12345670 111111112 Summer Sale 99995 L P 1 LT

RMR Job ID RMR ID RMR ID Type RMR Content Type RMR Value RMS ID …

C12345670 111111112 P A http://www.SummerSale.com/123vb.jpg A1234567

C12345670 111111112 P B http://www.SummerSale.com A1234567

RMS Job ID RMS ID Campaign Title Display Name Date Start (17-2 onwards in RMS – Date

Start) End Date (17-2 onwards in RMS Date End)

…

C12345670 A1234567 Summer Sale ACME Car Sales 20170510 20170510

PDR Job ID CQT Database ID Package ID Piece ID Piece Barcode IM Barcode …

C12345670 32858902 A1234567 111111112 10234300343 0100191600504800000124022999801

C12345670 32850289 A1234567 111111112 10234344343 0100191600504800000124022999802

C12345670 32858985 A1234567 111111112 10234300345 0100191600504800000124022999803

Table 6: Conventional/Single Presentation (RMR Linkage to CPT with Pieces in PDR)

Table 5: Conventional/Single Presentation (RMR Linkage to CPT with Pieces in PBC)

Job with a single Campaign Conventional/Single Presentation (.cpt level with .pbc)


C12345671 11730212 Car Sales 99995 L P 1 LT


C12345671 11730212 B A http://www.AcmeCarSales.com/img.jpg S2763890

C12345671 11730212 B B http://www.AcmeCarSales.com S2763890



…

C12345671 S2763890 Car Sales ACME Car Sales 12212017 12282017

Figure 4: CPT or PBC/PBR Scenario Using Conventional Presort Software


6.2 Conventional/Single Campaign Presentation at Piece Level (.pbc/.pdr)

The Conventional/Single Presentation applies to Letter and Flat mailings with one campaign at the PBC or PDR level. This scenario accommodates a single address list for a single version that runs through the presort process, thus generating a single CPT record. To begin this process, choose a CPT record, create a campaign against the CPT record, and create an RMR with a Representative/Ride-along Image, target URL, and display name. CSM can be used as an option to manage Start and End Dates. The creation of a campaign from a Conventional/Single Mail.dat file using PBC or PDR as the campaign driver includes the following presort data configuration and processes. This information is visually represented in Figure 4 within Section 4.1.

All mailpieces (PDR/PBC) are tied to a specific set of campaigns.

Campaign records are included in the RMS and RMR with the following information: o Campaign Title o Campaign Code o Campaign Start and End Dates


o Representative Image (optional for Letter mailpieces and required for Flats) o Ride-along Image o Target URL

Campaigns are tied to physical pieces with IMb barcodes. These pieces are located in PDR or PBC records. The campaign data in RMS-RMR is tied to the PDR or PBC piece records.

Campaign data from PostalOne! is transmitted to Informed Delivery when mail containers are marked with a Ready-to-Pay status. Informed Delivery processes the campaign data and creates unique campaign(s) based on the campaign data from PostalOne!.

Upon receipt of the image data from MPE, the Informed Delivery application matches the IMb and applies the associated campaign treatment to the pieces for the consumer view.

Note: At this time, piece level personalized campaigns are not supported.

6.2.1 Sample Data The table below represents sample data and the relationship between PBC, RMR, and RMS files. The table also depicts key fields for Conventional/Single Presentation at the PBC level.

Job with a single Campaign

Conventional/Single Presentation with .pbc Level CPT Job ID Component ID Component Description Weight Source Status Class Shape

C12345672 11730213 Houses Sales 99995 L P 1 LT

zRMR

PBC Job ID PBC Unique ID CQT Database ID Package ID Barcode Wasted or Shortage Piece indicator …

C12345671 200654854 32858902 200038 0100190000504800000124022999804

C12345671 200654855 32858903 200038 0100190000504800000124022999805

C12345671 200654856 32858904 200038 0100190000504800000124022999806

Figure 5: Piece Level Driven Scenario


Job with a single Campaign

Conventional/Single Presentation with .pbc Level Job ID RMR ID RMR ID Type RMR Content Type RMR Value RMS ID …

C12345672 11730213 B A http://www.HouseSales.com/img.jpg S2763891

C12345672 11730213 B B http://www.HouseSales.com S2763891

RMS Job ID RMS ID Campaign Title Display Name Date Start (17-2 onwards in RMS –

Date Start) End Date (17-2 onwards in RMS Date End)

…

C12345672 S2763891 Houses Sales ACME Houses Sales 12102017

12182017


C12345672 200654857 S2763891 200039 0100190000504800000124022999807

C12345672 200654858 S2763892 200039 0100190000504800000124022999808

C12345672 200654859 S2763893 200039 0100190000504800000124022999809

Table 7: Conventional/Single Presentation RMR Linkage with Pieces in PBC

The table below represents sample data and the relationship between PDR, RMR, and RMS files. The table also depicts key fields for Conventional/Single Presentation at the PDR level.

Job with a single Campaign Conventional/Single Presentation with .pdr Level

CPT

Job ID Component ID Component Description Weight Source Status Class Shape

C12345673 111113312 ACME Card Activation 99995 L P 1 LT


C12345673 111113312 P A http://www.AceCardactiation.com BC234565

C12345673 111113312 P B http://www.AcCardactition.com/134.jpg BC234565



…

C12345673 BC234565 Card Activation ACME Card Activation

20170510 20170510


C12345673 22858902 A9573510 111113312 10234300343 0100191600504800000124022999810

C12345673 22850289 A9573511 111113312 10234344353 0100191600504800000124022999811

C12345673 22858985 A9573512 111113312 10234300300 0100191600504800000124022999812

Table 8: Conventional/Single Presentation RMR Linkage with Pieces in PDR

6.3 Conventional/Multiple Campaign Presentations at Piece Level (.pdr or .pbc)

The Conventional/Multiple Presentation applies only to Letter mailings.

Note: Piece level campaigns are not the same as personalized piece level campaigns, which is currently being supported in a test environment only.

6.3.1 Scenario Description

Create the Mail.dat presort eDocs data o This file maps physical mailpiece IMb data (PDR or PBC) with specific

mail owner campaigns o A campaign record can be created in RMR by providing the Campaign

Start Date and End Date, as well as the Representative Image, Ride-along Image, and target URL for each campaign.

o If provided in the CSM file, Campaign Start Date and End Date will override those provided in the RMR.

Upon receipt of the eDocs data from PostalOne! and image data from MPE, the Informed Delivery application matches the campaign information with the eDocs data.

Figure 6: PDR or PBC for Conventional Presort Process


6.3.2 Sample Data The table below represents sample data and the relationship between PBC, RMR, and RMS files. The table also depicts key fields for Conventional/Single Presentation at the PDR level.

Job with Multiples Campaigns driven by .pdr Level

CPT Job ID Component ID Component

Description Weight Source Status Class Shape

B12349800 144411145 Cleaner House 10% 99995 L P 1 LT


B12349800 144411145 P A http://www.Cleanerhouse.com/img.jpg Z1234567

B12349800 144411145 P B http://www.Cleanerhouse.com Z1234567





B12349800 144411150 P A http://www.GarageACME.com/1034.jpg Z1234568

B12349800 144411150 P B http://www.GarageACME.com Z1234568





B12349800 144411156 P A http://www.RoofRmt.com/img.jpg Z1234569

B12349800 144411156 P B http://www.RoofRmt.com Z1234569






Start) End Date (17-2 onwards in RMS Date End) …

B12349800 Z1234567 Cleaner House 10% Cleaner House 20182017 20232017

B12349800 Z1234568 Garage Repair Installation

Garage Repair Installation

20152017 20202017

B12349800 Z1234569 Roof Replacement 50% Off

ACME Roof Replacement

20082017 20132017


B12349800 32858902 A1234567 144411145 10234300343 0100191600504800000124022999801

B12349800 32858905 A1234567 144411146 10234300343 0100191600504800000124022999804

B12349800 32858906 A1234567 144411147 10234300343 0100191600504800000124022999805

B12349800 32858909 A1234567 144411150 10234300343 0100191600504800000124022999808

B12349800 32858910 A1234567 144411151 10234300343 0100191600504800000124022999809

B12349800 32858911 A1234567 144411152 10234300343 0100191600504800000124022999810

B12349800 32858912 A1234567 144411153 10234300343 0100191600504800000124022999811

B12349800 32858915 A1234567 144411156 10234300343 0100191600504800000124022999814

B12349800 32858916 A1234567 144411157 10234300343 0100191600504800000124022999815

B12349800 32858917 A1234567 144411158 10234300343 0100191600504800000124022999816

Table 9: Job with Multiple Campaigns Driven by RMR Linkage with Pieces in PDR

The table below represents sample data and the relationship between PBC, RMR, and RMS files. The table also depicts key fields for Conventional/Single Presentation at the PBC level.

Job with Multiples Campaigns driven by .pbc Level

CPT Job ID Component ID Component

Description Weight Source Status Class Shape

C12345671 73540212 Test TM Card 99995 L P 1 LT


C12345671 73540211 B A http://www.AcmeCarSales.com/img.jpg P2763456

C12345671 73540211 B B http://www.AcmeCarSales.com/ P2763456





C12345671 73540221 B A http://www.TestSF.com/1243.jpg P2763457

C12345671 73540221 B B http://www.TestSF.com P2763457





C12345671 73540231 B A http://www.TestTM.com/creditcard.jpg P2763458

C12345671 73540231 B B http://www.TestTM.com P2763458







…

C12345671 P2763456 Test TM Card Test TM Card 12212017 12282017

C12345671 P2763457 Test S Insurance Test S Insurance 12302017 01022018

C12345671 P2763458 Test Bank Account Test Bank Account 12302017 01022018

PBC


Job with Multiples Campaigns driven by .pbc Level Job ID PBC Unique ID CQT Database ID Package ID Barcode Wasted or Shortage Piece indicator …

C12345671 73540211 X5763890 200038 0100180000504800000124022999501

C12345671 73540212 X5763891 200038 0100180000504800000124022999502

C12345671 73540213 X5763892 200038 0100180000504800000124022999503

C12345671 73540221 X5763900 200039 0100180000504800000124022999511

C12345671 73540222 X5763901 200039 0100180000504800000124022999512

C12345671 73540223 X5763902 200039 0100180000504800000124022999513

C12345671 73540230 X5763909 200040 0100180000504800000124022999520

C12345671 73540231 X5763910 200040 0100180000504800000124022999521

C12345671 73540232 X5763911 200040 0100180000504800000124022999522

C12345671 73540233 X5763912 200040 0100180000504800000124022999523

Table 10: Job with Multiple Campaigns Driven by RMR Linkage with Pieces in PBC

6.4 Combined Presentation The Combined Presentation applies only to Letter mailings. This scenario accommodates multiple address lists through presort or post-presort software, which can generate multiple component records/versions. The creation of the campaign from a Combined Mail.dat file includes the following presort data configuration and processes:

Multiple jobs, each with their own Campaign data, are merged together to create one job.

Campaign records are included in the RMS and RMR with the following information: o Campaign Title o Campaign Code o Campaign Start and End Dates o Representative Image (optional for Letter mailpieces and required for Flats) o Ride-along Image o Target URL

Campaigns are tied to physical pieces with IMb barcodes. These pieces are located in PDR or PBC records. The campaign data in RMS-RMR is provided at the CPT, PDR, or PBC piece records level. In the case that campaign data is provided at the CPT level, then campaigns are tied to pieces in PDR or PBC piece records by using the relationship from CPT to PDR or CPT to PBC.


Campaign data from PostalOne! is transmitted to Informed Delivery when mail containers are marked with a Ready-to-Pay status (CSM Container Status is “R”). Informed Delivery processes the campaign data and creates unique campaign(s) based on the campaign data from PostalOne!.

Upon receipt of the image data from MPE, the Informed Delivery application matches the IMb barcodes and applies the associated campaign treatment to the pieces for the consumer view.

6.4.1 Sample Data The table below represents sample data and the relationship between PBC, RMR, and RMS files. The table also depicts key fields for Conventional/Single Presentation at the PBC level.

.pbc Scenario - Job with Multiples Campaigns driven by .pbc Level


C12345671 73540212 Test TM Card 99995 L P 2 LT

C12345671 73540213 Test S Insurance 99995 L P 2 LT

C12345671 73540214 Test Bank Account 99995 L P 2 LT





Figure 7: Combined Presentation Process


.pbc Scenario - Job with Multiples Campaigns driven by .pbc Level C12345671 73540212 B B http://www.AcmeCarSales.com/ P2763456

















…





C12345671 73540211 X5763890 200038 0100180000504800000124022999501

C12345671 73540212 X5763891 200038 0100180000504800000124022999502

C12345671 73540213 X5763892 200038 0100180000504800000124022999503

C12345671 73540221 X5763900 200039 0100180000504800000124022999511

C12345671 73540222 X5763901 200039 0100180000504800000124022999512

C12345671 73540223 X5763902 200039 0100180000504800000124022999513

C12345671 73540231 X5763910 200040 0100180000504800000124022999521

C12345671 73540232 X5763911 200040 0100180000504800000124022999522

C12345671 73540233 X5763912 200040 0100180000504800000124022999523

Table 11: Flats Job with Multiple Campaigns Driven by RMR Linkage with Pieces in PBC

6.5 Comingle Presentation The Comingle Presentation applies predominately to Letter mailings, but may also be used for Flats. This scenario applies to hardware-based sortation merging of multiple mail streams that generate multiple component records or versions of the Mail.dat file.

Mail owners with multiple mailpiece versions (CPT) with a specific campaign in the combined Comingled Mail.dat must keep the CPT-to-RMR and Piece (PDR/PBC) relationships intact. o Original linkages should be kept in the RMR to include the Campaign Start Date and End

Date and supplemental content. o If provided in the CSM file, Campaign Start Date and End Date will override those provided

in the RMR. o Campaigns are tied to physical pieces in PDR or PBC records with actual IMbs.

Upon receipt of the eDocs data from PostalOne! and image data from MPE, the Informed Delivery application matches the campaign information with the eDocs data.

6.5.1 Sample Data The table below represents sample data and the relationship between CPT, RMR, and RMS tables, and key fields.

.pdr Scenario – Comingle Job with Multiples Campaigns driven by .pdr Level


B12349800 144411145 Cleaner House 10% 99995 L P 2 LT

B12349800 144411146 Garage Repair Installation 99995 L P 2 LT

B12349800 144411147 Roof Replacement 50% Off 99995 L P 2 LT



Figure 8: Comingle Sortation Process


.pdr Scenario – Comingle Job with Multiples Campaigns driven by .pdr Level







B12349800 144411150 P B http://www.GaragerACME.com Z1234568





B12349800 144411156 P A http://www.RoofRemt.com/img.jpg Z1234569








…


B12349800 Z1234568 Garage Repair Installation Garage Repair Installation 20152017 20202017

B12349800 Z1234569 Roof Replacement 50% Off Roof Replacement 20082017 20132017

PDR Job ID CQT Database

ID Package ID Piece ID Piece Barcode IM Barcode

…

B12349800 144411145 A1234567 144411145 10234300343 0100191600504800000124022999801

B12349800 144411146 A1234567 144411146 10234300343 0100191600504800000124022999802

B12349800 144411145 A1234567 144411145 10234300343 0100191600504800000124022999803

B12349800 144411146 A1234567 144411146 10234300343 0100191600504800000124022999804

B12349800 144411147 A1234567 144411147 10234300343 0100191600504800000124022999805

B12349800 144411150 A1234567 144411150 10234300343 0100191600504800000124022999808

B12349800 144411151 A1234567 144411151 10234300343 0100191600504800000124022999809

B12349800 144411152 A1234567 144411152 10234300343 0100191600504800000124022999810

B12349800 144411153 A1234567 144411153 10234300343 0100191600504800000124022999811

B12349800 144411156 A1234567 144411156 10234300343 0100191600504800000124022999814

B12349800 144411157 A1234567 144411157 10234300343 0100191600504800000124022999815

B12349800 144411158 A1234567 144411158 10234300343 0100191600504800000124022999816

Table 12: Comingle Job with Multiple Campaigns Driven by RMR Linkage with Pieces in PDR

6.6 Comail Presentation The Comail Presentation applies only to Flats. This scenario accommodates multiple address lists and versions combined through presort or post-presort software, which generates multiple component records/versions.

The creation of the campaign from a Comail Mail.dat file, which applies to multiple flat publications, includes the following presort data configuration and processes:

Multiple jobs for Flat mailings, each its own publication with its own Campaign data, are merged together to create one job. The different Flat publications are re-sorted together.

Campaign records are included in the RMS and RMR with the following information:

o Campaign Title o Campaign Code o Campaign Start and End Dates o Representative Image (optional for Letter mailpieces

and required for Flats) o Ride-along Image o Target URL

Campaigns are tied to physical pieces through the IMb. These pieces are located in PDR or PBC records. The campaign data in RMS-RMR is provided at the CPT, PDR, or PBC piece records level. In the case that campaign data is provided at the CPT level, then campaigns are tied to pieces in PDR or PBC piece records by using the relationship from CPT to PDR or CPT or PBC.

Campaign Start and End Dates provided in a CSM file will override Start and End Dates provided in the RMS file.

Figure 9: Comail Presentation Flats Process





.pdr Scenario - Comail Job with Multiples Campaigns driven by .pdr Level


B12349800 144411145 Cleaner House 10% 99995 L P 2 FL

B12349800 144411146 Garage Repair Installation 99995 L P 2 FL

B12349800 144411147 Roof Replacement 50% Off 99995 L P 2 FL


B12349800 32858902 P A http://www.Cleanerhouse.com/1img.jpg Z1234567


B12349800 32858902 P C http://www.Cleanerhouse.com/2img.jpg Z1234567









B12349800 32858907 P C http://www.GarageACME.com/1034.jpg Z1234568




A http://www.GarageACME.com/1014.jpg Z1234568



B12349800 32858912 P A http://www.RoofRemt.com/1img.jpg Z1234569


B12349800 32858912 P C http://www.RoofRemt.com/2img.jpg Z1234569









…





B12349800 32858902 A1234567 144411145 10234300343 0100191600504800000124022999801

B12349800 32858903 A1234567 144411146 10234300343 0100191600504800000124022999802

B12349800 32858904 A1234567 144411145 10234300343 0100191600504800000124022999803

B12349800 32858907 A1234567 144411148 10234300343 0100191600504800000124022999806

B12349800 32858908 A1234567 144411149 10234300343 0100191600504800000124022999807

B12349800 32858909 A1234567 144411150 10234300343 0100191600504800000124022999808

B12349800 32858912 A1234567 144411153 10234300343 0100191600504800000124022999811

B12349800 32858913 A1234567 144411154 10234300343 0100191600504800000124022999812

B12349800 32858914 A1234567 144411155 10234300343 0100191600504800000124022999813

Table 13: Comail Job with Multiple Campaigns Driven by RMR Linkage with Pieces in PDR

6.7 Copal Presentation The Copal Presentation typically applies to Letter mailings, but can also be applied to Flats. In this scenario, mailers may submit multiple trays into the mail stream. The Copal Presentation combines all the mailpieces in the consolidators’ pallets, which allows for increased mail volume and/or drop-ship discounts. The creation of the campaign from a Copal Mail.dat file includes the following presort data configuration and processes:


Figure 10: Copal Presentation Process

Multiple original jobs are submitted followed by a Consolidator job. The Consolidator job identifies the final pallet and its contents.

Campaign records are included in the RMS and RMR with the following information: o Campaign Title o Campaign Code o Campaign Start and End Dates o Representative Image (optional for Letter mailpieces and required for Flats) o Ride-along Image o Target URL

Campaigns are tied to physical pieces with IMb barcodes. These pieces are located in PDR or PBC records. The campaign data in RMS-RMR is provided at the CPT, PDR, or PBC piece records level. In the case that campaign data is provided at the CPT level, then campaigns are tied to pieces in PDR or PBC piece records by using the relationship from CPT to PDR or CPT to PBC.




USPS ensures the relationship integrity of Mail.dat files will be intact between records. In each scenario described above, USPS will not intertwine presort data. The files that are edited are the RMS and RMR files.


.pbc Scenario - Flats Job with Multiples Campaigns driven by .pbc Level


C12345671 73540212 Test TM Card 99995 L P 3 FL

C12345671 73540213 Test S Insurance 99995 L P 3 FL

C12345671 73540214 Test Bank Account 99995 L P 3 FL


C12345671 73540211 B A http://www.AcmeCarSales.com/0img.jpg P2763456


C12345671 73540211 B C http://www.AcmeCarSales.com/1img.jpg P2763456

C12345671 73540212 B A http://www.AcmeCarSales.com/1img.jpg P2763456


C12345671 73540212 B C http://www.AcmeCarSales.com/1img.jpg P2763456



C12345671 73540221 B C http://www.TestSF.com/1243.jpg P2763457







C12345671 73540231 B A http://www.TestTM.com/ccr.jpg P2763458


C12345671 73540231 B C http://www.TestTM.com/creditcard.jpg P2763458






.pbc Scenario - Flats Job with Multiples Campaigns driven by .pbc Level C12345671 73540233 B B http://www.TestTM.com P2763458




…





C12345671 73540211 X5763890 200038 0100180000504800000124022999501

C12345671 73540212 X5763891 200038 0100180000504800000124022999502

C12345671 73540221 X5763900 200039 0100180000504800000124022999511

C12345671 73540222 X5763901 200039 0100180000504800000124022999512

C12345671 73540223 X5763902 200039 0100180000504800000124022999513

C12345671 73540231 X5763910 200040 0100180000504800000124022999521

C12345671 73540232 X5763911 200040 0100180000504800000124022999522

C12345671 73540233 X5763912 200040 0100180000504800000124022999523

Table 14: Flats Job with Multiple Campaigns Driven by RMR Linkage with Pieces in PBC

The table below represents sample data and the relationship between PDR, RMR, and RMS tables, and key fields.

Note: Mail.dat allows either a PBC or PDR on a job.

.pdr Scenario - Flats Job with Multiples Campaigns driven by .pdr Level


B12349800 144411145 Cleaner House 10% 99995 L P 3 FL

B12349800 144411146 Garage Repair Installation 99995 L P 3 FL

B12349800 144411147 Roof Replacement 50% Off 99995 L P 3 FL


B12349800 32858902 P A http://www.Cleanerouse.com/1img.jpg Z1234567

B12349800 32858902 P B http://www.Cleanerouse.com Z1234567

B12349800 32858902 P C http://www.Cleanerouse.com/img.jpg Z1234567
















B12349800 32858912 P A http://www.RoofRmt.com/raimg.jpb Z1234569


B12349800 32858912 P C http://www.RoofRemt.com/img.jpg Z1234569









…




PDR Job ID CQT Database

ID Package ID Piece ID Piece Barcode IM Barcode

…

B12349800 32858902 A1234567 144411145 10234300343 0100191600504800000124022999801

B12349800 32858903 A1234567 144411146 10234300343 0100191600504800000124022999802

B12349800 32858904 A1234567 144411145 10234300343 0100191600504800000124022999803

B12349800 32858907 A1234567 144411148 10234300343 0100191600504800000124022999806

B12349800 32858908 A1234567 144411149 10234300343 0100191600504800000124022999807

B12349800 32858909 A1234567 144411150 10234300343 0100191600504800000124022999808

B12349800 32858912 A1234567 144411153 10234300343 0100191600504800000124022999811

B12349800 32858913 A1234567 144411154 10234300343 0100191600504800000124022999812

B12349800 32858914 A1234567 144411155 10234300343 0100191600504800000124022999813

Table 15: Flats Job with Multiple Campaigns Driven by RMR Linkage with Pieces in PDR


7 Mail.dat Campaigns without eDoc Presort Data USPS developed Mail.dat without eDoc Presort to enhance mailers’ experiences. This functionality can benefit mail owners with their own marketing departments and MSPs. This section explains the features that allow an Informed Delivery campaign to be submitted to PostalOne! via Mail.dat without any eDoc or presort data embedded. Mail.dat version 17-2 uses HDR, RMS, and RMB files to generate an Informed Delivery job. The HDR, RMS, and RMB files provide campaign summary data from the PostalOne! system, which sends this data to the Informed Delivery application. The HDR file is the highest file of the single submission. The Job ID is the key field contained in the Header File. The Presentation Category field value must be I = Informed Delivery. The HDR contains:

Header of the job

Job ID

Record counts of all other records

Record statuses of all other records The RMS file aggregates metrics and provides a reference for the campaign within mailer systems. The fields in the RMS include:

Campaign Title

Campaign Code

Brand Display Name

Campaign Start and End Dates The RMB file, when combined with the HDR and RMS files, provides campaign summary data. This event ties the RMB barcodes directly to USPS. The fields in the RMB include:

Ride-along Image

Target URL

Representative Image (optional for Letter mailpieces and required for Flats)

IMb

7.1 Mail.dat Submissions Exclusively for Informed Delivery Informed Delivery campaigns may be submitted using the latest Mail.dat client user interface and batch processing modes. The following elements are required:

CRID (must be populated in the HDR eDoc Sender CRID)

Customer Registration username

Password

USPS requires mailers to submit the HDR, RMS, and RMB.

7.2 Consumer Display: Mapping Mail.dat to Customer View

Informed Delivery will continue to support the incorporation of eDoc campaign files (e.g., RMS, RMR, and RMB). The following data elements are

Figure 11: Mail.dat Exclusive Submission


used in the consumer email messages and dashboard (see Figure 12).

Figure 12: Informed Delivery Consumer View with eDoc Information

7.3 Sample Data The RMB file scenario provides USPS with campaign information independent of the presort data, allowing mailers to submit their Informed Delivery campaigns once the IMb barcodes are available. This flexible process makes it easier to manage campaign submissions outside of the more complex presort processes.

Note: PostalOne! does not currently support RMB linkage to the Original Presort Job. While the Original Job ID data element exists in the RMB, the RMB linkage field is ignored in this instance.

.RMB Scenario - Letters Job with Multiples Campaigns driven by Barcode Ranges

HDR Job ID Presentation Category

B12349800 I

RMB Job ID RMS ID Barcode RMB Content Type RMB Value Original job ID – optional

B12349800 Z1234567 0100180000504800000124022999501 A http://www.Cleanerouse.com/img.jpg B12349801 B12349800 Z1234567 0100180000504800000124022999501 B http://www.Cleanerouse.com B12349801 B12349800 Z1234567 0100180000504800000124022999502 A http://www.Cleanerouse.com/img.jpg B12349801 B12349800 Z1234567 0100180000504800000124022999502 B http://www.Cleanerouse.com B12349801 B12349800 Z1234567 0100180000504800000124022999503 A http://www.Cleanerouse.com/img.jpg B12349801 B12349800 Z1234567 0100180000504800000124022999503 B http://www.Cleanerouse.com B12349801 B12349800 Z1234568 0100180000504800000124022999510 A http://www.GarageACME.com/1034.jpg B12349801 B12349800 Z1234568 0100180000504800000124022999510 B http://www.GarageACME.com B12349801 B12349800 Z1234568 0100180000504800000124022999511 A http://www.GarageACME.com/1034.jpg B12349801 B12349800 Z1234568 0100180000504800000124022999511 B http://www.GarageACME.com B12349801 B12349800 Z1234568 0100180000504800000124022999512 A http://www.GarageACME.com/1034.jpg B12349801 B12349800 Z1234568 0100180000504800000124022999512 B http://www.GarageACME.com B12349801 B12349800 Z1234569 0100180000504800000124022999521 A http://www.RoofRemt.com/img.jpg B12349801 B12349800 Z1234569 0100180000504800000124022999521 B http://www.RoofRmt.com B12349801 B12349800 Z1234569 0100180000504800000124022999522 A http://www.RoofRemt.com/img.jpg B12349801 B12349800 Z1234569 0100180000504800000124022999522 B http://www.RoofRmt.com B12349801 B12349800 Z1234569 0100180000504800000124022999523 A http://www.RoofRemt.com/img.jpg B12349801 B12349800 Z1234569 0100180000504800000124022999523 B http://www.RoofRmt.com B12349801






Table 16: Letters Job with Multiple Campaigns Driven by Barcode Ranges


7.4 Mail.dat Version 17-2 File Descriptions for Non-Presort Campaign Informed Delivery Scenario

The table below describes the Mail.dat file naming convention and the corresponding Idealliance and USPS standards for the Informed Delivery application. File Definition Header File name .hdr/HDR

The HDR file introduces the entire Mail.dat. It identifies who created the file, the Idealliance standard version used (ensuring compatibility with other users), and when the file was created. Most importantly, it identifies the total file record count for each file type. The Header also provides information such as the type of presort software used and the history of who has touched the Mail.dat file. The first indication that a file is incomplete is if the Header record displays a different number of records than received; an incomplete file is invalid. RMS Record Count – Required data field added to transmit/store the count for the file RMS

Record.

RMS Status – Required data field added to transmit/store the status for the RMS Record.

RMR Record Count – Required data field added to transmit/store the count for the RMR Record.

RMR Status – Required data field added to transmit/store the status for the RMR Record.

User Option Field – Note that character spaces from the User Option Field were repurposed to support the addition of the data fields enumerated directly above.

“Mail.dat presentation category” is one of the Key fields in HDR for Informed Delivery. Informed Delivery campaigns with Presort data can use values such as P, M, N, C, E, and T. Informed Delivery campaigns without Presort data must use the value of “I”.

Referenceable Mail Summary File name .rms/RMS

The RMS file is used to provide campaign names and Start and End Dates, as well as link campaign information with the RMR record.

Job ID – Field to identify the Job ID. Foreign key refers to the Header record.

RMS ID – Key field to identify each unique RMS Record.

Campaign Title – Title of the Informed Delivery campaign. Displays internally on the USPS Informed Delivery Administrative console.

Campaign Code – The Campaign Code must be unique for every campaign. If the same campaign Code is used across multiple jobs, the Informed Delivery application will treat the jobs as the same campaign.

Campaign Serial Grouping – This field is used to identify if the IMbs can be grouped together under an IMb Serial Number range. This field is used to identify one of the two types of campaigns:

o Blank = IMbs not in continuous Serial Number range. This option should create single-piece campaigns. This option should be used when the campaigns are personalized and/or the IMbs are not in continuous Serial Number range. As of publication of this document, personalized campaigns are not available. At this time, the PostalOne! application ignores any information inputted in this field.

o C = IMbs in continuous Serial Number range with non-personalized campaigns.

Display Name – Display Name of the mail owner or brand that appears in consumers’ email notifications and Informed Delivery dashboard views.

Date Start – Start Date when the Referenceable Mail Content can be used.

Date End – End Date by when the Referenceable Mail Content can be used.

RMS Record Status – Used to denote the status of the record as O = Original, D = Delete, I = Insert, or U = Update.

Referenceable Mail Barcode File name .rmb/RMB

The RMB file is used to provide USPS with campaign information as a standalone, with no dependence on presort data.

Job ID: (Zero fill prior to numeric, if numeric only). See Header File’s Job ID definition.

RMS ID: Unique ID of the individual campaign.

Barcode: IMb for Informed Delivery.

RMB Content Type: Field to capture the type of RMB content. RMB content can either be a URL of a media image that is supported by browsers or a target URL that will be placed as a Hyperlink for the media/image. Details of the codes will be available in the USPS Technical Guide for Mail.dat.

o A = Content Type A: Ride-along Image URL (URL for the image source location. This image is displayed along with the mailpiece image).

o B = Content Type B: Ride-along Target URL (URL for marketing material/page for consumers).

o C = Content Type C: Replace Image URL (URL for the image source location. This image is displayed instead of the scanned mailpiece image).

o D = Content Type D: Replace Image target URL (This field is a placeholder for future


File Definition content which is currently not displayed in the Informed Delivery consumer-facing feature).

o O = Content Type O: Opt Out – Not supported by the Informed Delivery application.

Original Job ID: (Zero fill prior to numeric, if numeric only). Job ID provided in another mailing job.

Original User License Code: User License Code provided in another mailing job.

RMB Value: Value/Content URL for the Referenceable Mail media or target/Hypertext Reference (HREF) document (e.g., webpage or image/media driven by the RMB Content Type field).

RMB Template Code: In future use, USPS will provide multiple templates. o Possible values can be A through Z.

RMB Record Status: o O = Original o D = Delete o I = Insert o U = Update

Table 17: Mail.dat 17-2 File Names and Descriptions

8 Feature(s) Slated for Future Releases The following features are slated for PostalOne! and Informed Delivery releases:

Mailer Campaign Portal Visibility for Campaigns Submitted via PostalOne!: Display the status of campaigns submitted via PostalOne! on the Mailer Campaign Portal and provide access to reports.


9 Legal Terms A mailer who submits an Informed Delivery campaign using the PostalOne! system is subject to the following terms and conditions: CUSTOMER/SUBMITTER OBLIGATIONS REGARDING INTERACTIVE CONTENT AND IMAGES By submitting Content to USPS in connection with any Informed Delivery campaign, you agree to the terms and conditions specified below and to faithfully comply with all other rules, regulations, technical specifications and requirements for Informed Delivery campaigns. “Content” as used herein includes Ride-along images and links, Representative images, interactive links, and text or any other content that you provide to USPS by any means whatsoever (including but not limited to email, upload through PostalOne!, or otherwise), other than the physical mailpiece and any USPS-generated greyscale image thereof. Your Representations and Warranties You represent and warrant that you have all necessary third party rights, and hereby grant to USPS such rights, to use, display, publish, transmit, distribute, and make copies of the Content, and otherwise use it in your Informed Delivery campaign, without infringing any rights of any third party or violating any applicable laws, rules or regulations. This grant includes the rights covering the ordinary use to which recipients put the Content. The rights referred to in the foregoing include, without limitation, copyrights, trademark rights, rights of publicity (name and likeness rights) and any other rights necessary to use the Content. You further represent and warrant that the nature, appearance, and display of the Content is consistent with the mailability requirements of the Domestic Mail Manual. Eligible Content must not: (1) be defamatory, indecent or obscene; (2) depict violent or sexual material and/or material that would be harmful to minors; (3) violate any applicable law, statute, ordinance or regulation, or be legally actionable; (4) claim or create the impression, whether expressly or by implication, that the Postal Service endorses you or your product, service or offering; or (5) promote alcohol, tobacco, weapons, or gambling. You acknowledge and agree that USPS will not be involved in any way with the design of the Content. You agree to evaluate and bear all risks associated with the use of any Content. You are solely responsible for and assume all liability arising from use of the Content in or through or otherwise as a result of your Informed Delivery campaign. You agree that the fact that USPS reproduces, displays, or distributes the Content and/or otherwise uses it in the Informed Delivery campaign: (1) does not constitute approval or endorsement of the Content; (2) does not indicate that the Content complies with any or all applicable laws, including Postal law or regulations, or (3) does not constitute acceptance of any liability or risk arising from the Content. In the event that the Content contains an interactive link, you warrant and represent that any web page linked to directly from Informed Delivery, whether through an email or through the Informed Delivery interface, shall not take Informed Delivery users to a web page that could be confused by a reasonable person to be a Postal Service web page. Indemnity You agree to indemnify and hold the Postal Service and its Governors, officers, employees, agents, printers, contractors, vendors, and suppliers harmless against any and all expenses and losses of any kind (including attorneys’ fees and costs) incurred in connection with any claims of any kind arising out of breach of any of the above representations and warranties, and publication, transmission, display or distribution of the Content (including, without limitation, any claim of patent, trademark or copyright infringement, libel, defamation, breach of confidentiality, misappropriation of trade secret, invasion of the rights of privacy or publicity (including the right to control use of one’s name and likeness), false or


deceptive advertising or sales practices) or any material or products of your’ s to which third parties can link through the Content. Disclaimer THE PRODUCTS, SERVICES, WEBSITE, CONTENT AND/OR MATERIALS AVAILABLE THROUGH USPS ARE PROVIDED ON AN "AS IS" AND "AS AVAILABLE" BASIS AND WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED. USPS MAKES NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ARISING FROM A COURSE OF DEALING OR PERFORMANCE, NONINFRINFGEMENT, OR TRADE USAGE. USPS SHALL NOT BE LIABLE TO YOU OR ANY OTHER PERSON OR ENTITY FOR ANY LOSS, COST, DAMAGE OR EXPENSE, INCLUDING WITHOUT LIMITATION LOSS OF PROFITS, ARISING OUT OF OR IN CONNECTION WITH ANY CONTENT INCLUDED IN INFORMED DELIVERY, THE MANNER IN WHICH ANY CONTENT IS DISPLAYED OR DISTRIBUTED, THE FAILURE TO DISPLAY ANY CONTENT, OR ANY TECHNICAL MALFUNCTION, COMPUTER ERROR OR LOSS OF DATA OR OTHER INJURY, ARISING, DIRECTLY OR INDIRECTLY, FROM YOUR USE OF THE INFORMED DELIVERY FEATURE. SPECIFICALLY, AND WITHOUT LIMITING THE FOREGOING, USPS DOES NOT REPRESENT OR WARRANT THAT ANY CONTENT WILL BE DISPLAYED OR OTHERWISE TRANSMITTED OR DISSEMINATED THROUGH INFORMED DELIVERY WITHOUT INTERRUPTION OR ERROR. Limitation of Liability IN NO EVENT SHALL USPS BE LIABLE FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL OR EXEMPLARY DAMAGES, EVEN IF SUCH DAMAGES ARE FORSEEABLE, AND REGARDLESS OF WHETHER USPS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. YOUR SOLE AND EXCLUSIVE REMEDY FOR ANY CLAIM ARISING FROM OR RELATING TO YOUR PARTICIPATION IN AN INFORMED DELIVERY CAMPAIGN SHALL BE LIMITED TO A MAKE-GOOD PLACEMENT OF THE CONTENT AT A LATER TIME IN CONNECTION WITH A SUBSEQUENT MAILING.


APPENDIX – Mail.dat Specification Lists The following tables are taken from the Mail.dat version 17-2 specification list. The tables list each file, the fields, and the corresponding Idealliance descriptions. Referenceable Mail (.rmr) Record

Referenceable Mail Record (RMR)

Field Acceptable Values

Required Notes

Job ID Alphanumeric Required Must match Job ID of header.

RMR ID Alphanumeric Required Must correspond to a PBC Unique ID, Piece ID, or CPT ID when the RMR ID Type is B = PBC, P = PDR, or C = CPT, respectively.

RMR ID Type

P, B, C Required P = PDR, B = PBC, C = CPT.

RMS ID Alphanumeric RMS ID of the Referenceable Mail Summary record.

RMR Content Type

A, B, C, D, O Required Field to capture the type of RMR content. RMR content can either be a URL of a media image that is supported by browsers or a target URL that will be placed as a hyperlink for the media/image. The value of O is not currently supported.

CQT Database ID

Number Required for RMR ID type of PBC and PDR. Field must be blank for RMR ID type of Component.

Referenceable Mail Record Value

Alphanumeric Value/Content URL for the Referenceable Mail media or target/HREF document (could be a webpage, or image/media driven by the RMR Content Type field). The URL value must start with a lower case http:// or https://.

Start Date Marked with a dagger and not supported.

End Date Marked with a dagger and not supported.

RMR Template Code

A-Z A, B, C…to Z. A is only supported value.

RMR Record Status

O,D, I,U O = Original, D = Delete, I = Insert, U = Update.

Closing Character

# No characters are permitted after the closing character.

Referenceable Mail Summary (.rms) Record

Referenceable Mail Summary (RMS)

Field Acceptable Values

Required Notes

Job ID Alphanumeric Required Must match Job ID of header.

RMS ID Alphanumeric Required Unique ID of individual campaign.

Campaign Title

Alphanumeric Required.

Campaign Code


Campaign Serial Grouping

Alphanumeric Blank = IMbs not in continuous Serial Number range. This option should create single piece campaigns. This option should be used when: the campaigns are personalized and/or the IMbs are not in continuous Serial Number range. Currently, this field is ignored and the “C” field is implemented. C = IMbs in continuous Serial Number range with non-personalized campaigns.

Display Name


Date Start Date

Date End Date

RMS Record Status

O,D, I,U O = Original, D = Delete, I = Insert, U = Update.

Closing Character

# No characters are permitted after the closing character.


Referenceable Mail Barcode (.rmb) Record

Referenceable Mail Barcode (RMB)

Field Acceptable Values Required Notes

Job ID Alphanumeric Required Must match Job ID of header

RMS ID Alphanumeric Required Unique ID of individual campaign.

Barcode Alphanumeric Required IMb for Informed Delivery.

RMB Content Type A, B, C, D, O Required Field to capture the type of RMR content. RMR content can either be a URL of a media image that is supported by browsers or a target URL that will be placed as a hyperlink for the media/image.

Original Job ID Alphanumeric

Original User License Code Alphanumeric

RMB Value Alphanumeric Value/Content URL for the Referenceable Mail media or target/HREF document (could be a webpage, or image/media driven by the RMR Content Type field).

RMB Template Code A-Z

RMS Record Status O,D, I,U O = Original, D = Delete, I = Insert, U = Update.

Closing Character # No characters are permitted after the closing character.

For questions and comments related to this document please email USPS Informed Delivery eDoc Support Team at [email protected]


united states postal service technical specification · technical specification: mail.dat® for...

Documents