Koddi sits beside your CMS or CX/personalization platform as the decisioning and delivery layer for paid and promotional content. The CMS owns layout and publishing. The personalization platform owns the who and when. Koddi decides which ad or offer should fill a given slot, then returns a renderable payload with measurement. Here is how it typically comes together:

From your CMS

The CMS renders a page template with named slots (experiences)
On render, the CMS calls Koddi’s Winning Ads API with context, user, slot metadata, etc.
Koddi returns the winning ads creative with creative and tracking
CMS injects the returned component and publishes the page

With a CX/personalization platform added

These platforms orchestrate audiences and experience combinations
The platform calls Koddi for certain experiences and audiences, then renders the component (same as above)

Things to consider

Audience and eligibility. Your personalization tool resolves audiences. Koddi consumes audience labels and eligibility rules, for example high value shopper, and only bids or ranks advertisers eligible for that audience.
Experimentation. Use your platform to allocate traffic, holdouts, and variants. Koddi returns the ad choice inside that allocation and reports experiment IDs back for unified analysis.
Content hierarchy. CMS controls structure, for example hero, nav, editorial. Koddi fills designated commercial slots like sponsored product carousels, hero offers, or on page recommendations.

Typical build plan

Choose slots and define the contract - slot IDs, formats, fallbacks.
Wire the Winning Ads API in your CMS. Add timeouts and caching.
Register components or templates in CMS. Map to Koddi’s payload.
Connect identity and consent. Validate PII handling.
Set up measurement.
Run a dark launch with organic fallbacks. Then ramp traffic.

In Summary

Koddi works seamlessly with a variety of CMS and personalization platforms today, and our team has experience tailoring integrations to different environments. We’d be happy to get our technical team engaged to map the best integration approach for your specific stack and ensure it’s smooth for both your CMS and CX platforms.