The sync is available on plans that include the Export API.
How it works
3RD uses Fabric open mirroring. You create a mirrored database. 3RD writes files to that database’s landing zone in OneLake, and Fabric turns them into Delta tables within a few minutes. Replication runs on your capacity at no extra compute cost, and mirrored storage is free up to your capacity’s allowance.What you need
- A Fabric workspace on a running capacity (F SKU or trial).
- Someone who can create an app registration in Microsoft Entra ID.
- A Fabric administrator to allow service principals, if your tenant doesn’t already.
- The owner or admin role in your 3RD organization.
Set it up
1
Register an app in Microsoft Entra ID
In the Azure portal, go to Microsoft Entra ID → App registrations → New registration and create an app, for example
3RD sync. On its Certificates & secrets page, create a client secret.Note three values: the Directory (tenant) ID and Application (client) ID from the app’s Overview page, and the secret’s Value. You can’t see the secret’s value again after you leave the page.2
Let service principals use Fabric
A Fabric administrator opens Admin portal → Tenant settings → Developer settings and turns on Service principals can use Fabric APIs. They can turn it on for the whole tenant or for a security group; with a group, add your app to it.
3
Create a mirrored database
In your workspace, select New item → Mirrored database and choose open mirroring. Name it, for example
3RD, and create it. On its Home page, copy the landing zone URL.4
Give the app access to the workspace
In the workspace, open Manage access, add your app by name, and give it the Contributor role.
5
Connect in 3RD
Go to Brand → Integrations, and under Reporting open Microsoft Fabric. Paste the landing zone URL, tenant ID, application ID and client secret, then click Connect.
6
Test the connection
Click Test connection. 3RD signs in as your app and writes and deletes a test file in the landing zone. When the test passes, 3RD starts loading your history. If it fails, the message tells you which step to fix. See Troubleshooting.
Security
- Your app, your control. 3RD signs in as the app registration you created. Delete its secret or remove it from the workspace, and 3RD loses access.
- Encrypted secret. 3RD stores the client secret encrypted and only ever shows its last four characters.
- Write-only. 3RD writes files to the mirrored database’s landing zone. It doesn’t read your other data.
Tables
Each dataset becomes one table in the mirrored database. Column names are the Export API field names in upper case; see the Export API reference for what each field means.
Every table also has
ROW_KEY, the key Fabric uses to update a row. Every dated table has BRAND_ID, which joins to BRANDS.ID, and _SYNCED_AT, the time the row was written.
How the sync works
- Daily refresh. Each run reloads the last 7 days, because AI answers for recent days can still arrive. Rows for those days are updated in place.
- Rows aren’t deleted. If a row for a reloaded day no longer exists in 3RD, for example because every answer behind it was removed, it stays in Fabric. This is rare. Reload history doesn’t remove such rows either.
- History. The first sync goes back as far as your plan’s Export API history allows, up to two years. See Pagination and history.
- New columns. When 3RD adds a field to the Export API, Fabric can’t add a column to an open-mirroring table in place. 3RD drops that table and loads it again with its whole history on the next sync, so the table is briefly missing.
- Sync now. Click Sync now in settings to run a sync outside the daily schedule, or Reload history to load your whole history again.
Example query
Weekly visibility per AI model for one brand:VISIBILITY_RATE: a day with more answers should weigh more.
Manage the connection
- Change details. Update the client secret, the app or the landing zone in settings. Test the connection again afterwards.
- Disconnect. Click Disconnect. 3RD deletes its copy of the secret and stops syncing. Your mirrored database and its tables stay. Delete the client secret in Microsoft Entra ID, and remove the app from the workspace if nothing else uses it.
- Plan changes. If your plan no longer includes the Export API, syncing stops and your tables stay as they were.
Troubleshooting
If 3RD shows a successful sync but a table is missing or stale in Fabric, open the mirrored database’s Monitor replication page. It shows each table’s status and any error.
Related
- Export API — the endpoints and fields behind the tables
- Snowflake — the same data in Snowflake
- Looker Studio connector — the same data in Looker Studio
- Metrics at a glance — what each metric means