Sample Message to Partners after Inbound Processing

Whenever an inbound Server-to-Server file is processed, a receipt is sent via email to partner solutions and, if configured, to the partner.

The following example is a sample email message. The table below the message describes the various lines in the message.

From: s2s-delivery-receipt-demdex@demdex.com[s2s-delivery-receipt-demdex@demdex.com]

Subject: SFTP Server-To-Server Processing Result:

Dear Adobe Partner: (ID:7)

We have received your SFTP file delivery.

File name:

s3n://<bucket_name>/2013-05-17/ftp_dpm_7_901_1368806402.sync

s3n://<bucket_name>/2013-05-16/ftp_dpm_7_901_1368655202.sync

s3n://<bucket_name>/2013-05-17/ftp_dpm_7_901_1368784804.sync

s3n://<bucket_name>/2013-05-17/ftp_dpm_7_901_1368806403.sync

s3n://<bucket_name>/2013-05-17/ftp_dpm_7_901_1368784802.sync

s3n://<bucket_name>/2013-05-17/ftp_dpm_7_901_1368784803.sync

s3n://<bucket_name>/2013-05-17/ftp_dpm_7_901_1368806404.sync

Records received: 40669900

Invalid lines: 7

Invalid UUIDs: 112

Failed UUID lookup: 0

Records without traits: 26730823

Records processed: 40669900

Succeeded: 13938958

User without new traits: 26730823

Total signals: 918878926

Total unused signals: 660348376

Total realized traits: 258086908

Total new traits: 258086908

Total removed traits: 0

Total skipped duplicated users: 0

Job start time: 2013-05-17 18:07:49

Job end time: 2013-05-17 18:45:02

The following table contains rows corresponding to lines in the received email message.

Line Description
File name

List of all inbound files that Adobe received for this partner that were processed together. In the previous sample email message, the partner ID is 7 and the data owner ID is 901.

The tail number (1,2,3...) is the split number added either by the customer or by the inbound distributor.

Records received

Total number of records Adobe received across all files. In most cases, this should be the total number of lines in inbound files.

Invalid lines

Number of lines that did not match the expected format. These lines were not recognizable by the inbound job.

Invalid UUIDs

Number of audience management UUIDs that did not match the expected 38-digit format. Or the audience management UUIDs are not numbers.

Failed UUID lookup:

Total number of users for whom audience management failed to find a matching UUID. These files have not been ID synced, so audience management cannot look up the UUID.

Records without traits

Number of records where none of the signals on the line maps to an audience management trait.

Records processed

Total number of records audience management processed. In most cases, this number should be the same as "Records received."

Succeeded

Number of records resulting in data to be loaded into the system = records processed - invalid lines - invalid UUIDs - failed UUID lookup - records without traits.

User without new traits

For full syncs only, number of users that had exactly the same traits as they did after the last job. These users are not processed.

Total signals

Total number of signals for all users across all inbound files (total number of key/value pairs in the records processed).

Total unused signals

Total number of unused signal for all users across all inbound files (key/value pairs that did not map to audience management traits). In most cases, this means that audience management does not have rules defined for the signal.

Total realized traits

Number of audience management traits for all users across all inbound files based on the signals.

Total new traits

Total number of audience management traits minus (for full syncs) the number of traits realized in a previous inbound job. Only the new traits are passed to downstream processing.

Total removed traits

Total number of removed traits for all users across all inbound files. For full syncs, this happens if the user had the trait in a previous run but not in the current run.

Total skipped duplicated users

This is the total number of users that inbound job skipped to process because there were no new traits for them.

For full syncs, if a user has records with two different timestamps, only the newer record is used and the older one is skipped.

Job start time The time the inbound job starts.
Job end time The time the inbound job ends.