Connector name: Profound (Pre Release connector)

Table name: Brand Visibility

API documentation link: https://docs.tryprofound.com/rest-api/introduction

Additional details:  Further to my conversation in support ticket 382385

I am trying to report AI Visibility by Brand By Date

This is the API query I would run - 

{
  "method": "POST",
  "url": "https://api.tryprofound.com/v1/reports/visibility",
  "headers": {
    "Content-Type": "application/json",
    "X-API-Key": "***REDACTED***"
  },
  "data": {
    "category_id": "c6a19e5b-30ee-405a-a1e2-d1a275b77cc2",
    "start_date": "2026-05-21",
    "end_date": "2026-05-22",
    "metrics": [
      "visibility_score"
    ],
    "dimensions": [
      "asset_name",
      "date"
    ],
    "pagination": {
      "limit": 10000
    }
  }
}

I reviewed this again with that context. The output you need is generated by Profound’s /v1/reports/visibility endpoint using the dynamic report dimensions:

```
[
  "asset_name",
  "date"
]
```

 
with the metric:

```
[
  "visibility_score"
]
```

This returns a brand-by-date visibility report directly from the Profound API.
 
The current prerelease connector output does not expose an equivalent table or field combination that reproduces this same asset_name + date report output. The existing REPORT_VISIBILITY table is based on the dimensions currently synced by the connector, and the asset_idvalues returned by the source API for that table shape often contain the all-zero UUID. Because of that, joining REPORT_VISIBILITY.asset_id to ASSET.id will not produce the same brand-by-date visibility report that your direct API query returns with asset_name.
 
Based on this, the current connector schema does not yet support this specific reporting use case. You can raise this as a feature request for the prerelease connector: support syncing the Profound visibility report output at the asset_name + date grain, including visibility_score, so customers can report AI visibility by brand by date from the destination tables.