> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getinteract.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Write-back

> Tables Interact writes to your warehouse from Marketing Intelligence.

Marketing reports query your contract tables in place. Interact also **writes results back** into the **Warehouse - write** dataset from [Data mapping](https://docs.getinteract.com/org-settings/semantic-layer/data-mapping.md), so you can use them in BigQuery, BI, and agents.

```mermaid theme={null}
flowchart LR
  Contract[Your contract tables] -->|Warehouse - read| MI[Marketing Intelligence]
  MI -->|Write-back| Dest[Your write dataset]
```

The destination dataset must already exist (for example `src_interact`). Interact does not create it. The write connector’s service account needs write access to this dataset only. The read connector can stay read-only.

## Table names

Names are `{org_id}_` plus the table below. If your organisation id starts with a digit, the prefix is `org_{org_id}_`. `context_events` is not prefixed.

| Table | What it is |
| - | - |
| `{org_id}_attribution_results` | Conversion-level credit per [model](https://docs.getinteract.com/marketing/attribution.md) |
| `{org_id}_attribution_touchpoints` | Converting journeys used to compute that credit |
| `{org_id}_marketing_performance` | Precalculated daily metrics used by the marketing reports |
| `{org_id}_marketing_product_performance` | Product performance — when product tables are mapped |
| `{org_id}_marketing_product_availability` | Product availability — when price/stock is mapped |
| `{org_id}_marketing_product_classification` | Product classification — when product tables are mapped |
| `{org_id}_anomaly_scores` | Detected metric anomalies |
| `context_events` | Business events, when Interact owns that table |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.