Kentico - Canto Integration and Automation

Common Integration Use Cases Between Kentico and Canto

1. Centralized asset publishing from Canto to Kentico

Direction: Canto to Kentico

Marketing teams store approved images, videos, brochures, and brand files in Canto, then publish selected assets directly into Kentico for use on websites, landing pages, and campaign microsites. This ensures web teams always work with the latest approved content and reduces the risk of outdated or off-brand assets being used online.

Business value: Faster content publishing, stronger brand consistency, and less manual downloading and re-uploading of files.

2. Automatic asset metadata sync for better content governance

Direction: Bi-directional

When an asset is updated in Canto, key metadata such as title, description, usage rights, campaign tags, and expiration dates can be synchronized to Kentico. Kentico content editors can then search and filter assets more effectively when building pages or campaigns. If Kentico adds contextual usage data, it can be pushed back to Canto to improve asset governance and reporting.

Business value: Improved searchability, better compliance with usage rights, and reduced content management effort.

3. Campaign asset delivery to Kentico landing pages

Direction: Canto to Kentico

For product launches, events, or seasonal promotions, campaign teams can manage all approved visuals and documents in Canto and make them available to Kentico page builders. Kentico editors can then assemble landing pages using pre-approved campaign assets without waiting for manual file transfers or design team intervention.

Business value: Shorter campaign launch cycles, fewer approval bottlenecks, and more consistent campaign execution across channels.

4. Asset usage tracking from Kentico back to Canto

Direction: Kentico to Canto

When assets from Canto are used in Kentico pages, the integration can send usage data back to Canto, including page URL, campaign name, publish date, and content owner. This gives marketing and brand teams visibility into where assets are deployed and helps identify which files are driving engagement or need updating.

Business value: Better asset lifecycle management, improved reporting, and stronger control over content reuse.

5. Expiration and replacement workflow for time-sensitive assets

Direction: Canto to Kentico

Assets in Canto can carry expiration dates for legal, seasonal, or licensing reasons. When an asset is nearing expiration, the integration can notify Kentico editors or automatically flag the asset for replacement on active pages. Updated versions in Canto can then be swapped into Kentico without rebuilding the page.

Business value: Reduced compliance risk, fewer broken or outdated web assets, and lower maintenance overhead.

6. Brand portal or content hub powered by Kentico and fed by Canto

Direction: Canto to Kentico

Organizations can use Kentico to build a branded content hub, partner portal, or media library while sourcing approved assets from Canto. External users or internal teams access a curated experience in Kentico, while Canto remains the system of record for asset storage and governance.

Business value: A controlled self-service experience for stakeholders, reduced ad hoc file sharing, and better brand asset distribution.

7. Workflow handoff between creative production and web publishing

Direction: Bi-directional

Creative teams finalize assets in Canto, then notify Kentico content owners when files are ready for publishing. If Kentico editors request revisions or alternate formats, those requests can be sent back to Canto or the creative workflow process. This creates a cleaner handoff between design, marketing, and web publishing teams.

Business value: Fewer email-based handoffs, clearer accountability, and smoother collaboration across creative and digital teams.