inriver - Agility Integration and Automation

Common Integration Use Cases Between inriver and Agility

1. Centralized product content publishing to content-rich web pages

Data flow: inriver → Agility

Use inriver as the system of record for product attributes, descriptions, specifications, and marketing copy, then push approved content into Agility to build product landing pages, category pages, and campaign pages. This allows marketing teams to assemble web experiences without manually rekeying product data.

• Reduces duplicate content entry across PIM and CMS teams
• Ensures product pages stay aligned with approved product information
• Speeds up page creation for launches, promotions, and seasonal campaigns

2. Automated enrichment of editorial content with product data

Data flow: inriver → Agility

Marketing teams can create editorial content in Agility and dynamically insert product details, feature highlights, dimensions, and comparison data from inriver. This is useful for buying guides, solution pages, and industry-specific landing pages that need accurate product references.

• Improves content accuracy and consistency
• Supports faster production of campaign and thought-leadership pages
• Enables non-technical teams to build product-led content experiences

3. Product launch workflow across marketing and web teams

Data flow: Bi-directional

When a new product is prepared in inriver, approved product content can be sent to Agility for page creation, while Agility can return page status, publication readiness, or content completion signals to support launch coordination. This creates a structured workflow between product marketing, web content, and digital operations teams.

• Improves launch governance and cross-team visibility
• Helps ensure product pages are ready when products go live
• Reduces launch delays caused by disconnected content processes

4. Localization of product pages for regional markets

Data flow: inriver → Agility

Use inriver to manage localized product descriptions, compliance text, and market-specific attributes, then publish the correct language and regional variants into Agility. Regional marketing teams can then build localized web pages using approved product content without relying on manual translation copy-paste.

• Supports global content operations with local market relevance
• Reduces translation errors and inconsistent messaging
• Accelerates rollout of multilingual product pages

5. Dynamic category and collection pages driven by product hierarchy

Data flow: inriver → Agility

inriver product hierarchies, families, and relationships can feed Agility to power category pages, product collections, and comparison pages. This is especially valuable for manufacturers and distributors with large catalogs that need structured navigation and filtering on the website.

• Improves site navigation and product discoverability
• Automates updates when product relationships change
• Supports scalable management of large and complex catalogs

6. Digital asset and rich media coordination for product storytelling

Data flow: inriver → Agility

Product images, videos, spec sheets, and other approved assets managed alongside product content in inriver can be surfaced in Agility to enrich product pages and campaign content. This helps ensure that web teams use the latest approved media for each product.

• Creates more compelling product experiences
• Reduces risk of outdated or unapproved assets appearing on the website
• Improves conversion through stronger visual merchandising

7. Content governance and approval synchronization

Data flow: Bi-directional

Organizations can integrate approval states so that only product content marked as ready in inriver is published to Agility, while Agility can signal whether a page is drafted, reviewed, or live. This supports controlled publishing for regulated industries or brands with strict content governance.

• Strengthens compliance and approval control
• Prevents premature publication of incomplete product information
• Provides better auditability across product and web content workflows

8. Personalized product-led experiences on headless web properties

Data flow: inriver → Agility

Agility can use product content from inriver to assemble personalized or segment-specific web experiences, such as industry landing pages, account-based marketing pages, or solution bundles. Product data remains centrally managed in inriver while Agility handles presentation logic and page composition.

• Supports tailored digital experiences without duplicating product data
• Enables faster creation of segment-specific campaigns
• Improves consistency across web, mobile, and campaign channels