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

# Your Data

> A plain-language map of every data domain in your workspace — what each one holds and where to find its details.

Your workspace holds several kinds of data, each grouped into a **domain**. This page is the map: what each domain is, in plain language, and a direct link to the **full field-by-field reference** for every single dataset. To learn how to *work with* any of these as a table — filtering, columns, visibility — see [Data Views](/guide/data-views).

<Columns cols={2}>
  <Card title="Sales & Commerce" icon="cart-shopping" href="/api/data-model/orders">
    Your shop's transactions — orders, line items, the customers behind them, the products they bought, and synced meeting notes.
  </Card>

  <Card title="Procurement" icon="boxes-stacked" href="/guide/procurement">
    Buying the right stock at the right time — demand, a per-SKU queue, purchase orders, suppliers, seasonality and trend analytics.
  </Card>

  <Card title="Marketing & Outreach" icon="bullhorn" href="/api/data-model/linkedin-leads">
    How you reach and track customers — LinkedIn, email, ads, web events, the YouTube market-intelligence pipeline, and support.
  </Card>

  <Card title="Governance" icon="gavel" href="/api/data-model/decisions">
    The rules and playbooks your company runs on — decisions, strategy documents, and SOPs.
  </Card>
</Columns>

## Every dataset, in detail

Every dataset below has its own reference page — what it is, how it gets its data, and **every field explained**. This is the full catalog.

### Sales & Commerce

Your shop's raw transaction data — the material behind almost every sales and retention number.

* [**Orders**](/api/data-model/orders) — every e-commerce order with status, totals, and shipping.
* [**Order Line Items**](/api/data-model/order-line-items) — the individual products on each order.
* [**Customers**](/api/data-model/customers) — customer/contact records with lifecycle status.
* [**Products**](/api/data-model/products) — product master data: stock, prices, lead times, family/model attributes.
* [**Meeting Notes**](/api/data-model/meeting-notes) — synced call and meeting notes with action items.

### Procurement

Turning sales history into one clear buying decision per product. Start with the [Purchasing & Procurement](/guide/procurement) chapter for the full workflow.

* [**Product Demand**](/api/data-model/product-demand) — how fast each variant sells and how long stock lasts.
* [**Procurement Queue**](/api/data-model/procurement-queue) — one row = one buying decision per SKU, with status and recommendation.
* [**Purchase Orders**](/api/data-model/purchase-orders) — order lines from draft through received.
* [**Suppliers**](/api/data-model/suppliers) — supplier master data: lead times, target stock, currency.
* [**Procurement Config**](/api/data-model/procurement-config) — the tunables: demand weights, cutoffs, seasonality.
* [**Weekly Sales**](/api/data-model/weekly-sales) — units sold per product per calendar week.
* [**Family Trend**](/api/data-model/family-trend) — which model families are rising or falling, seasonally adjusted.
* [**Seasonality**](/api/data-model/seasonality) — the seasonal factor per month and where it comes from.
* [**Customer Reorder Due**](/api/data-model/customer-reorder-due) — repeat customers due for their next purchase.

### Marketing & Outreach

How you reach and track customers. These are largely **agent-maintained** — they fill and stay current once your workspace runs the relevant outreach and market-intelligence agents.

* [**LinkedIn Leads**](/api/data-model/linkedin-leads) — the LinkedIn lead/CRM record: identity, pipeline scoring, outreach timing, agent handoff.
* [**LinkedIn Messages**](/api/data-model/linkedin-messages) — the per-message log behind each lead.
* [**LinkedIn Activity Limits**](/api/data-model/linkedin-activity) — the daily guardrail keeping automated activity safe.
* [**Email Campaigns**](/api/data-model/email-campaigns) — one row per send: audience, opens, clicks, revenue.
* [**Meta Ads**](/api/data-model/meta-ads) — daily Facebook/Instagram ad performance.
* [**Web Events**](/api/data-model/web-events) — raw website behaviour events with session and device context.
* [**YouTube Watch**](/api/data-model/youtube) — watched channels and the videos pulled, transcribed, and AI-enriched from them.
* [**Support Tickets**](/api/data-model/support-tickets) — customer support tickets with status, priority, and resolution.
* [**Customer Outreach**](/api/data-model/customer-outreach) — the reorder-outreach tracker, one row per customer per cycle.

### Governance

The rules and playbooks your company runs on.

* [**Decisions**](/api/data-model/decisions) — process questions and the rules they become (61 fields, the full loop).
* [**Strategy**](/api/data-model/strategy) — company strategy documents.
* [**SOP**](/api/data-model/sop) — standard operating procedures.

### Knowledge (what your agents know)

Not business tables but the context agents draw on — documented in the API reference: [Knowledge](/api/knowledge), [Memory](/api/memory), [Skills](/api/skills).

## How data gets in

Most domains fill themselves as your business runs. Two paths bring data in:

* **Connectors & ingest** — admins connect external systems under **Settings › Data Sources** and point them at an ingest endpoint; rows appear idempotently (re-sending the same record updates instead of duplicating). Full details in the [Ingest API](/api/ingest) reference.
* **Agents** — the marketing, outreach, and market-intelligence domains are largely **agent-maintained**: they appear and stay current once your workspace runs the relevant agents.

<Note>
  Every table is isolated to your company and then filtered by your departments and each record's visibility scope — see [Data Views](/guide/data-views) for how that works in the UI.
</Note>