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

# Metrio

> Metrio integration for ESG performance management and carbon accounting.

<Tip>
  Need help in this area? See [Data Export FAQ](/platform/data-export/faq).
</Tip>

The Metrio integration connects Nectar to Nasdaq Metrio for ESG performance management. Nectar pushes aggregated monthly utility usage into your Metrio datasources, then reads back Metrio's import reports so you can verify exactly what Metrio accepted — and spot discrepancies before reporting.

## Platform views

| View                  | Where to open it                                                                                                                      | What it is for                                                                       |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| **Setup wizard**      | [**Data Export > Integrations > Metrio**](https://dash.nectarclimate.com/data-export/integrations/metrio/setup) (when not configured) | Connect Metrio, verify datasource keys, and map sites to Metrio facility identifiers |
| **Integration hub**   | [**Data Export > Integrations > Metrio**](https://dash.nectarclimate.com/data-export/integrations/metrio)                             | Day-to-day home: connection status, export, recent history, and sync verification    |
| **Export dialog**     | **Export** on the integration hub                                                                                                     | Configure and run a download or API push without leaving the hub                     |
| **Standalone export** | [**Data Export > Integrations > Metrio > Export**](https://dash.nectarclimate.com/data-export/integrations/metrio/export)             | Full-page export form (same fields as the dialog)                                    |
| **Settings**          | [**Settings > Company > Integrations > Metrio**](https://dash.nectarclimate.com/settings/company/integrations/metrio)                 | Edit credentials, datasource keys, import mode, and facility mapping                 |

Nothing is pushed to Metrio during setup — you decide when your data is ready to sync. Verification views populate after your first export with **Upload to Metrio** enabled: each push stores Metrio's import report, which becomes the basis for comparison.

## Setup wizard

The setup wizard at [**Data Export > Integrations > Metrio > Set up Metrio**](https://dash.nectarclimate.com/data-export/integrations/metrio/setup) has three steps:

1. **Credentials** — Your Metrio account prefix (for example `yourcompany` for yourcompany.metrio.net) and API key. One key covers all datasources; ask your Metrio administrator for a key with access to the Datasources API.
2. **Datasources** — The datasource key for each utility type you push (electricity, gas and fuel, water, waste). Leave a field blank to skip that utility. Every key is verified against the live Metrio API before the wizard continues — a failed check tells you whether the API key was rejected or the datasource key was not found in your account.
3. **Facility mapping** — The Metrio facility identifier for each [site](/platform/glossary#site) (the value written to the datasource's "offices" column). Rows are prefilled from each site's external ID, and you can exclude sites you don't want to push.

When setup finishes, Nectar returns you to the integration hub. Run a full-range export with **Upload to Metrio** enabled so verification has a stored import report to compare against.

## Integration hub

Navigate to [**Data Export > Integrations > Metrio**](https://dash.nectarclimate.com/data-export/integrations/metrio) for the main integration page. It is a single-page layout (not tabbed): status and history at the top, sync verification below once fully configured.

### Page header

* **Archive** — Deactivates the integration and hides it from navigation. Export history and data already in Metrio are not deleted.
* **Settings** — Opens [**Settings > Company > Integrations > Metrio**](https://dash.nectarclimate.com/settings/company/integrations/metrio) for credentials, datasources, and facility mapping.

### Warning banners

* **Legacy config (push only)** — Older companies may still use metadata-only credentials. Push still works, but verification, facility mapping, and read-back comparison require completing the [setup wizard](https://dash.nectarclimate.com/data-export/integrations/metrio/setup).
* **Unmapped sites** — Sites without a Metrio facility identifier (and not explicitly excluded) are skipped during export. The banner links to facility mapping in settings.

### Status card

Shows whether Metrio is **Connected**, **Not configured**, or **Legacy config (push only)**. The primary **Export** button opens the export dialog. The card explains that Metrio requires a separate export per utility type and that Nectar stores Metrio's import report after each API push.

### Recent syncs & downloads

Lists your latest Metrio exports and API pushes. Click a row to open the **export detail sheet** — configuration, download link (if applicable), and (for API pushes) the Metrio import report. Use **All history** or [**Data Export > History**](https://dash.nectarclimate.com/data-export/history) for the full cross-integration log.

### Sync verification — find and resolve discrepancies

After setup (non-legacy companies only), the **Compare previous Metrio exports with Nectar** section is where you confirm Metrio holds the right numbers and fix the ones it does not. It verifies one push at a time.

**How to use it:**

1. **Pick a sync** — Use the required **Sync** picker (labels show date, utility type, and export name). The most recent sync is selected by default; every clear resets to it.
2. **Read the summary line** — The card description tallies the outcome: how many rows are synced, drifted, not on Metrio, missing in Nectar, and rejected, plus the sync date and range.
3. **Filter to what needs attention** — Use the **Status** filter (multi-select) to isolate, for example, only **Drifted** and **Rejected** rows, and the **Facility** filter to focus on one site.
4. **Inspect each row** — For the selected sync, Nectar compares every row Metrio **accepted** against what the same export scope would produce **today**, per facility, month, and unit. Values use the exact units that were pushed, so the diff reflects real data changes, not unit conversion.

| Column                 | Meaning                                                                        |
| ---------------------- | ------------------------------------------------------------------------------ |
| **Facility**           | Nectar site name and Metrio facility identifier                                |
| **Month**              | Calendar month for the aggregated row                                          |
| **Unit**               | Unit label for that row (gas and water may split by fuel type or water source) |
| **Pushed into Metrio** | Value Metrio accepted for that import                                          |
| **Nectar today**       | Value Nectar would export for the same facility and month now                  |
| **Diff**               | Absolute and percentage difference (amber = higher today, red = lower today)   |
| **Status**             | See the status list below                                                      |

**Statuses:**

* **Synced** — The value Metrio holds still matches your data. No action needed.
* **Drifted** — Your data changed since the push (for example, bills were revised after the sync). Resolve with **Sync**.
* **Not on Metrio** — Today's export would include a row this sync never pushed. Resolve with **Push**.
* **Missing in Nectar** — Metrio accepted a value your data no longer produces. Investigate in [Data Inventory](/platform/data-inventory/overview); Metrio keeps the old value until you re-push a correction.
* **Rejected** — Metrio refused the row at import time. Hover the badge for Metrio's reason, correct the underlying data, then **Push**.
* **Superseded** — A newer sync already re-covered this row; Metrio's current value comes from that later push, so you can usually ignore it.

**Resolving discrepancies:**

* **Per row** — Click **Push** (for *Not on Metrio* / *Rejected*) or **Sync** (for *Drifted*) to re-export just that facility, month, and utility. A confirmation dialog states that existing Metrio values for that facility and month are overwritten.
* **In bulk** — Click **Re-push N rows** in the card header to re-export every actionable row (drifted, not on Metrio, or rejected) in the current filter scope as a single sync. Narrow the filters first to control exactly what gets re-pushed.

Re-pushing overwrites previous Metrio values cleanly when import mode is **Replace duplicates** (the default — see [Import modes](#import-modes)). Nectar pulls the import report automatically while Metrio is still processing, so statuses settle without a manual refresh. After a re-push, the row status returns to **Synced** once Metrio confirms the new value.

## Export dialog and standalone export

Click **Export** on the hub, or open the [standalone export page](https://dash.nectarclimate.com/data-export/integrations/metrio/export). Both use the same form:

| Field                                      | Description                                                                                                      |
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- |
| **Export label**                           | Name shown in export history                                                                                     |
| **Utility type**                           | One commodity per export (electricity, gas and fuel, water, or waste). Gas includes natural gas and fuel meters. |
| **Month range**                            | Billing months to aggregate                                                                                      |
| **Sites**                                  | Scope to specific sites, or leave empty for all mapped sites                                                     |
| **Include bills with data quality issues** | When off, flagged bills are excluded                                                                             |
| **Upload to Metrio**                       | When on, pushes via API in addition to generating the file                                                       |

A progress dialog runs during the export; a success dialog confirms when it completes.

## Import report

When an export uploads to Metrio, Nectar waits for the import to finish and stores Metrio's full import report. Open any API push from the recent history card (or from [Export History](/platform/data-export/export-history)) to see per-row verdicts — **Accepted**, **Rejected**, or **Merged** — with each row's facility, month, and value. If an import is still processing, Nectar pulls the report automatically as soon as it finishes.

The import report shows *what Metrio did at import time*; sync verification shows *whether Metrio still matches Nectar today*. Use the report to diagnose a failed push (rejected rows and reasons) and sync verification to catch drift after the fact.

## Settings

Manage the integration in [**Settings > Company > Integrations > Metrio**](https://dash.nectarclimate.com/settings/company/integrations/metrio):

* **Connection** — Metrio account, masked API key, import mode, and last sync result. **Edit** re-verifies every datasource key against Metrio before saving, so invalid keys never reach your configuration.
* **Datasources** — Upload target per utility type, with live row count and last input date from Metrio at verification.
* **Facility mapping** — Each Nectar site mapped to its Metrio facility identifier, with exclusions.
* **Archive** — Same as **Archive** on the integration hub.

### Import modes

| Mode                                 | Behavior                                                                   |
| ------------------------------------ | -------------------------------------------------------------------------- |
| **Replace duplicates** (recommended) | Re-pushed months overwrite the matching rows in Metrio — safe for re-syncs |
| **Ignore duplicates**                | Rows that already exist in Metrio are left unchanged                       |
| **Replace all**                      | Deletes everything in the datasource before importing — use with care      |

## FAQ

<AccordionGroup>
  <Accordion title="How does Nectar map sites to Metrio facilities?">
    Through the facility mapping in integration settings. Each Nectar site maps to a Metrio facility identifier — the value written to the datasource's "offices" column. The mapping is prefilled from each site's external ID during setup, and sites can be excluded from pushes.
  </Accordion>

  <Accordion title="Where do I get datasource keys?">
    Datasource keys identify the Metrio datasources that receive your data (one per utility type). They are provided by Metrio and are specific to your account — contact your Metrio administrator, or [support@nectarclimate.com](mailto:support@nectarclimate.com) for help configuring them.
  </Accordion>

  <Accordion title="What does Nectar read back from Metrio?">
    The import reports of pushes Nectar made — Metrio's record of every row it accepted, rejected, or merged. This powers sync verification without extra Metrio permissions. Data added to Metrio by other means (manual entry, other tools) is not visible to Nectar.
  </Accordion>

  <Accordion title="What is the difference between Push and Sync?">
    **Push** sends data that Metrio does not have yet (**Not on Metrio**) or that Metrio rejected. **Sync** overwrites data that Metrio already holds but that no longer matches Nectar (**Drifted**). Bulk **Re-push** handles every actionable row in the current verification view.
  </Accordion>

  <Accordion title="How do I fix a drifted row?">
    Use **Sync** on the row to re-push that facility and month, or **Re-push** to re-export everything the verification flagged. With the default **Replace duplicates** import mode, the re-push overwrites the old values in Metrio cleanly.
  </Accordion>

  <Accordion title="Why is sync verification empty?">
    Run at least one export with **Upload to Metrio** enabled. Legacy push-only configurations must complete the setup wizard first. Verification appears only for API pushes that stored an import report.
  </Accordion>
</AccordionGroup>