Agility - Phrase Integration and Automation

Common Integration Use Cases Between Agility and Phrase

1. Centralized website localization workflow for multilingual content publishing

Data flow: Agility ? Phrase ? Agility

Marketing and content teams create pages, landing pages, and reusable content in Agility, then send selected content entries to Phrase for translation. Once translations are completed and approved, localized content is synced back into Agility for publishing across regional websites.

• Reduces manual copy and paste across language versions
• Supports faster launch of new market sites and campaign pages
• Helps maintain consistent structure and formatting across languages

2. Automated translation of campaign landing pages

Data flow: Agility ? Phrase ? Agility

When a marketing team publishes a new campaign landing page in Agility, the page content is automatically routed to Phrase for translation into target languages. Localized versions are returned to Agility so regional teams can publish campaign pages in sync with the original launch.

• Improves speed to market for global campaigns
• Ensures campaign messaging is aligned across regions
• Reduces dependency on email-based translation handoffs

3. Translation of reusable content components and content blocks

Data flow: Agility ? Phrase ? Agility

Agility often stores content in modular components such as banners, callouts, product highlights, and promotional blocks. These reusable elements can be sent to Phrase for translation once, then reused across multiple pages and channels in each language.

• Eliminates duplicate translation work for repeated content
• Improves consistency of terminology and messaging
• Supports scalable content operations for large websites

4. Localization workflow for headless content delivered to multiple channels

Data flow: Agility ? Phrase ? Agility

For organizations using Agility as a headless CMS, content can be translated in Phrase before being distributed to websites, mobile apps, kiosks, or other digital touchpoints. This enables a single localization process to support multiple presentation layers.

• Creates one source of truth for multilingual content
• Reduces channel-specific translation effort
• Supports consistent customer experiences across digital properties

5. Human and machine translation routing based on content type

Data flow: Agility ? Phrase ? Agility

High-volume or lower-risk content such as blog summaries, metadata, or internal announcements can be sent to machine translation in Phrase, while customer-facing pages and legal or brand-sensitive content are routed to human translators for review. Final approved content is then synchronized back to Agility.

• Optimizes translation cost based on content priority
• Speeds up turnaround for non-critical content
• Improves quality control for high-visibility pages

6. Translation of SEO metadata and multilingual page elements

Data flow: Agility ? Phrase ? Agility

Agility page metadata such as titles, descriptions, alt text, and structured page labels can be sent to Phrase for localization alongside page copy. This ensures search optimization elements are translated consistently for each market.

• Improves international SEO performance
• Reduces the risk of untranslated metadata going live
• Supports better discoverability in local search engines

7. Localization governance and approval workflow for regional teams

Data flow: Bi-directional

Content authors in Agility can submit source content to Phrase, where translators, reviewers, and regional marketing teams collaborate on approvals. Status updates can be reflected back in Agility so content owners know when localized assets are ready for publishing.

• Provides visibility into translation status across teams
• Improves accountability in multilingual publishing workflows
• Helps regional teams manage market-specific review cycles

8. Ongoing synchronization for content updates and version changes

Data flow: Bi-directional

When source content changes in Agility after initial translation, updated fields can be re-sent to Phrase for delta translation rather than retranslating the full page. Phrase returns only the updated localized content, keeping language versions aligned with the latest source copy.

• Reduces translation effort for incremental content changes
• Keeps global sites synchronized with the source language
• Minimizes publishing delays caused by content drift