Blog posts by Ritu Madan

Blog posts by Ritu Madan2026-07-14T19:01:56.0000000Zhttps://world.optimizely.com/blogs/ritu-madan/ Optimizely World Finding Thomas Part 4 - The Intelligence LayerI've been finding Thomas for a couple weeks now. Bear with me — we're almost at the full picture. Quick catch-up : Thomas is the returning visitor who reads everything, opens every email, converts on nothing — and one day quietly stops coming back. No warning. No signal. Just gone. In Parts 1 through 3 we built the foundation — the <a href="https://www.linkedin.com/pulse/finding-thomas-part-1-observation-post-ritu-madan-8kkwe/">CMS</a> watching him, <a href="https://www.linkedin.com/pulse/finding-thomas-part-2-recognition-engine-ritu-madan-wq2ef/">ODP</a> profiling him, <a href="https://www.linkedin.com/pulse/finding-thomas-part-3-moment-recognition-ritu-madan-5hvwe/">Personalization</a> making him feel seen for the first time. Part 4 is where it gets interesting. Because everything we've built so far has a ceiling. Someone still has to hypothesize the Thomas profile, build the segment manually, monitor the scores, and make judgment calls. At the scale of a real content ecosystem, that human dependency is the bottleneck. Opal removes the ceiling. It doesn't guess what Thomas looks like. It learns what Thomas looks like — from the behavior of every visitor who eventually stopped coming back. Then it scales that recognition to thousands of Thomas-profile users without manual intervention. There's also a productive paradox at the heart of this one: the answer to AI displacing your site traffic is AI deployed inside your own ecosystem. Part 4 makes that case. Read it <a style="color: rgb(35, 111, 161);" href="https://www.linkedin.com/pulse/finding-thomas-part-4-intelligence-layer-ritu-madan-tgvgc">here</a>.2026-07-14T19:01:56.0000000Z

Blog post

Finding Thomas Part 3 - The Moment of Recognition<h3 class="ember-view reader-text-block__heading-3">Remember Thomas?</h3> In digital landscape, Thomas is the returning visitor who reads everything, opens every email, converts on nothing. In standard reporting, he is invisible — absorbed into aggregate metrics that look healthy, precisely because he keeps showing up. In <a class="uPrscYCJahCprYhlPAURdHcDRCZBqqmbEI " style="color: rgb(35, 111, 161);" href="https://www.linkedin.com/pulse/finding-thomas-part-1-observation-post-ritu-madan-8kkwe">Part 1</a>, we talked about the CMS - how it watches Thomas's behavior, page by page, scroll by scroll, without anyone assembling that data into a story. In <a class="uPrscYCJahCprYhlPAURdHcDRCZBqqmbEI " style="color: rgb(35, 111, 161);" href="https://www.linkedin.com/pulse/finding-thomas-part-2-recognition-engine-ritu-madan-wq2ef/">Part 2</a>, we talked about ODP - how it takes that behavioral data and turns it into a real, scorable profile, complete with an Engagement Trajectory that tells you Thomas is Drifting before he's gone. Here's where we left off - the data has recognized Thomas but the experience hasn't! <h3 class="ember-view reader-text-block__heading-3">In Part 3,  we recognize Thomas and curate his experience of your site.</h3> This is where Optimizely Personalization comes into play. It translates Thomas's behavioural data profile from ODP into an experience that finally makes him feel seen without naing him or using surveillance language. Read the full story <a href="https://www.linkedin.com/pulse/finding-thomas-part-3-moment-recognition-ritu-madan-5hvwe/">here</a> on how we remove the friction points and recalibrate the experience to appreciate Thomas's loyalty.2026-06-26T17:08:48.0000000Z

Blog post

