FTP - Loci Integration and Automation

Common Integration Use Cases Between FTP and Loci

FTP and Loci complement each other well in enterprise environments where large content files, batch data exchanges, and legacy workflows must feed intelligent personalization engines. FTP is often the transport layer for scheduled file delivery, while Loci uses content and behavioral signals to generate relevant recommendations. Integrating the two enables organizations to move content and metadata efficiently into recommendation workflows and to export performance data back to operational teams.

1. Bulk Content Ingestion for Recommendation Indexing

Flow: FTP to Loci

Publishers, retailers, and media companies can use FTP to deliver large batches of content files, product descriptions, image assets, or article metadata to Loci for recommendation analysis. This is useful when source systems cannot expose APIs or when content is managed in nightly batch exports.

• Content teams export new or updated assets to an FTP server on a scheduled basis.
• Loci consumes the files through OneTeg integration and analyzes content attributes.
• Recommendations are refreshed based on the latest catalog or editorial updates.

Business value: Faster onboarding of new content into personalization workflows without changing upstream publishing systems.

2. Behavioral Data Export for Personalization Optimization

Flow: FTP to Loci

Organizations can export user interaction logs, clickstream summaries, or campaign performance files from analytics platforms to FTP, then feed them into Loci to improve recommendation relevance. This is especially useful when analytics data is produced in batch files by legacy reporting systems.

• Web or commerce teams generate daily engagement files.
• Files are transferred via FTP or SFTP to a secure landing location.
• Loci uses the data to refine content ranking and recommendation logic.

Business value: Better personalization decisions based on actual user behavior, with minimal impact on existing analytics processes.

3. Automated Media Asset Delivery for Personalized Content Experiences

Flow: FTP to Loci

Media companies and digital publishers often manage large image, video, or document files through FTP. These assets can be delivered to Loci so it can associate content recommendations with the correct media objects and metadata.

• Production teams upload approved media packages to FTP.
• Loci ingests the files and links them to content records.
• Personalized content modules can then surface the most relevant assets to users.

Business value: Streamlined asset distribution and more accurate content recommendations across digital channels.

4. Recommendation Performance Reporting Back to Business Teams

Flow: Loci to FTP

Loci can generate recommendation performance outputs such as top recommended items, engagement lift, content affinity scores, or segment-level results. These reports can be exported to FTP for downstream use by BI teams, marketing operations, or merchandising teams.

• Loci produces scheduled performance files.
• Files are deposited on FTP for retrieval by reporting tools or data warehouses.
• Business teams use the data to evaluate recommendation effectiveness and adjust content strategy.

Business value: Easier operational reporting and alignment between personalization teams and business stakeholders.

5. Product Catalog Synchronization for Personalized Merchandising

Flow: FTP to Loci

Retailers can send full product catalog extracts, pricing files, and inventory availability updates via FTP to Loci. This allows recommendation logic to prioritize in-stock products, seasonal items, or high-margin categories.

• Merchandising systems export catalog files nightly.
• Loci ingests the data and updates recommendation rules or content associations.
• Customers see more relevant and available products in recommendation widgets.

Business value: Improved conversion and reduced promotion of unavailable products.

6. Editorial Content Refresh for Dynamic Homepage Recommendations

Flow: FTP to Loci

Publishing and media organizations can use FTP to deliver updated editorial calendars, article metadata, and topic tags to Loci. This supports dynamic homepage or section-page recommendations based on the latest editorial priorities.

• Editors export planned content and tagging files.
• Loci processes the files and updates recommendation inputs.
• Homepage modules surface timely and relevant stories or features.

Business value: Better alignment between editorial strategy and audience engagement.

7. Secure Partner Content Exchange for Recommendation-Ready Assets

Flow: Bi-directional

Enterprises working with external content partners can use FTP for secure batch exchange of assets and metadata, while Loci consumes the incoming files and returns recommendation insights or content performance summaries. This is useful in syndicated content, affiliate commerce, and co-branded campaigns.

• Partners deliver approved content packages via SFTP.
• Loci analyzes the content and generates recommendation inputs.
• Performance summaries are exported back to partners through FTP for campaign review.

Business value: Reliable partner collaboration with measurable content performance feedback.

8. Legacy System Bridge for Personalization Enablement

Flow: FTP to Loci and Loci to FTP

Many enterprises still rely on legacy CMS, DAM, or reporting systems that only support file-based exchange. FTP can act as the bridge to move content and analytics files into Loci, enabling personalization without replacing core systems.

• Legacy systems export batch files to FTP on a fixed schedule.
• Loci ingests the files for recommendation processing.
• Updated recommendation outputs or reports are sent back through FTP for use in downstream systems.

Business value: Extends the life of legacy platforms while enabling modern personalization capabilities.