Bango performs similar record correlation processes with resellers who offer your products and services to customers through Bango Resale.
Unless otherwise agreed, the Bango data is considered the source of truth.
Supplying correlation data to Bango
To supply correlation data to Bango, you must upload it to your reporting Amazon S3 bucket provided by Bango by 04:00 UTC on the day after the end of the reporting period. All times should be in UTC. The files must be RFC 4180 CSV format, in a single file for each correlation period and uploaded to a dedicated input folder broken down by reseller. The naming convention for the reseller must match the resellerKey Bango use for the reseller. E.g. s3://merchant_identifier/CorrelationReports/[Reseller]/Input/ File name and examples
Bango will provide the merchant the following information to access their specific S3 storage area:
This information will be provided by our Bango support team as part of the provisioning process.
Examples of accessing data stored in Amazon S3 are:
Data comparison results
When comparing the data you supply to the data in the Bango Platform, Bango checks the following: ExternalEntitlementId also known as the MerchantEntitlementIdProductKeyStatusRecord correlation report input format
The data you provide to Bango must be in the following format:Record correlation report output files
Bango will provide four output files for each correlation execution in an output folder. The naming convention for the OTT service provider must match the merchantAccountKey value passed in the create entitlement. E.g. s3://merchant_identifier/CorrelationReports/[OTTServiceProvider1]/Output/Record correlation report output results
Bango recommends that merchants resolve any discrepancies identified by contacting Bango Support.
Here’s an example of a matched correlation report:

