---
name: strata-integration-support
description: "Diagnose and support STRATA platform integrations."
version: 2.0.0
author: Hermes Agent (rebuild)
license: Proprietary site content
platforms: [linux, macos, windows]
metadata:
  hermes:
    tags: [STRATA, Cross-Platform, Operations, Verification]
    related_skills: []
---

# STRATA Integration Support

Use for supporting STRATA program integrations: SBMS to Eleven, AEInbox, OneStrata, VIEW, and OneTIM.

## Core Resources

- **SBMS to Eleven to AEInbox Workflow:** https://freewheel.zendesk.com/hc/en-us/articles/33524748609677
- **StrataLink Guides:** https://support.workamajig.com/hc/en-us/sections/360005938751
- **StrataLink Overview:** Strata sync overview
- **StrataLink Troubleshooting:** StrataLink troubleshooting guide
- **StrataLink Log Files:** Sending StrataLink logs
- **Strata-to-Workamajig Sync Fields:** Field mapping reference
- **AEInbox Support:** https://freewheel.zendesk.com/hc/en-us/sections/33524173628301
- **API Docs:** https://api-docs.freewheel.tv/
- **Knowledge Hub:** https://hub.freewheel.tv/

## Integration Programs

- **SBMS → Eleven:** Schedule export, Hiatus Week/Day data, status sync
- **Eleven → AEInbox:** Order release, status transitions, traffic coordination
- **AEInbox ↔ OneCONNECT:** Order redirecting (bidirectional)
- **OneStrata:** Unified platform integration, cross-media data sync
- **VIEW:** Partner API integration, programmatic inventory connectivity
- **OneTIM:** TIM/traffic management coordination, schedule sync

## Integration Diagnostic Workflow

1. **Identify the integration:** SBMS→Eleven, Eleven→AEInbox, AEInbox↔OneCONNECT, OneStrata, VIEW, OneTIM
2. **Identify direction:** source → destination or bidirectional
3. **Gather context:**
   - Connected programs and versions
   - Sync frequency and schedule
   - Field mapping configuration
   - Authentication (OneLogin, API keys)
4. **Check sync status:**
   - SBMS "Send to Eleven" button and Status transitions
   - Eleven status: "Unsent" vs. "Sent"
   - AEInbox order receipt and traffic status
   - OneCONNECT redirect status
   - StrataLink log files for errors
   - OneStrata unified data sync
5. **Identify blockers:**
   - Schedule export failures (SBMS → Eleven)
   - Hiatus Week/Day data transmission issues
   - Status sync failures between programs
   - AEInbox ↔ OneCONNECT redirect errors
   - .scx/.xml save format mismatches
   - OneStrata module navigation/data access
   - VIEW partner API auth/token issues
   - OneTIM schedule coordination gaps
6. **Remediate:**
   - Update schedule export configuration (SBMS)
   - Fix status sync between Eleven and AEInbox
   - Correct AEInbox ↔ OneCONNECT redirect rules
   - Refresh OneStrata data sync
   - Update VIEW partner credentials
   - Adjust OneTIM coordination settings

## SBMS to Eleven to AEInbox Workflow (Comcast Spotlight)

- **SBMS:** Select schedules → "Send to Eleven" → Status = "Sent"
- **Eleven:** Status = "Unsent" (buyer has not released to AEInbox)
- **Eleven:** Buyer releases → Status = "Sent" to AEInbox
- **AEInbox:** Order received, traffic initiated
- **Key issue:** Status sync failures at any transition point

## AEInbox ↔ OneCONNECT Redirect Issues

- AEInbox → OneCONNECT redirect
- OneCONNECT → AEInbox redirect
- Order format compatibility
- Status tracking during redirect

## OneStrata Integration Issues

- Module navigation (SPOT/Network/Print/Outdoor/Digital/Media Billing)
- Cross-media data sync between modules
- Unified platform access and authentication
- OneStrata ↔ Eleven/AEInbox data alignment

## Output

Provide: integration identified, sync status analysis, root cause, remediation steps, and recommended configuration changes.

## Inputs and Boundaries

- Require the account, environment, platform scope, identifiers, date range, requested operation, and source-system definitions.
- Establish the authoritative source, schema, timezone, currency, attribution window, and aggregation grain before comparison.
- Default to read-only inspection. Require explicit approval before changing campaign state, billing records, identities, routing, or integrations.
- Protect credentials, client data, audience data, financial data, and partner information.

## Failure Handling

- Record target, operation, timestamp, response status, error, source, and correlation ID when available.
- Distinguish authentication, permission, schema, identity, stale-data, dependency, timeout, and platform failures.
- Do not retry mutations blindly. Check current state and partial completion before retrying.
- Escalate critical incidents with customer impact, revenue risk, privacy risk, owner, and safe fallback.

## Verification

- Confirm every requested platform, record, period, and reconciliation dimension was checked.
- Preserve source totals and compare them with normalized or corrected totals.
- Read back approved changes from the authoritative system and verify downstream propagation.
- Report status, evidence, exceptions, assumptions, confidence, approvals, unresolved risks, and next actions.