In podcasting today, audiences are everywhere. You can find them listening on Apple, Rumble and Spotify, watching on YouTube, and increasingly streaming video directly on Spotify.
Why Set Up Spotify Integration?
If your show is on Spotify, integrating your Megaphone data with Podscribe gives you a more complete picture of performance. By enabling this integration, publishers unlock cross-platform visibility within the Podscribe dashboard. This allows you to model campaign performance more accurately, include Spotify views in ranker totals, and close a major blind spot in podcast analytics. Learn more.
Spotify Integration Requirements
To enable Podscribe to ingest your Spotify (Megaphone) data, please follow these steps:
- Set Up a Dedicated S3 Bucket: You will need to create a dedicated Amazon S3 bucket specifically for Megaphone export data. This should not be a shared or repurposed bucket.
- Grant Access to Podscribe: After Spotify approves the export, please share S3 access credentials with us securely. We use 1Password vaults to ensure credentials are shared and stored safely.
- Submit an Export Request to Spotify: Once the S3 bucket is configured, submit a request to Spotify to enable the export. This request must include the appropriate access permissions for the bucket. Spotify will need 1 - 2 weeks to setup the export
Note: If you need access to your data before the export is fully set up, Spotify is preparing documentation to enable read-only access through Spotify for Creators. This provides a way to view your data while the export setup is in progress.
How to Set Up an S3 Bucket on AWS
- Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.
- In the navigation bar on the top of the page, choose the name of the currently displayed AWS Region. Next, choose the Region in which you want to create a bucket.
- In the left navigation pane, choose General purpose buckets.
- Choose Create bucket. The Create bucket page opens.
- Configure Bucket Settings
- Block Public Access: Leave this enabled for security, unless public access is required.
- Leave other settings as-is unless instructed otherwise.
- Set Permissions
- AWS recommends keeping public access blocked.
- You can later configure access using IAM policies or share credentials for read access (e.g., for Podscribe).
- Create the Bucket
- Click “Create bucket” to finalize.
You've now created a bucket in Amazon S3! For more help on creating an S3 bucket, please check out the official AWS S3 documentation.
Setting Up S3 Live Replication for Spotify Data
To ensure your data is securely and continuously replicated, we’ll configure S3 Live Replication between your source bucket and Podscribe’s destination bucket.
When the source and destination buckets are owned by different AWS accounts, both sides must configure permissions to allow replication. This includes adding a bucket policy on the destination bucket to grant the source account permission to perform replication actions.
1. Exchange AWS Account Details
To begin, please send the following information to adops@podscribe.com:
- Your S3 bucket name
- Your AWS Account ID
Podscribe’s details for replication setup:
- Podscribe Account ID:
484618524793
- Destination Bucket ARN:
arn:aws:s3:::podscribe-qcode
2. Create a Role for Cross-Account Replication
Create an IAM role in your AWS account to allow replication into the Podscribe destination bucket.
Refer to the example policy in the AWS documentation addendum for cross-account replication.
3. Share the Role ARN with Podscribe
Once the IAM role has been created, please share the Role ARN with us.
We’ll use this information to update the replication policy on our destination bucket to allow incoming replication from your source bucket.
4. Configure the Replication Rule
After Podscribe confirms the destination bucket policy has been updated, set up the replication rule in your source bucket according to the example in the AWS documentation.
Once configured, data from your export bucket will automatically replicate to Podscribe’s destination bucket.
For any other questions, please contact us at adops@podscribe.com.
Powered by