What Fields Are Available In PMA's Connectors?
Every Power My Analytics connector includes a set of PMA metadata fields alongside your platform's own metrics and dimensions. This article explains what each one means, and why the cached data dates can read newer than your most recent row of data.
You can find the complete list of fields available for each connector in the Schema Explorer. Please see How to Use Schema Explorer.
PMA Metadata Fields
Alongside the metrics and dimensions that come from your source platform, every connector schema includes a small set of PMA metadata fields. These describe your data source, your report, or your subscription rather than your marketing performance, and they appear no matter which platform you are reporting.
You will see them in Schema Explorer and in the field picker when you build a data table in Data Builder.
| Field | What it tells you |
| PMA Minimum Cached Data Date | The earliest date covered by the data Power My Analytics has cached behind your report. |
| PMA Maximum Cached Data Date | The most recent date covered by the data Power My Analytics has cached behind your report. |
| Data Freshness | When Power My Analytics last collected data for this data source. This is a separate field from the cached data dates. |
| PMA Is Interpolated? | Whether lifetime values in your report may be interpolated (estimated between known data points). |
| Data Source | The platform your data came from, such as Facebook Ads or Shopify. Useful for labeling reports that combine several sources. |
| Data Source Logo | The platform's logo, for use in report headers and multi-source reports. |
| Data Platform | The platform grouping your data source belongs to. |
| PMA Subscription ID | Your subscription identifier. See Where Can I Find My Subscription ID? |
| PMA Trial Status | Whether your hub is currently on a free trial. |
| PMA Payment URL | A direct link to the billing section of your hub. |
| Function Execution ID | An internal reference that our support team can use when investigating a specific report request. |
The Cached Data Dates Are Not Row Dates
PMA Minimum Cached Data Date and PMA Maximum Cached Data Date describe the span of cached data behind your report. They are returned as a single pair of values stamped identically onto every row, so they are not the date of the row they sit next to.
This matters most on connectors whose platform publishes data on a delay. On those connectors, PMA Maximum Cached Data Date will normally read newer than the most recent date in your own data rows, and that gap is expected. For example, an Amazon Vendor Central report can show PMA Maximum Cached Data Date as September 17 while the newest Sales Report row ends on September 13, because Amazon had not yet published the days in between.
A gap between PMA Maximum Cached Data Date and your newest row of data does not mean data is missing. To see what a normal delay looks like for your connector, see Understanding Data Delays.
Hiding Metadata Fields from Your Reports
Metadata fields are optional. If you do not need them, simply leave them unselected when you choose fields for your data table or report, and they will not appear in your output.
When Your Data Really Has Stopped Updating
If you suspect your data source has stopped collecting data, check it directly rather than reading it from a single metadata field. Go to Sources > Manage accounts, open Actions > History for the account, and review recent sync activity and any reported data gaps. If the source looks stalled there, please submit a ticket and our team will investigate.