Skip to main content
The correlation process lets you compare entitlement data held in your systems with the corresponding entitlement data held by DVM. Use correlation reports to identify matching records, records that exist in only one dataset, and records where key entitlement values differ. Correlation identifies the differences; use reconciliation to investigate and correct them.

​
Correlation types

DVM supports three correlation types.
An entitlement appears only once in a correlation file, using the latest available data, even if it changed multiple times during the correlation period.

​
Send correlation data to DVM

Upload your correlation file to the Amazon S3 bucket provided for DVM correlation during onboarding. Correlation processing starts when the file arrives and normally completes within minutes. Supported correlation periods are: Correlation is processed by partner. Provide one file for each counterpart partner and correlation period required.

​
Input location

Upload files to:
For resellers, {partner} is the merchantAccountKey used when creating an entitlement. For content providers, {partner} is the resellerId provided in the create entitlement request.

​
File naming

Use:
Dates use YYYYMMDD format. Examples: Files must use RFC 4180 CSV format and UTF-8 encoding. Use UTC for timestamps and RFC 3339 date-time values.

​
How correlation works

DVM validates and normalizes the file, then compares the supplied entitlement data with the corresponding DVM data. The fields used for correlation depend on whether you are a reseller or content provider.

Reseller correlation file format

Required fields, matching rules, and output columns for reseller correlation.

Content provider correlation file format

Required fields, matching rules, and output columns for content provider correlation.

​
Correlation results

Each output record includes:
  • CorrelationResult — the overall result
  • CorrelationResultReason — the reason for a mismatch, where applicable
  • The values supplied in your file
  • The corresponding values held by DVM
Possible results are: Typical mismatch reasons include:
  • Missing entitlement in DVM
  • Extra entitlement in DVM
  • CustomerIdentifier is different
  • ProductKey is different
  • Status is different
  • Multiple differences detected

​
Output files

By default, DVM generates four output files for each input file and publishes them to:
A single consolidated output file can also be enabled:

​
Output configuration

DVM correlation output can be configured to suit the agreed partner setup. Configuration is agreed during onboarding and can be updated through Bango Support.

​
Next step

Correlation tells you where the datasets differ. Use Reconciliation to investigate those differences and correct the relevant data.