Skip to main content

Connected Portal FAD 2026 Metrics

Key metrics to remain compliant in the Factory Authorized Dealer program.

Updated over a week ago

This article explains the 2026 Connected Portal FAD metrics, including what’s required, why each metric matters, and which actions in Connected Portal count toward your score.

Metric

Requirement

8 daily logins per quarter (max 1 per day)

At least 5 remote service actions per quarter

Targets based on % of connected controls

Targets based on % of systems with data sharing enabled

Download at least 15 runtime reports

*Indicates Bonus Metric


Connected Portal Daily Logins

Requirement
8 daily logins per quarter (only one login per day counts).

Why this metric matters
Regular logins ensure dealers stay aware of system health, alerts, and opportunities to proactively support homeowners.

What counts

  • Logging into Connected Portal on a given day

  • Multiple logins on the same day count as one

What does not count

  • Multiple logins on the same day

  • Passive sessions without an authenticated login


Remote Services Performed (Bonus Metric)

Requirement
Perform at least 5 remote service actions per quarter.

Why this metric matters
Remote services help dealers diagnose issues faster, prevent failures, and resolve problems without an on-site visit. This reduces truck rolls, improves first-time fix rates, and increases homeowner satisfaction.

What actions count
For supported systems, a remote service action is tracked when you perform any of the following:

  • Remote Configuration Change
    Update supported system configuration fields (ex. filter interval months, humidity offset percent, or outdoor temperature offset in °F).

  • Malfunction Detection Report
    Run a Malfunction Detection report to identify early signs of equipment degradation before a fault occurs.

  • Remote System Test
    Run a remote test to on compatible systems to assess system performance using real-time data.

Where to perform these actions

  • Remote Configuration Change

    1. From the control/indoor Unit/outdoor unit product details pages, navigate to the configuration menu, change a configuration setting, and save the changes

  • Malfunction Detection Report

    1. From the navigation, click the Malfunction Detection tab, and click "Run a Report"

  • Remote System Test

    1. For compatible systems, navigate to any device, click "Test Equipment", and initiate a test


% Controls Connected

Requirement
Points are awarded based on the percentage of controls connected:

  • Minimum points: 75%–84%

  • Medium points: 85%–95%

  • Maximum points: 95%+

Why this metric matters
This metric tracks how effectively homeowners are converting their systems into connected SmartHome profiles, taking the first steps to enable system health visibility, diagnostics, and proactive service.

How it’s calculated

  • % Connected = Total connected controls ÷ (Total connected controls + total queued controls)


% Systems with Data Sharing Enabled

Requirement
Points are awarded based on the percentage of connected systems with data sharing enabled:

  • Minimum points: 35%–50%

  • Medium points: 51%–75%

  • Maximum points: 76%–100%

Why this metric matters
Data sharing enables dealers to remotely view system status, configurations, and service-relevant information, which is required for remote diagnostics and proactive service.

What counts
A system counts when at least one data-sharing permission is enabled by the homeowner.

How homeowners enable permissions

  • Infinity / Evolution: Home App or Consumer Portals

  • Ecobee: Ecobee Home App


Runtime Reports Generated (Bonus Metric)

Requirement
Download at least 15 runtime reports per year.

Why this metric matters
Runtime reports provide insight into system usage, performance trends, and potential optimization opportunities.

How it’s calculated

  1. Navigate to a compatible thermostat or control and click "Runtime Report"

  2. Click "Export Runtime Report"


Calculation Context:

% Connected and % Systems with Data Sharing

  • Originally, metrics were intended to include only controls linked between January 2024 and December 2026.

  • A February 2025 database migration reset the “first linked date” for many systems.

  • As a result, systems linked prior to February 2025 now appear newly linked.

  • Because of this, current FAD calculations are effectively based on lifetime statistics, not a strict date-bounded window.

Did this answer your question?