Power My Analytics allows Custom plan subscribers to export marketing data from Data Builder reports to destinations like BigQuery, MySQL, Azure SQL Database, PostgreSQL, Amazon S3, and FTP. This article is a central index of troubleshooting resources to help you resolve common issues with your data exports.

Plan Eligibility: Data exports are exclusively available on the Custom plan. If you are on a Free, Business, or Pro plan and would like to use data exports, please contact our sales team to learn more about upgrading.

Getting Started with Data Exports

If you are new to data exports or need help setting up your export configuration, start with these guides:

1. How to Use Data Exports – Overview of PMA's export feature, plan eligibility, and how to set up and schedule exports from Data Builder
   
2. Data Builder Guide – How to create the Data Builder reports that power your exports

Troubleshooting BigQuery Exports

If you are experiencing errors or issues with your BigQuery exports, start here:

1. How to Export to BigQuery – Setup guide for connecting your BigQuery dataset and scheduling exports
   
2. Troubleshooting BigQuery – How to view and interpret your BigQuery export logs
   
3. BigQuery Export Limitations – Common export size limits, timeout errors, "Failed to Fetch" errors, and hung exports
   
4. BigQuery Error: Billing Has Not Been Enabled for This Project – Resolve billing errors caused by free-tier BigQuery plans
   
5. BigQuery Error: Code 403; Message: Access Denied – Resolve free-tier streaming insert restrictions and dataset permission issues
   
6. BigQuery Error: Could Not Handle the Request, Error Code 500 or 502 – Resolve errors caused by exports exceeding BigQuery row limits
   
7. Error: Missing BigQuery Scopes – Resolve insufficient permissions when selecting a Google account as a BigQuery destination
   
8. Error: Exporting report ‘[report name]’, the owner of the report has left the organization – Resolve errors when a report owner is no longer part of your hub
   

Troubleshooting SQL Database Exports (MySQL, PostgreSQL, Azure SQL)

If you are experiencing errors or issues with your SQL database exports, start here:

1. How to Export to MySQL – Setup guide for connecting your MySQL database and scheduling exports
   
2. How to Export to PostgreSQL – Setup guide for connecting your PostgreSQL database and scheduling exports
   
3. How to Export to Azure SQL Database – Setup guide for connecting your Azure SQL database and scheduling exports
   
4. How to Use the SQL Connector – Guide for using PMA's SQL connector to connect to MSSQL or MySQL servers
   
5. SQL Error: Exporting report ‘[report name]’, Incorrect string value – Resolve character set incompatibility errors by updating your MySQL server to utf8mb4
   

General Export Troubleshooting Tips

If you are unable to find a solution in the destination-specific sections above, try these general troubleshooting steps:

1. Check your export logs. Most export destinations provide a View Logs option in your hub under Exports. Review the log entries for error messages that can help you identify the issue.
2. Verify your Data Builder report. Make sure the report you are exporting contains the required fields (such as a date field for BigQuery) and does not exceed row limits for your destination.
3. Confirm your destination credentials. Double-check that your connection credentials (account URL, database name, access keys, etc.) are correct and that the destination service is accessible.
4. Check permissions. Ensure the account you are using to connect to your destination has the required write and access permissions.
5. Review plan eligibility. Data exports require a Custom plan that includes exports. If you recently changed plans, confirm that your current plan still includes this feature.

If you still need help after reviewing these articles, please contact our support team for assistance.