Home | Connectors | Brightcove | Brightcove - OpenText Decision Service Integration and Automation

Brightcove - OpenText Decision Service Integration and Automation

Integrate Brightcove Video Platform and OpenText Decision Service Business Transaction Management apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between Brightcove and OpenText Decision Service

1. Rule-Based Video Access and Entitlement Control

Data flow: Brightcove ? OpenText Decision Service ? Brightcove

Brightcove can send viewer, account, subscription, geography, device, or campaign context to OpenText Decision Service to determine whether a user should be allowed to view premium, restricted, or time-sensitive content. The decision engine applies business rules such as membership tier, region, age restriction, contract status, or event registration status and returns an allow, deny, or alternate-content decision back to Brightcove.

Business value: This improves content monetization, enforces licensing rules consistently, and reduces manual intervention when access policies change.

2. Dynamic Ad and Monetization Decisioning for Video Streams

Data flow: Brightcove ? OpenText Decision Service ? Brightcove

Brightcove can pass viewer attributes, content category, and session context to OpenText Decision Service to determine which monetization path should be used, such as ad-supported playback, sponsorship overlay, subscription-only playback, or ad suppression for premium users. The decision service can also apply rules for campaign eligibility, frequency caps, or regional advertising restrictions.

Business value: Media and marketing teams can optimize revenue while ensuring ad delivery follows business and compliance rules without changing application code.

3. Personalized Content Routing for Marketing and Communications

Data flow: Brightcove ? OpenText Decision Service ? Brightcove

When a visitor lands on a video experience, Brightcove can send audience segment data, referral source, or CRM attributes to OpenText Decision Service. The service can decide which video variant, playlist, call to action, or next-best content should be shown based on rules such as industry, funnel stage, product interest, or customer lifecycle status.

Business value: This enables more relevant video experiences, improves conversion rates, and allows marketing teams to update targeting logic quickly without redeploying the video application.

4. Compliance and Policy Enforcement for Regulated Video Content

Data flow: Brightcove ? OpenText Decision Service ? Brightcove

For organizations in healthcare, finance, education, or public sector, Brightcove can submit content metadata and viewer context to OpenText Decision Service to determine whether a video can be shown, whether a disclaimer must be displayed, or whether additional approval is required. Rules can account for jurisdiction, content sensitivity, employee role, or training completion status.

Business value: This reduces compliance risk, standardizes policy enforcement, and supports audit-ready decisioning across multiple video channels.

5. Automated Event Access and Audience Segmentation for Live Streaming

Data flow: Brightcove ? OpenText Decision Service ? Brightcove

During live events, Brightcove can send registration status, ticket type, customer tier, or partner affiliation to OpenText Decision Service to determine access level. The decision engine can route viewers to the correct live stream, replay, or restricted session and can also decide whether to expose chat, Q and A, or downloadable assets.

Business value: Event teams can manage complex access models efficiently, improve attendee experience, and enforce sponsor or VIP entitlements consistently.

6. Workflow-Driven Video Approval and Publishing Decisions

Data flow: OpenText Decision Service ? Brightcove

When video content is ready for publication, upstream workflow systems can use OpenText Decision Service to determine whether the asset meets publishing criteria such as legal approval, brand review, localization completion, or required metadata presence. Once the rules are satisfied, the decision service can trigger Brightcove publishing or release the content for distribution.

Business value: This shortens approval cycles, prevents premature publishing, and ensures only compliant and complete assets are distributed.

7. Exception Handling and Escalation for High-Value Video Requests

Data flow: Brightcove ? OpenText Decision Service ? workflow or case management, then Brightcove

If a viewer requests access to a restricted video, a premium live event, or a special content package, Brightcove can send the request to OpenText Decision Service. The service can automatically approve standard cases, reject ineligible requests, or route exceptions to a case management process for manual review. Once resolved, the final decision can be returned to Brightcove for immediate enforcement.

Business value: This reduces support workload, speeds up exception handling, and creates a controlled process for high-risk or high-value content decisions.

8. Post-Playback Actions Based on Viewer Behavior and Business Rules

Data flow: Brightcove ? OpenText Decision Service ? downstream systems

Brightcove analytics can feed engagement signals such as completion rate, drop-off point, repeat viewing, or interaction with overlays into OpenText Decision Service. Based on predefined rules, the service can trigger actions such as lead scoring updates, follow-up content assignment, customer success alerts, or training certification status changes in connected systems.

Business value: This helps sales, marketing, and learning teams act on video engagement data in a structured way and align follow-up actions with business policy.

How to integrate and automate Brightcove with OpenText Decision Service using OneTeg?