Finding Thomas Part 2 - The Recognition Engine<h3 class="ember-view reader-text-block__heading-3">Remember Thomas?</h3> In digital landscape, Thomas is the returning visitor who reads everything, opens every email, converts on nothing. In standard reporting, he is invisible — absorbed into aggregate metrics that look healthy, precisely because he keeps showing up. In <a class="txPgeVsVxoqXupMimruaYRfcYiAbVbmTSCT " href="https://www.linkedin.com/pulse/finding-thomas-part-1-observation-post-ritu-madan-8kkwe">Part 1</a>, we talked about the CMS - how Optimizely CMS is not just a publishing platform but an observation post. Every visit Thomas makes generates behavioral data - which content he reads, how deeply he scrolls, which paths he returns through, how his visit frequency is trending over time. The data is there. The problem is that most implementations are not built to read it as a story. The narrative exists. Nobody is assembling it. <h3 class="ember-view reader-text-block__heading-3">In Part 2, Thomas Becomes Visible</h3> This is where ODP takes the raw behavioral events from the CMS, stitches them together across sessions and channels, and builds a persistent, unified profile that can be segmented, scored, and acted upon. This is not a data warehouse exercise. It is a recognition exercise. Read the full story <a href="https://www.linkedin.com/pulse/finding-thomas-part-2-recognition-engine-ritu-madan-wq2ef">here</a> on how we put together an engagement trajectory for Thomas in ODP, that then helps your digital estate recognize him.2026-06-01T16:59:04.0000000Z

Blog post

Finding Thomas Part 1 - The Observation Post<div style="mso-element: para-border-div; border: none; border-bottom: solid #1A56DB 1.0pt; mso-border-bottom-alt: solid #1A56DB .5pt; padding: 0in 0in 6.0pt 0in;"> <h2 style="border: none; mso-border-bottom-alt: solid #1A56DB .5pt; padding: 0in; mso-padding-alt: 0in 0in 6.0pt 0in;">Meet Thomas</h2> </div> Thomas is the returning visitor who has been to your site forty times but has never filled out a form. He opens every newsletter but rarely clicks through. He reads your long-form content to the end while your analytics records him as just another session. He has a deep, genuine interest in the topics you cover — and an equally deep invisibility in the metrics your team reviews every week. He does not bounce. He does not unsubscribe with a parting comment. He does not leave a one-star review. He just quietly, incrementally, recalibrates whether your experience is worth his time. And when he decides it is not — when the accumulated weight of feeling unseen finally tips the balance — he stops coming. Without a word. Without a signal. We call this a recognition failure. And it's the most expensive problem in digital experiences that almost nobody is actively measuring. <div style="mso-element: para-border-div; border: none; border-bottom: solid #1A56DB 1.0pt; mso-border-bottom-alt: solid #1A56DB .5pt; padding: 0in 0in 6.0pt 0in;"> <h2 style="border: none; mso-border-bottom-alt: solid #1A56DB .5pt; padding: 0in; mso-padding-alt: 0in 0in 6.0pt 0in;">About This Series</h2> </div> Finding Thomas is a five-part series about understanding and solving this problem using the Optimizely platform. Across these posts, we follow Thomas through the full digital experience layer — what your CMS can reveal about him, what ODP can connect across his behavioral history, how Personalization can respond in ways that make him feel known, and how Opal helps teams move from insight to action at scale. Each post covers one layer of the stack. Together they trace a complete, closed-loop recognition system — one that finds Thomas before he finishes leaving, and makes him feel, for the first time, like someone noticed he was there. In Part 1 of our Finding Thomas series, we trace where this starts — and why the CMS most teams treat purely as a publishing tool is actually the first place Thomas's story can be caught before it ends. Read the full story <a style="color: rgb(35, 111, 161);" href="https://www.linkedin.com/pulse/finding-thomas-part-1-observation-post-ritu-madan-8kkwe">here</a>.  2026-05-28T14:40:53.0000000Z

Blog post

Optimizely Configured Commerce and Spire CMS - Figuring out HandlersI recently entered the world of Optimizely Configured Commerce and Spire CMS. Intriguing, interesting and challenging at the same time, especially when my past experience had been with traditional Optimizely CMS and Customized Commerce. The idea is the same, but the implementation is quite different. So yes it becomes a bit daunting, to forget old ways and get used to these new ones.  But I believe in learning on the job, so figuring things out sort of comes as part of the deal. This time, my challenge lies around figuring out how frontend handlers work in Spire CMS, where code lives, where should I intercept and tweak. Read below for the full story on how I went about this learning. <a href="https://blogs.perficient.com/2025/03/10/optimizely-b2b-commerce-and-spire-cms-figuring-out-handlers/">https://blogs.perficient.com/2025/03/10/optimizely-b2b-commerce-and-spire-cms-figuring-out-handlers/</a> Hoping to share more such learning as I gain them. :)2025-03-12T19:33:49.0000000Z

