Popularity Reports Delivery
Set up delivery for twice-weekly popularity reports that rank tracks, artists, and products across the MassiveMusic global catalogue.
Popularity reports provide rankings and popularity scores across the full catalogue so you can support search, discovery, and recommendation workflows in your platform.
Before you start
Confirm:
- The team or system that will receive the reports
- Whether you want manual email downloads or automated S3 ingestion
- The AWS account, bucket, and region if using S3 delivery
- The account representative who will coordinate setup with MassiveMusic
Report Schedule & Content
- Frequency: Generated twice weekly.
- Scope: Contains everything in our global catalogue.
All delivery methods provide the same report contents and schema.
Note: The report includes all tracks, including some you may not have actively licensed. You can filter these out on your end using the standard track metadata you already receive.
Report format
Reports are delivered as JSON files. Track, artist, and product/release popularity reports are delivered as separate reports. The ranking fields stay the same across report types; the identifier field changes based on the report type.
// Track report item
{
"trackId": 261719145,
"searchRank": 80804803,
"searchModifier": 0.19
}
// Artist report item
{
"masterArtistId": 18217993,
"searchRank": 1871820,
"searchModifier": 0.11
}
// Product / release report item
{
"productId": 53041285,
"searchRank": 23110820,
"searchModifier": 0.22
}Data Schema
Each report contains one identifier field plus the same two ranking fields.
| Report type | Identifier field | Description |
|---|---|---|
| Track | trackId | The unique identifier for the track. |
| Artist | masterArtistId | The unique identifier for the master artist. |
| Product / release | productId | The unique identifier for the product or release. |
The ranking fields are the same for all report types:
| Field | Type | Description |
|---|---|---|
searchRank | Integer | The absolute ranking from 1 to n, where 1 is the most popular item in that report. |
searchModifier | Float | The popularity score (the same value returned in standard API search responses). |
If two items share the same searchModifier score, the searchRank dictates which item is absolute top in popularity.
Choose a delivery method
Review the options below and tell your account representative which delivery method you want to use.
| Method | Best for | Setup required |
|---|---|---|
| Email delivery | Manual downloads and lightweight review | Provide recipient email addresses |
| S3 delivery using IAM role | Automated ingestion for production pipelines | Create a cross-account IAM role |
| S3 delivery using IAM user credentials | Automated ingestion when IAM roles are not possible | Create restricted IAM user credentials |
Option 1: Email delivery
Use email delivery for manual review or lightweight integrations that do not need automated ingestion.
- How it works: Every time a report is generated, we will send an email to your designated team inbox.
- Download window: The email contains a pre-signed S3 download link valid for 7 days.
- Requirements: Just provide us with the email address(es) where the notifications should be sent.
Option 2: S3 delivery using IAM role
Use S3 delivery with an IAM role for automated ingestion. This is the recommended option for production pipelines.
We securely write the files directly to an Amazon S3 bucket owned by you using a cross-account IAM role.
- File Naming: All delivered objects are automatically timestamped, ensuring unique filenames for every delivery.
- Setup Requirements: You must create an IAM role on your side that trusts our AWS account and grants the required permissions.
To configure this, please create a role allowing our account principal to perform:
s3:PutObjects3:ListBucket(ors3:ListBucketMultipartUploads)s3:AbortMultipartUpload
Grant permissions only to the destination bucket or prefix used for popularity report delivery. s3:ListBucket applies to the bucket ARN, while s3:PutObject and s3:AbortMultipartUpload apply to object ARNs.
Information we need from you:
Bucket ARN: arn:aws:s3:::your-bucket-name
Bucket Region: e.g., us-east-1
Trusted IAM Role ARN: arn:aws:iam::your-account-id:role/your-role-name
(Please reach out to your account representative to receive our AWS Account Principal ID to establish the trust relationship).
Option 3: S3 delivery using IAM user credentials
If you prefer not to use cross-account IAM roles, we can authenticate using dedicated IAM user credentials that you provision for us.
- How it works: You provide us with a set of AWS access keys restricted entirely to the destination bucket path.
- Required Permissions: The credentials must allow
s3:PutObject,s3:ListBucket, ands3:AbortMultipartUploadfor the specified bucket/path.
If you use IAM user credentials, restrict the access keys to the destination bucket or prefix used for popularity report delivery. Do not provide credentials with broader AWS account access.
Information we need from you:
Bucket ARN: arn:aws:s3:::your-bucket-name
Bucket Region: e.g., us-east-1
AWS Access Key ID: XXXXXXXXXXXXXXXXXXXX
AWS Secret Access Key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
What to send MassiveMusic
To activate your popularity report delivery, please reply to your account manager with:
- Your preferred delivery method (Option 1, 2, or 3).
- The corresponding configuration details listed above.
What happens next
- You send your preferred delivery method and configuration details to your account manager.
- MassiveMusic configures the delivery pipeline.
- MassiveMusic confirms when setup is complete.
- The next scheduled report is delivered using your selected method.
Updated 6 days ago
