Branding plugin

Channel Metrics

Provider-neutral metrics contract for channel-native outcome snapshots.

1 listed action1 capability groups

Connection facts

What the Channel Metrics connector actually exposes.

These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.

Connection method
mixed
Setup
Use the selected channel provider's analytics or API console, then store only the provider credential material and safe provider ref in StackOS.
Capability groups
Outcome Learning
Action boundaries
1 read action

Action catalog

Actions listed for Channel Metrics.

Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.

1 matching action

Outcome LearningReads data

Snapshot Distribution Outcome

Pull channel-native metrics for one distribution record into outcome snapshots.

Direct answer

How does the Channel Metrics integration work?

People continue using Channel Metrics as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.

  1. 01Your requestStart in your AI
  2. 02StackOS planExpands the steps
  3. 03Channel MetricsDoes its bounded part
  4. 04Checked resultKeeps the proof

Common questions

Channel Metrics and StackOS.

What can the Channel Metrics integration do in StackOS?

The current catalog includes 1 Channel Metrics action across Outcome Learning. The exact actions used depend on the workflow and approval rules.

Does StackOS replace Channel Metrics?

No. Channel Metrics remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.