Blog post

Decoding DI in Optimizely CMS 12DI or Dependency Injection is a complex topic, not just in Optimizely CMS, but in general in .net core implementations. Some aspects we get, like the different ways dependencies can be injected and which is better over others, while some leave us scratching our heads. Often times we end up doing a lot of troubleshooting, digging into internal code and finding the right alternatives to DI, to get things to work. The biggest blocker here is understanding the order in which steps get executed, modules get initialized and services get registered. Once this is clear, we know where to add our custom code and avoid any surprise runtime errors around missing service registrations. One such error led me to this discovery so sharing my findings and learnings. Read the complete post <a href="https://blogs.perficient.com/2024/01/23/decoding-di-in-optimizely-cms-12/">here </a>for details.2024-01-23T21:31:43.0000000Z

Blog post

Custom form element with dependenciesEpiserver Forms are cool as is. They provide solid ground to build basic forms out of the box. But often times, we have custom needs that require us to customize or add to the out of the box functionality. In my case, I needed a custom form element that can support some unique requirements and at the same time I needed this to support the built in dependency logic. For those of you unfamiliar with the forms dependency logic, see the Optimizely document <a href="https://support.optimizely.com/hc/en-us/articles/4413192345101-Form-element-types#DependenciesTab">here</a>. Read the complete blog <a href="https://blogs.perficient.com/2024/01/17/optimizely-cms-custom-form-element-with-dependencies/">here </a>for all the fun details on how this was achieved with minor code tweaks.2024-01-17T18:26:42.0000000Z

Blog post

Special symbols in TinyMCETinyMCE has evolved over the years, allowing more and more flexibility with the features it offers and capabilities it allows to customize. And this is pretty handy as every client has their unique needs and requirements for what they want their Rich Text Editors to do. My use case - pretty straightforward - among the many customizations already on, we needed to accommodate very special symbols in the RTE. Now I'm not the first person to present this need ofcourse, which is why TinyMCE already had a plugin called Charmap that contains a whole ensemble of special symbols to use from. And talk about flexibility, it also gives you, the developer, the capability to customize this plugin and add more symbols to it, in case yours are not in the preset list. And, what do you know.. not all of mine made the preset list cut, ofcourse! :) So, I added them in there. Read the complete post <a href="https://blogs.perficient.com/2024/01/10/working-with-special-symbols-in-tinymce/">here</a> to find out exactly how! There are some good to know details in there for sure. 2024-01-10T23:27:54.0000000Z

Blog post

Optimizely CMS 12 Upgrade takeawaysI've now gone through multiple CMS 12 upgrade projects. Each project had its own unique customizations and hence its own unique set of challenges when upgrading. I learnt something new, overcame a new hurdle, found/solved a new problem with every project. Some took quite a bit of time and synergy with Opti community, some back and forth on Opti support tickets, and solutions from other MVPs. So I thought it would be nice to put them all together in one place, for others on their upgrade journey, looking for same or similar solutions. So here goes : This <a href="https://blogs.perficient.com/2023/02/17/optimizely-cms-12-unique-upgrade-challenges/">first blog post</a> talks about things like Marketing connector and Visitor group related issues. This <a href="https://blogs.perficient.com/2023/07/27/optimizely-cms-12-takeaways">second one</a> talks about small nitty gritty, more generic things, but if you don't know about them, they can end up giving you massive headaches. Hope you find this one stop post helpful! I am looking forward to hear other's upgrade stories and challenges faced/resolved, so please do share in comments if you encountered something unique.2023-08-01T20:01:40.0000000Z

Blog post

Icon Library in Optimizely CMSIcons are graphical representations of different elements on a website. They make the webpages visually appealing and like any other image, have a stronger connection and retention to the end user’s memory than plain text. When used in moderation and the right way, they can be self-explanatory and reduce the need for text content in a lot of use cases. Icon Library is basically a curated list/dictionary of icons that ties an icon to a meaningful name. This library can then be used to pick icons for the different elements of the website. A good use case would be websites that use icons heavily and need to give CMS Editors control to pick icons with content within CMS, in a way that's well in line with the site's theme and design as well as maintains consistency in terms of meaning and usage. It also allows to have dedicated user roles that control the creation and modification of the actual Icon Library, so they can ensure the icons added are per design and theme and that other user roles can't mess the list up. And by providing a select list of the icon library on content types, instead of a ContentReference property where any media can be added, it can be ensured that no icons outside of this curated list are added to content. Please see my detailed post <a href="https://blogs.perficient.com/2023/05/15/icon-library-in-optimizely-cms/">here </a>on how to setup the Icon Library and then use it in CMS.2023-05-15T21:20:56.0000000Z

Blog post

Bitbucket CI/CD pipelines for Optimizely CMS 12Recently, we had a client with code repository hosted on Bitbucket and they showed interest in setting up CI/CD pipelines for automating Optimizely CMS deployments from within Bitbucket. When I started researching, I found several blog posts and documentation around building Azure Devops pipelines for Optimizely CMS deployments. But none that would guide us through building Optimizely CI/CD pipelines in Bitbucket. So after spending quite some time understanding Bitbucket pipeline basics, a lot of trial and error and help from other fellow colleagues, I was able to setup a Bitbucket CI/CD build pipeline for my project. This exercise was quite the learning as it wasn't just Bitbucket pipeline specific. I learnt Bash and Powershell scripting. I learnt how Azure Devops and Bitbucket pipelines are so drastically and syntactically different from each other. I also learnt that this effort needed sharing, because this topic is relevant and very much in need of more readily available, one stop shop content. Hopefully, after this, others on the same path won't have to spend as much time figuring smaller pieces and syntax for Bitbucket pipelines like I did. Please follow along to the detailed blog <a href="https://blogs.perficient.com/2023/05/05/bitbucket-ci-cd-pipelines-for-optimizely-cms-12/">here</a>, providing step by step breakdown of the Bitbucket pipeline code. I will look forward to feedback and recommendation from others here, to make this better.2023-05-05T20:10:20.0000000Z

Blog post

Optimizely CMS 12 – Unique upgrade challengesBy now, a lot of us have already participated in one or more CMS 12 upgrade projects. The others are still evaluating whether they should do it now or wait some more. Regardless of when you do it, there will definitely be some unique upgrade challenges you will come across, as I and many others […]2023-02-17T20:56:45.0000000Z

Blog post

Optimizely CMS – the importance of GUIDs and Assembly NamesIn Optimizely CMS world, we see GUIDs everywhere. They are the unique identifiers for content types and more. As part of developing with Optimizely CMS, developers are advised to always specify GUIDs in there Content Type declarations. If one isn’t specified, the DB assigns one dynamically when saving the Content type. A big reason for […]2022-08-16T16:34:16.0000000Z

Blog post

Optimizely CMS 12 – Dependency Injection(DI) – StructureMap vs ASP.Net CoreIf you are upgrading to Optimizely CMS 12, one of the breaking changes to consider is the change to the Dependency Injection(DI) framework. Earlier versions of Optimizely CMS had their own DI hosting framework that supported other concrete DI implementations, like StructureMap. With CMS 12 and ASP.Net Core, DI framework is built into the system. […]2022-06-30T19:43:59.0000000Z

Blog post

Optimizely Page Publish Options – Do’s and Dont’sPage Publish is the most basic feature of a CMS. This is what makes our content visible to the world. Episerver CMS (now known as Optimizely Content Cloud) too has the feature and some more flexibility built around it to aid our content authors. There’s the usual page publish, where you hit a button and […]2022-05-13T13:58:55.0000000Z

Blog post

Optimizely Search : How to search for all expired assetsFirst of all, I want to mention that EPiServer Find (now known as Optimizely Search and Navigation) is a great tool to search for content on an Optimizely site, whether its CMS or Commerce. It comes with a range of options to customize and with filtering and boosting ability to get the best results. Often […]2022-05-03T14:41:05.0000000Z

Blog post

Kathryn Bogen Recognized on 2022 CRN Women of the Channel ListCRN’s annual Women of the Channel program honors some of the most influential women leaders within the channel. We’re proud to have five Perficient colleagues recognized in the 2022 CRN Women of the Channel list, and we’re highlighting their individual accomplishments in a special blog series. We previously celebrated Liza Sisler, Liz Stuart, and Lynn […]2012-05-19T18:06:00.0000000Z

Blog post