Perficient is proud to be included in the IDC Market Glance: Digital Business Professional Services, 3Q25, (Doc # US52789825, July 2025)”. This marks our fourth consecutive year of inclusion.

In the report, Perficient is included in the Technology Transformation Dominant category, where IDC defines participants as: “organizations [that] offer technology consulting advice and services as their primary service line to drive digital transformation.”

Built to Lead with Technology

IDC notes: “Many technology transformation dominant firms also offer business consulting services, and some are expanding their capabilities into design services and product engineering services as well.”

This aligns with our evolution as a consulting partner. At Perficient, we integrate strategy, implementation, and innovation, giving clients the technology foundations and AI readiness to accelerate transformation and achieve tangible outcomes.

An Industry in Motion

The report also highlights a key trend shaping the digital business consulting landscape:

“Acquisitions to boost AI/cloud/digital capabilities and to fill niche areas of expertise.”

Perficient’s strategic investments reflect this shift. We continue to deepen our AI-first capabilities, expand our industry expertise, and deliver consulting services grounded in execution.

Strategy to Execution, Powered by AI

Technology transformation at Perficient is built for scale, speed, and strategy. We help enterprises modernize platforms, streamline architectures, and align technology investments to real business outcomes. Our AI-powered Envision experience connects strategy to execution, combining proven frameworks with intelligent tools that help leaders prioritize, activate, and accelerate transformation. From capability mapping to platform selection, Envision turns insight into action and helps organizations move faster with confidence.

Ready to move from ambition to impact? Let’s define your AI-first strategy and build the foundation to lead what’s next.

Migrating a website or upgrading to a new Sitecore platform is more than a technical lift — it’s a business transformation and an opportunity to align your site and platform with your business goals and take full advantage of Sitecore’s capabilities. A good migration protects functionality, reduces risk, and creates an opportunity to improve user experience, operational efficiency, and measurable business outcomes.

Before jumping to the newest version or the most hyped architecture, pause and assess. Start with a thorough discovery: review current architecture, understand what kind of migration is required, and decide what can realistically be reused versus what should be refactored or rebuilt, along with suitable topology and Sitecore products.

This blog expands the key considerations before committing to a Sitecore-specific migration, translating them into detailed, actionable architecture decisions and migration patterns that guide impactful implementation.

1) Clarifying client requirements

Before starting any Sitecore migration or implementation, it’s crucial to clarify client’s requirements thoroughly. This ensures the solution aligns with actual business needs, not just technical requests and helps avoid rework or misaligned outcomes.

Scope goes beyond just features: Don’t settle for “migrate this” as the requirement. Ask deeper questions to shape the right migration strategy:

• Business goals: Is the aim a redesign, conversion uplift, version upgrade, multi-region rollout, or compliance?
• Functional scope: Are we redesigning the entire site or specific flows like checkout/login, or making back office changes?
• Non-functional needs: What are the performance SLAs, uptime expectations, compliance (e.g.: PCI/GDPR), and accessibility standards?
• Timeline: Is a phased rollout preferred, or a big-bang launch?

Requirements can vary widely, from full redesigns using Sitecore MVC or headless (JSS/Next.js), to performance tuning (caching, CDN, media optimization), security enhancements (role-based access, secure publishing), or integrating new business flows into Sitecore workflows.
Sometimes, the client may not fully know what’s needed, it’s up to us to assess the current setup and recommend improvements. Don’t assume the ask equals the need, A full rewrite isn’t always the best path. A focused pilot or proof of value can deliver better outcomes and helps validate the direction before scaling.

2) Architecture of the client’s system

Migration complexity varies significantly based on what the client is currently using. You need to evaluate current system and its uses and reusability.

Key Considerations

• If the client is already on Sitecore, the version matters. Older versions may require reworking the content model, templates, and custom code to align with modern Sitecore architecture (e.g.: SXA, JSS).
• If the client is not on Sitecore, evaluate their current system, infrastructure, and architecture. Identify what can be reused—such as existing servers(in case of on-prem), services, or integrations—to reduce effort.
• Legacy systems often include deprecated APIs, outdated connectors, or unsupported modules, which increase technical risk and require reengineering.
• Historical content, such as outdated media, excessive versioning, or unused templates, can bloat the migration. It’s important to assess what should be migrated, cleaned, or archived.
• Map out all customizations, third-party integrations, and deprecated modules to estimate the true scope, effort, and risk involved.
• Understanding the current system’s age, architecture, and dependencies is essential for planning a realistic and efficient migration path.

3) Media Strategy

When planning a Sitecore migration or upgrade, media handling can lead to major performance issues post-launch. These areas are critical for user experience, scalability, and operational efficiency, so they need attention early in the planning phase. Digital Asset Management (DAM) determines how assets are stored, delivered, and governed.

Key Considerations

• Inventory: Assess media size, formats, CDN references, metadata, and duplicates. Identify unused assets, and plat to adopt modern formats (e.g., WebP).
• Storage Decisions: Analyze and decide whether assets stay in Sitecore Media Library, move to Content Hub, or use other cloud storage (Azure Blob, S3)?
• Reference Updates: Plan for content reference updates to avoid broken links.

4) Analytics, personalization, A/B testing, and forms

These features often carry stateful data and behavioral dependencies that can easily break during migration if not planned for. Ignoring them can lead to data loss and degraded user experience.

Key Considerations

• Analytics: Check if xDB, Google Analytics, or other trackers are in use? Decide how historical analytics data will be preserved, validated, and integrated into the new environment?
• Personalization: Confirm use of Sitecore rules, xConnect collections, or an external personalization engine. Plan to migrate segments, conditions, and audience definitions accurately.
• A/B Testing & Experiments: Draft a plan to export experiment definitions and results is present.
• Forms: Analyze which forms collects data, and how do they integrate with CRM or marketing automation?

Above considerations play important role in choosing Sitecore topology, if there is vast use of analytics XP makes a suitable option, forms submission consent flows have different approach in different topologies.

5) Search Strategy

Search is critical for user experience, and a migration is the right time to reassess whether your current search approach still makes sense.

Key Considerations

• Understand how users interact with the site, Is search a primary navigation tool or a secondary feature? Does it significantly impact conversion or engagement?
• Identify current search engine if any. Access its features, if advanced capabilities like AI recommendations, synonyms, or personalization being used effectively.
• If the current engine is underutilized, note that maintaining it may add unnecessary cost and complexity. If search is business-critical, ensure feature parity or enhancement in the new architecture.
• Future Alignment:  Based on requirements, determine whether the roadmap supports:

• • Sitecore Search (SaaS) for composable and cloud-first strategies.
  • Solr for on-prem or PaaS environments.
  • Third-party engines for enterprise-wide search needs.

6) Integrations, APIs & Data Flows

Integrations are often the hidden complexity in Sitecore migrations. They connect critical business systems, and any disruption can lead to post-go-live incidents. For small, simple content-based sites with no integrations, migrations tend to be quick and straightforward. However, for more complex environments, it’s essential to analyze all layers of the architecture to understand where and how data flows. This includes:

Key Considerations

• Integration Inventory: List all synchronous and asynchronous integrations, including APIs, webhooks, and data pipelines. Some integrations may rely on deprecated endpoints or legacy SDKs that need refactoring.
• Criticality & Dependencies: Identify mission-critical integrations (e.g.: CRM, ERP, payment gateways).
• Batch & Scheduled Jobs: Audit long-running processes, scheduled exports, and batch jobs. Migration may require re-scheduling or re-platforming these jobs.
• Security & Compliance: Validate API authentication, token lifecycles, and data encryption. Moving to SaaS or composable may require new security patterns.

7) Identify Which Sitecore offerings are in use — and to what extent?

Before migration, it’s essential to document the current Sitecore ecosystem and evaluate what the future state should look like. This determines whether the path is a straight upgrade or a transition to a composable stack.

Key Considerations

• Current Topology: Is the solution running on XP or XM? Assume that XP features (xDB, personalization) may not be needed if moving to composable.
• Content Hub: Check if DAM or CMP is in use. If not, consider whether DAM is required for centralized asset management, brand consistency, and omnichannel delivery.
• Sitecore Personalize & CDP: Assess if personalization is currently rule-based or if advanced testing and segmentation are required.
• OrderCloud: If commerce capabilities exist today or are planned in the near future.

Target Topologies

This is one of the most critical decisions is choosing the target architecture. This choice impacts infrastructure, licensing, compliance, authoring experience, and long-term scalability. It’s not just a technical decision—it’s a business decision that shapes your future operating model.

Key Considerations

• Business Needs & Compliance: Does your organization require on-prem hosting for regulatory reasons, or can you move to SaaS for agility?
• Authoring Experience: Will content authors need Experience Editor, or is a headless-first approach acceptable?
• Operational Overhead: How much infrastructure management can team handle post-migration?
• Integration Landscape: Are there tight integrations with legacy systems that require full control over infrastructure?

Architecture Options & Assumptions

Along with topology its important to consider hosting and frontend delivery platform. Lets look at available hosting options with their pros and cons:

• On-Prem(XM/XP): You can build the type of machine that you want.
  • Pros: Maximum control, full compliance for regulated industries, and ability to integrate with legacy systems.
  • Cons: High infrastructure cost, slower innovation, and manual upgrades, difficult to scale.
  • Best For: Organizations with strict data residency, air-gapped environments, or regulatory mandates.
  • Future roadmap may require migration to cloud, so plan for portability.
• PaaS (Azure App Services, Managed Cloud – XM/XP)
  • Pros: Minimal up-front costs and you do not need to be concerned about the maintenance of the underlying machine.
  • Cons: Limited choice of computing options and functionality.
  • Best For: Organizations expecting to scale vertically and horizontally, often and quickly
• IaaS (Infrastructure as a service – XM/XP)
  • This is same as on-premise, but with VMs you can tailor servers to meet your exact requirements.
• SaaS (XM Cloud)
  • Pros: Zero infrastructure overhead, automatic upgrades, global scalability.
  • Cons: Limited deep customization at infra level.
  • Best For: Organizations aiming for composable DXP and agility.
  • Fully managed by Sitecore (SaaS).

For development, you have different options for example: .Net MVC, .Net Core, Next JS, React. Depending on topology suggested, selection of frontend delivery can be hybrid or headless:

.NET MVC → For traditional, web-only application.
Headless → For multi-channel, composable, SaaS-first strategy.
.NET Core Rendering → For hybrid modernization with .NET.

8) Security, Compliance & Data Residency

Security is non-negotiable during any Sitecore migration or upgrade. These factors influence architecture, hosting choices and operational processes.

Key Considerations

• Authentication & Access: Validate SSO, SAML/OAuth configurations, API security, and secrets management. Assume that identity providers or token lifecycles may need reconfiguration in the new environment.
• Compliance Requirements: Confirm obligations like PCI, HIPAA, GDPR, Accessibility and regional privacy laws. Assume these will impact data storage, encryption, and as AI is in picture now a days it will even have impact on development workflow.
• Security Testing: Plan for automated vulnerability scans(decide tools you going to use for the scans) and manual penetration testing as part of discovery and pre go-live validation.

9) Performance

A migration is the perfect opportunity to identify and fix structural performance bottlenecks, but only if you know your starting point. Without a baseline, it’s impossible to measure improvement or detect regressions.

Key Considerations

• Baseline Metrics: Capture current performance indicators like TTFB (Time to First Byte), LCP (Largest Contentful Paint), CLS (Cumulative Layout Shift), throughput, and error rates. These metrics will guide post-migration validation and SLA commitments.
• Caching & Delivery: Document existing caching strategies, CDN usage, and image delivery methods. Current caching patterns may need reconfiguration in the new architecture.
• Load & Stress Testing: Define peak traffic scenarios and plan load testing tools with Concurrent Users and Requests per Second.

10) Migration Strategies

Choosing the right migration strategy is critical to balance risk, cost, and business continuity. There’s no one size fits all approach—your suggestion/choice depends on timeline, technical debt and operational constraints.

Common Approaches

• • Lift & Shift
    Move the existing solution as is with minimal changes.
    This is low-risk migrations where speed is the priority. When the current solution is stable and technical debt is manageable.
    However with this approach the existing issues and inefficiencies stays as is which can be harmful.

• • Phased (Module-by-Module)
    Migrate critical areas first (e.g.: product pages, checkout) and roll out iteratively.
    This can be opted for large, complex sites where risk needs to be minimized, when business continuity is critical.
    With this approach, timelines are longer and requires dual maintenance during transition.

• • Rewrite & Cutover
    Rebuild the solution from scratch and switch over at once.
    This is can be chosen when the current system doesn’t align with future architecture. When business wants a clean slate for modernization.

Above options can be suggested based on several factors whether business tolerate downtime or dual maintenance. What are the Timelines, What’s the budget. If the current solution worth preserving, or is a rewrite inevitable? Does the strategy align with future goals?

Final Thoughts

Migrating to Sitecore is a strategic move that can unlock powerful capabilities for content management, personalization, and scalability. However, success lies in the preparation. By carefully evaluating your current architecture, integration needs and team readiness, you can avoid common pitfalls and ensure a smoother transition. Taking the time to plan thoroughly today will save time, cost, and effort tomorrow setting the stage for a future-proof digital experience platform.

Modern Healthcare has once again recognized Perficient among the largest healthcare management consulting firms in the U.S., ranking us ninth in its 2025 survey. This honor reflects not only our growth but also our commitment to helping healthcare leaders navigate complexity with clarity, precision, and purpose.

What’s Driving Demand: Innovation with Intent

As provider, payer, and MedTech organizations face mounting pressure to modernize, our work is increasingly focused on connecting digital investments to measurable business and health outcomes. The challenges are real—and so are the opportunities.

Healthcare leaders are engaging our experts to tackle shifts from digital experimentation to enterprise alignment in business-critical areas, including:

• Digital health transformation that eases access to care.
• AI and data analytics that accelerate insight, guide clinical decisions, and personalize consumer experiences.
• Workforce optimization that supports clinicians, streamlines operations, and restores time to focus on patients, members, brokers, and care teams.

These investments represent strategic maturity that reshapes how care is delivered, experienced, and sustained.

Operational Challenges: Strategy Meets Reality

Serving healthcare clients means working inside a system that resists simplicity. Our industry, technical, and change management experts help leaders address three persistent tensions:

1. Aligning digital strategy with enterprise goals. Innovation often lacks a shared compass. We translate divergent priorities—clinical, operational, financial—into unified programs that drive outcomes.
2. Controlling costs while preserving agility. Budgets are tight, but the need for speed and competitive relevancy remains. Our approach favors scalable roadmaps and solutions that deliver early wins and can flex as the health care marketplace and consumer expectations evolve.
3. Preparing the enterprise for AI. Many of our clients have discovered that their AI readiness lags behind ambition. We help build the data foundations, governance frameworks, and workforce capabilities needed to operationalize intelligent systems.

Related Insights: Explore the Digital Trends in Healthcare

Consumer Expectations: Access Is the New Loyalty

Our Access to Care research, based on insights from more than 1,000 U.S. healthcare consumers, reveals a fundamental shift: if your healthcare organization isn’t delivering a seamless, personalized, and convenient experience, consumers will go elsewhere. And they won’t always come back.

Many healthcare leaders still view competition as other hospitals or clinics in their region. But today’s consumer has more options—and they’re exercising them. From digital-first health experiences to hyper-local disruptors and retail-style health providers focused on accessibility and immediacy, the competitive field is rapidly expanding.

• Digital convenience is now a baseline. More than half of consumers who encountered friction while scheduling care went elsewhere.
• Caregivers are underserved. One in three respondents manage care for a loved one, yet most digital strategies treat the patient as a single user.
• Digital-first care is mainstream. 45% of respondents aged 18–64 have already used direct-to-consumer digital care, and 92% of those adopters believe the quality is equal or better to the care offered by their regular health care system.

These behaviors demand a rethinking of access, engagement, and loyalty. We help clients build experiences that are intuitive, inclusive, and aligned with how people actually live and seek care.

Looking Ahead: Complexity Accelerates

With intensified focus on modernization, data strategy, and responsible AI, healthcare leaders are asking harder questions. We’re helping them find and activate answers that deliver value now and build resilience for what’s next.

Our technology partnerships with Adobe, AWS, Microsoft, Salesforce, and other platform leaders allow us to move quickly, integrate deeply, and co-innovate with confidence. We bring cross-industry expertise from financial services, retail, and manufacturing—sectors where personalization and operational excellence are already table stakes. That perspective helps healthcare clients leapfrog legacy thinking and adopt proven strategies. And our fluency in HIPAA, HITRUST, and healthcare data governance ensures that our digital solutions are compliant, resilient, and future-ready.

Optimized, Agile Strategy and Outcomes for Health Insurers, Providers, and MedTech

Discover why we been trusted by the 10 largest U.S. health systems, 10 largest U.S. health insurers, and 14 of the 20 largest medical device firms. We are recognized in analyst reports and regularly awarded for our excellence in solution innovation, industry expertise, and being a great place to work.

Contact us to explore how we can help you forge a resilient, impactful future that delivers better experiences for patients, caregivers, and communities.

On the hundredth anniversary of its circulation, Automotive News launched a series on the technological innovations driving the shift to “software-defined vehicles” (SDVs). The articles explore the fragmented U.S. roadmap to software integration, intensifying global competition, OEM progress to date, and the uncertainties shaping automakers’ strategies. 

This coverage signals an evolution. As automakers race to redefine themselves as technology companies, the industry is grappling with how software will reshape value, competition, and consumer trust. 

Perficient’s Connected Products Research Provides Clarity 

At Perficient, our latest connected products research “Build a Powerful Connected Products Strategy” adds a critical layer of data to the SDV conversation: distinguishing not what automakers think matters most — but what consumers actually care about.

“OEMs are making strategic bets on software-defined vehicles, but consumers are weighing very different factors when making purchase decisions. The gap between those perspectives is significant — and closing it is critical,” said Justin Huckins, Director, Strategy, Automotive Industry Lead.  

This difference matters. OEMs navigating still-undefined SDV pathways need data-based consumer signals to guide product architecture, user experience, data governance, and connected services. Otherwise, they risk widening the gap between industry emphasis and end-user expectations. 

Four Key Insights: Where Automakers and Consumers Diverge 

Our research gathered perspectives from 1,307 respondents including consumers, OEMs, and manufacturers, surfacing a series of misalignments: 

1. Trust is the top consumer priority, but not for manufacturers. Only 22% of manufacturers flagged “trust” as a critical factor in adoption — yet consumers consistently rank it #1. 
2. Consumers don’t feel informed about data collection. Despite widespread anxiety about data privacy, only 19% of consumers feel fully aware of what their vehicles are collecting. 
3. Experience outweighs engineering. “Consumers are more worried about the experience than the engineering. OEMs often enter the connected space for internal reasons — field data, R&D — but buyers expect tangible value in everyday use,” said Kevin Espinosa, Director, Strategy, Manufacturing Industry Lead. 
4. Integration matters. 38% of consumers highlighted integration with other connected devices as a key feature. This points to expectations of seamless cross-device ecosystems — from vehicles to homes to mobile apps. 

Why this Research Matters in the Race to Software Defined Vehicles 

• Trust as a foundation: Software-defined vehicles amplify consumer concerns around data handling, privacy, and transparency.  “It’s alarming that manufacturers and their customers don’t value trust in the same way,” said Jim Hertzfeld, Area Vice President. Trust is no longer a secondary issue; it’s the foundation for adoption. 

• The global race, China’s edge & collaboration: As Automotive News highlights, China’s accelerated SDV progress creates global pressure. Collaborative development models will only succeed if OEMs align around consumer trust and clarity. 

• Roadmap clarity through consumer signals: With the SDV roadmap still fuzzy, consumer insights provide directional clarity on where to invest — from UX and subscriptions to data governance and operating models. “OEMs are looking to monetize, but customers are looking for better experiences. Whoever reconciles that disconnect first will lead the next wave of SDVs,” added Justin. 

Shaping SDV Strategies Around What Buyers Value 

As the SDV era accelerates — with new architectures, shared development models, and software updates over the air — aligning strategy with consumer expectations around transparency and privacy will be just as important as the technology itself.  

Leveraging our position as the global AI-first consultancy, Perficient partners with Fortune 2000 companies across industries—healthcare, financial services, manufacturing, and more—to digitize operations, modernize with cloud and AI, and unlock insights from connected data platforms. That cross-industry vantage point matters, because there are now more connected products in the world than people, and vehicles are becoming one of the most important nodes in this ecosystem. 

If you’re exploring how SDV strategies can be shaped by what buyers truly value, our research offers a tangible perspective. Download Build a Powerful Connected Products Strategy or schedule an interview with our industry leaders to discuss how consumer insights can inform your software defined vehicle strategy.

Balancing AI Strategy With Human Wisdom 

“AI-first” has become a buzzword in executive conversations, but what does it really mean? Is it about using artificial intelligence at every turn, or applying it with intention and purpose? For analyst and researcher Susan Etlinger, it’s clearly the latter. 

On the latest episode of “What If? So What?”, Susan joins host Jim Hertzfeld to explore what it takes to build AI strategies that are both innovative and responsible. With a background that bridges the humanities and technology, she makes a compelling case for the critical role of human insight in an AI-driven world. 

When (and When Not) to Automate 

AI’s power lies not just in what it can do, but in knowing when not to use it. Susan argues that leaders must assess whether automation truly improves outcomes or risks eliminating valuable learning opportunities. 

She shares a story from early in her career, when manually compiling business data helped her develop essential skills like stakeholder management, strategic thinking, and financial literacy. Her point: AI can accelerate, but only human experience gives results meaning. 

From Generative to Agentic AI: Who’s in Control? 

The conversation explores the evolution from machine learning to Generative AI, and now to Agentic AI. Susan encourages leaders to ask:  

Who sets the goals? Who ensures alignment?  

While AI agents can handle tasks from start to finish, intention, ethics, and judgment remain the responsibility of humans. 

Smarter AI Strategies, Not Just More AI 

Susan’s key takeaway is clear:  

Organizations don’t need more AI; they need better AI strategies. 

Start with a clear use case, implement with intention, and learn from the outcome. The most effective approaches respect the limits of automation while amplifying human strengths. 

Keep People at the Center of Your AI Strategy 

For leaders shaping AI strategy, Susan offers a clear reminder:  progress isn’t about replacing human decision making, it’s about enhancing it. AI can accelerate outcomes, but it’s people who ensure those outcomes are purposeful, ethical, and aligned to your business goals. 

Listen to the full conversation

Subscribe Where You Listen

Apple | Spotify | Amazon | Overcast | Watch the full video episode on YouTube

Meet our Guest – Susan Etlinger

Susan Etlinger is a globally recognized expert on the business and societal impact of data and artificial intelligence and senior fellow at the Centre for International Governance Innovation, an independent, non-partisan think tank based in Canada. Her TED talk, “What Do We Do With All This Big Data?” has been translated into 25 languages and has been viewed more than 1.5 million times. Her research is used in university curricula around the world, and she has been quoted in numerous media outlets including The Wall Street Journal, The Atlantic, The New York Times and the BBC. Susan holds a Bachelor of Arts in Rhetoric from the University of California at Berkeley. 

Follow Susan on LinkedIn  

Learn More about Susan Etlinger

Meet our Host

Jim Hertzfeld is Area Vice President, Strategy for Perficient.

For over two decades, he has worked with clients to convert market insights into real-world digital products and customer experiences that actually grow their business. More than just a strategist, Jim is a pragmatic rebel known for challenging the conventional and turning grand visions into actionable steps. His candid demeanor, sprinkled with a dose of cynical optimism, shapes a narrative that challenges and inspires listeners.

Connect with Jim:

LinkedIn | Perficient

In today’s hyper-personalized digital world, delivering the right message to the right customer at the right time is non-negotiable. 

Adobe Commerce is a powerful eCommerce engine, but when coupled with Adobe Real-Time CDP (Customer Data Platform), it evolves into an intelligent experience machine, which is capable of deep AI-powered personalization, dynamic segmentation, and real-time responsiveness. 

What is Adobe Real-Time CDP? 

Adobe Real-Time CDP is a Customer Data Platform that collects and unifies data across various sources (websites, apps, CRM, etc.) into a single, comprehensive real-time customer profile. This data is then accessible to other systems for marketing, sales, and service. 

Key Capabilities of Real-time CDP

• Real-time data ingestion and activation.  
• Identity resolution across devices and platforms 
• AI-driven insights and audience segmentation 
• Data governance and privacy compliance tools 

Why Integrate Adobe Commerce with Adobe CDP? 

Adobe Commerce offers native customer segmentation, but it’s limited to session or behavior data within the commerce environment. When the customer data is vast, the native segmentation becomes very slow, impacting overall performance.  

What We Gain with Real-Time CDP

Use Cases

1. Win-back Campaign: Identify dormant users in CDP and activate personalized discounts  
2. Cart Recovery: Capture cart abandonment events. 
3. High-Intent Buyers: Target customers who browse premium products but didn’t convert 

Integration of Adobe Commerce with Adobe Real-Time CDP 

Data Layer Implementation

• Install Adobe Experience Platform Web SDK to enable real-time event tracking and identity collection.  
• Define and deploy a custom XDM schema aligned with Commerce events. 

Customer Identity Mapping

• Implement Adobe Identity Service to build unified customer profiles across anonymous and logged-in sessions. 
• Ensure login/signup events are tracked for persistent identification. 

Data Collection Configuration

• Tag key Commerce events (add to cart, purchase, product) to collect data. 
• Set up batch or streaming ingestion using the following extensions: 
  • audiences-activation 
  • experience-platform-connector
• Admin configuration for Organization ID, Dataset ID & Data Stream ID:  
  • System -> Services -> Data Connection 
  • System -> Services -> Commerce Service Connector 

Audience Segmentation & Activation

• Create dynamic audiences using behavioral, transactional, and CRM data.  
• Assign Audience in Adobe Commerce. 

Personalization Execution

• Leverage Adobe Target or Adobe Experience Manager (AEM) to serve personalized content.
• CDP can be used for decision making, like suppressing offers to churn customers. 

Challenges to Consider 

• Data Governance: Ensure GDPR/CCPA compliance with CDP’s consent management tools. 
• Identity Resolution Complexity: Work closely with marketing teams to define identity rules. 
• Cross-Team Collaboration: Integration touches data engineering, commerce, marketing, and legal teams.

Conclusion 

Integrating Adobe Commerce with CDP empowers both business and technical teams to unify profiles and stay ahead in a dynamic marketplace by delivering personalization.  

Adobe Real-Time CDP is not just a marketing tool, it’s an asset for creating commerce experiences that adapt to the customer in real-time.   

The pressure is on for healthcare organizations to deliver more—more value, more equity, more impact. That’s where a well-known approach is stepping back into the spotlight.

If you’ve been around healthcare conversations lately, you’ve probably heard the resurgence of term value-based care. And there’s a good reason for that. It’s not just a buzzword—it’s reshaping how we think about health, wellness, and the entire care experience.

What Is Value-Based Care, Really?

At its core, value-based care is a shift away from the old-school fee-for-service model, where providers got paid for every test, procedure, or visit, regardless of whether it actually helped the patient. Instead, value-based care rewards providers for delivering high-quality, efficient care that leads to better health outcomes.

It’s not about how much care is delivered, it’s about how effective that care is.

This shift matters because it places patients at the center of everything. It’s about making sure people get the right care, at the right time, in the right setting. That means fewer unnecessary tests, fewer duplicate procedures, and less of the fragmentation that’s plagued the system for decades.

The results? Better experiences for patients. Lower costs. Healthier communities.

Explore More: Access to Care Is Evolving: What Consumer Insights and Behavior Models Reveal

Benefits and Barriers of Value-Based Care in Healthcare Transformation

There’s a lot to be excited about, and for good reason! When we focus on prevention, chronic disease management, and whole-person wellness, we can avoid costly hospital stays and emergency room visits. That’s not just good for the healthcare system, it’s good for people, families, and communities. It moves us closer to the holy grail in healthcare: the quintuple aim. Achieving it means delivering better outcomes, elevating experiences for both patients and clinicians, reducing costs, and advancing health equity.

The challenge? Turning value-based care into a scalable, sustainable reality isn’t easy.

Despite more than a decade of pilots, programs, and well-intentioned reforms, only a small number of healthcare organizations have been able to scale their value-based care models effectively. Why? Because many still struggle with some pretty big roadblocks—like outdated technology, disconnected systems, siloed data, and limited ability to manage risk or coordinate care.

That’s where digital transformation comes in.

To make value-based care real and sustainable, healthcare organizations are rethinking their infrastructure from the ground up. They’re adopting cloud-based platforms and interoperable IT systems that allow for seamless data exchange across providers, payers, and patients. They’re tapping into advanced analytics, intelligent automation, and AI to identify at-risk patients, personalize care, and make smarter decisions faster.

As organizations work to enable VBC through digital transformation, it’s critical to really understand what the current research says. Our recent study, Access to Care: The Digital Imperative for Healthcare Leaders, backs up these trends, showing that digital convenience is no longer a differentiator—it’s a baseline expectation.

Findings show that nearly half of consumers have opted for digital-first care instead of visiting their regular physician or provider.

This shift highlights how important it is to offer simple and intuitive self-service digital tools that help people get what they need—fast. When it’s easy to find and access care, people are more likely to trust you, stick with you, and come back when they need you again.

You May Also Enjoy: How Innovative Healthcare Organizations Integrate Clinical Intelligence

Redesigning Care Models for a Consumer-Centric, Digitally Enabled Future

Care models are also evolving. Instead of reacting to illness, we’re seeing a stronger focus on prevention, early intervention, and proactive outreach. Consumer-centric tools like mobile apps, patient portals, and personalized health reminders are becoming the norm, not the exception. It’s all part of a broader movement to meet people where they are and give them more control over their health journey.

But here’s an important reminder: none of these efforts work in a vacuum.

Value-based care isn’t just a technology upgrade or a process tweak. It’s a cultural shift.

Success requires aligning people, processes, data, and technology in a way that’s intentional and strategic. It’s about creating an integrated system that’s designed to improve outcomes and then making those improvements stick.

So, while the road to value-based care may be long and winding, the destination is worth it. It’s not just a different way of delivering care—it’s a smarter, more sustainable one.

Success In Action: Empowering Healthcare Consumers and Their Care Ecosystems With Interoperable Data

Reimagine Healthcare Transformation With Confidence

If you’re exploring how to modernize your digital front door, consider starting with a strategic assessment. Align your goals, audit your content, and evaluate your tech stack. The path to better outcomes starts with a smarter, simpler way to help patients find care.

We combine strategy, industry best practices, and technology expertise to deliver award-winning results for leading healthcare organizations.

• Business Transformation: Activate strategy for transformative outcomes and health experiences.
• Modernization: Maximize technology to drive health innovation, efficiency, and interoperability.
• Data + Analytics: Power enterprise agility and accelerate healthcare insights.
• Consumer Experience: Connect, ease, and elevate impactful health journeys.

Our approach to designing and implementing AI and machine learning (ML) solutions promotes secure and responsible adoption and ensures demonstrated and sustainable business value.

Discover why we have been trusted by the 10 largest health systems and the 10 largest health insurers in the U.S. Explore our healthcare expertise and contact us to learn more.

In earlier blogs – Why AI-Led Experiences Are the Future — And How Sitecore Stream Delivers Them and Creating a Brand Kit in Stream: Why It Matters and How It helps Organizations, I tried to explore what Sitecore Stream is, how it powers AI-led content management, and how features like Brand Kit and Assist streamline your creative process. Those were all about content creation and brand consistency.

But here’s the next big leap:

Imagine this: You’re enhancing your website, launching a new campaign, or rolling out a promotional activity — and you can plan, manage, and execute it all without ever leaving Sitecore portal. No switching between tools. No messy integrations. No lost time.

With AI seamlessly integrated into project creation and management, Sitecore Stream becomes more than just a workspace — it becomes your smart workspace. From automatically generating project outlines, suggesting tasks, and assigning responsibilities, to tracking progress and flagging risks, AI acts as your proactive co-pilot every step of the way.

• One Unified Platform – Content, creative assets, AI planning, project tracking — all in one place.
• Smarter, Faster Execution – AI recommendations help you plan and launch in record time.
• Team Alignment Without the Chaos – Everyone works in the same environment, with instant visibility into priorities and progress.
• Eliminate Context Switching – Stay focused by keeping everything connected inside Sitecore Stream.

Why Manage Projects in Sitecore Stream?

Traditional workflows often mean hopping between:

• A PM tool for scheduling and tasks
• A content platform for asset creation
• A chat app for collaboration

With Sitecore Stream, you get:

• A centralized workspace to create and manage projects
• Built-in AI to help suggest deliverables and tasks
• Direct Sitecore product actions (e.g., linking straight into XM Cloud or Personalize or CDP)
• Multiple visual views (List, Kanban, Timeline, Funnel) for different working styles
• Integrated file storage for creative assets and documents

Let’s walk through the steps to create and manage your first project in Sitecore Stream.

Creating Your First Project — Step-by-Step

1. Check Permissions

To create projects, you need:

• Admin app role in Stream, or
• Org Admin / Owner in Sitecore Cloud Portal

If you don’t have these permissions, request them from your Sitecore Cloud admin.

2. Create the Project

• Navigate to Projects → Create project
• Fill in:
  • Project name
  • Start and End dates (the UI will calculate total days)
  • Brand Kit – link directly to your approved assets
  • Labels – for easy filtering
  • Thumbnail – for quick visual recognition
• Click Save to open your Project Details page

Tip: If you have a Brand Kit, always link it when creating a campaign — it keeps every deliverable aligned with approved brand standards.

3. Add Team Members

• Admins can invite members directly or approve/reject access requests.
• Keep project access restricted to relevant stakeholders to reduce noise and maintain focus.
• Click on +(Plus) icon on top right corner to add new team member

Add Deliverables – Turning Ideas into Action:

Deliverables are the big-ticket outputs your project needs – the stepping stones between concept and execution.

Manual Creation

From the Project Details -> List tab:

• Click Add deliverable
• Enter:
  • Name
  • Due date
  • Funnel stage (Top, Middle, Bottom)
  • Funnel tactic (predefined or custom)
  • Labels (optional)
• Save

AI-Powered Creation

As Sitecore stream is AI packed, its helps you in every step from brainstorming to executions, Use Suggest deliverables with AI:

• Stream analyzes your project name and description
• Add a prompt for more context for creating deliverable. Ex: In below screenshot, I have given context to create deliverable to add campaign and stream has generated deliverables.
• AI proposes deliverables across funnel stages
  – Pick, refine, or regenerate until it fits your plan

Breaking It Down Further: Tasks

Tasks are the day-to-day actions needed to complete each deliverable.

Manual Task Creation

Under a deliverable in the List tab:

• Click Add task
• Give it a name and save
• Open the task pane to set:
  • Labels
  • Status (Not started / In progress / Done)
  • Start & end dates (Stream shows remaining days)
  • Assignee
  • Priority (High / Medium / Low)
  • Description
  • Attachments (DOCX, PDF, PNG, JPG)
  • Dependencies
  • Actions (predefined calls into Sitecore products)

AI-Powered Task Suggestions

• Click Suggest tasks with AI under a deliverable
• AI proposes tasks — you can save, edit, or remove as needed

Linking Sitecore Actions

You can add Sitecore actions to a task — e.g., a button to create an specific item in XM Cloud. This bridges planning and doing in one click.  You can add action for sitecore products like Personalize, CDP, XMcloud, once you choose resource, you can select action to be performed in the products.

Working Your Way: Multiple Views

Different teams prefer different ways of visualizing work. Sitecore Stream gives you five interactive views:

1. List View (Default)

• Hierarchical view of deliverables and tasks
• Best for editing, filtering, and using AI suggestions

2. Kanban View

• Drag task cards between statuses
• Perfect for daily standups and quick progress tracking
• Expand/collapse deliverables for focus

3. Timeline View (Gantt-Style)

• Visualize start/end dates, durations, and dependencies
• Drag-and-drop to adjust schedules
• Switch between Day/Week/Month/Quarter for planning at different levels

4. Funnel View

• Organize deliverables into Top, Middle, Bottom stages
• See funnel coverage at a glance
• Drag between stages to reassign

5. Attachments View

• Centralized file repository for your project
• Search, preview, filter, and download creative assets

The Value of Stream’s Orchestration

Sitecore Stream doesn’t just bolt project management onto a content tool — it blends them into a single marketing execution hub. The benefits are tangible:

• No context switching between PM tools and content platforms
• AI assistance for faster planning
• Visual views for different work styles
• Integrated Sitecore actions to reduce clicks and friction
• Built-in asset management for projects

When your campaign planning, creative production, and execution all live in one system, your team can move faster and with more confidence that nothing is falling through the cracks.

Sitecore Stream moves marketing orchestration into the same ecosystem as content and product tools. You’ll gain a unified space for ideation, execution, and optimization — keeping strategy, tasks, and assets aligned from start to finish.

That combination cuts down context switches, lesser dependencies, AI help for ideation, speeds campaigns, and makes funnel coverage and task ownership visible at a glance. If you already use Sitecore products, the integrated actions are particularly time-saving.

The digital world isn’t slowing down, and neither are your customers. They expect fast, around-the-clock support in their language. For global businesses, meeting that demand can be costly. Hiring multilingual agents in every region adds up quickly. That’s why more companies are turning to real-time translation tools. They offer a more scalable, cost-effective way to deliver consistent, high-quality service across languages.

In this blog article, I will guide you through how we, at Perficient, are addressing this challenge by leveraging Twilio’s ConversationRelay and AI translation technology to deliver real-time voice translation for contact centers. The result is a quick, accurate, and natural conversation with an agent who can speak in the customer’s native language. Pretty impressive, isn’t it?

What Is Twilio ConversationRelay?

For real-time voice translation with Twilio ConversationRelay, developers can access live Media Streams between the customer and agent, and improve their conversation in real-time. Think of it as a smart audio bridge that enables you to plug in AI features such as text-to-speech, real-time translation, speech-to-text transcription, or an LLM. As a result, it provides a strong basis for creating dynamic, multilingual voice experiences in modern contact centers.

Now, let’s see how the backend of our real-time voice translation demo is put together.

Twilio ConversationRelay captures live audio when a customer speaks in their native language, for example, Spanish, using Programmable Voice. That stream is then routed through WebSockets to maintain a quick and responsive connection.

The procedure reverses itself when the agent responds in English, recording their voice, transcribing it, translating it back into the customer’s language, and then turning it back into speech.

It’s fascinating how AI makes it possible to have seamless, two-way, real-time conversation between speakers of different languages without the need for a human interpreter.

Why It Matters

Real-time voice translation is revolutionizing the way businesses communicate with customers by enabling support in the customer’s language without needing an agent who speaks it natively.

But it’s not just about translating words. This method helps support teams truly understand what customers are saying, including the tone and emotion behind their message. That results in fewer misunderstandings, quicker resolution times, and a smoother overall experience.

More importantly, it helps build trust and empathy in conversations that might otherwise feel distant or disconnected. With that, customer satisfaction isn’t just possible, it’s almost guaranteed.

Challenges And Considerations

Real-time voice translation is a game-changer, but making it work seamlessly in a live contact center is a whole different story.

One of the biggest hurdles is latency. Even a slight delay, just a few hundred milliseconds, can disrupt the natural flow of a conversation and make things feel awkward or disjointed.

Then there’s the issue of accuracy. In industries like healthcare or finance, where precise language and industry-specific terms matter, generic translation tools can easily miss the mark.

And let’s not forget about privacy and compliance. When you’re dealing with live audio and sensitive data, you have to play by the rules, whether it’s GDPR, HIPAA, or PCI DSS.

That’s why building a multilingual contact center solution isn’t just about plugging in a translation tool. It takes careful planning, the right tech stack, and thorough testing to get it right.

At Perficient, our Customer Care practice is actively focused on minimizing latency in real-time voice translation for cloud contact centers. Leveraging Twilio ConversationRelay, we are optimizing low-latency audio streaming and integrating optimal ASR and translation models tailored to a specific industry. We also embed secure, compliant workflows that protect sensitive data while preserving natural conversational flow.

See It in Action

We’ve put together a live demo that walks through the full experience, from capturing the customer’s voice to translating it in real-time and vice versa within a cloud contact center.

Curious to see it in action? Or wondering how something like this could level up your contact center? Let’s connect, and we’d love to show you what’s possible.

In today’s data-driven world, understanding how users interact with your application is no longer optional , it’s essential. Every scroll, click, and form submission tells a story, a story about what your users care about, what they ignore, and where they might be facing friction.

This is where event tracking and analytics come into play.

Traditionally, developers and product teams rely on third-party tools like Google Analytics, Log rocket, or Hot-jar to collect and analyse user behaviour. These tools are powerful, but they come with trade-offs:

• Privacy concerns : You may not want to share user data with external services.
• Cost : Premium analytics platforms can be expensive.
• Limited customization : You’re often restricted to predefined event types and dashboards.

 What Is Event Tracking?

Event tracking is the process of capturing and analyzing specific user interactions within a website or application. These events help you understand how users engage with your product.

 Common Events to Track:

• Page Views – When a user visits a page
• Button Clicks – Interactions with CTAs or navigation
• Scroll Events – How far users scroll down a page
• Form Submissions – When users submit data
• Text Inputs – Typing in search bars or forms
• Mouse Movements – Hovering or navigating with the cursor

Why Is It Important?

The primary goal of event tracking is to:

• Understand user behaviour
• Identify friction points in the UI/UX
• Make data-informed decisions for product improvements
• Measure feature adoption and conversion rates

Whether you’re a developer, product manager, or designer, having access to this data empowers you to build better, more user-centric applications.

In this blog, I’ll give you a high-level overview of a custom Event Tracker POC built with React.js and Bootstrap—highlighting only the key snippets and how user interactions are tracked.

1. Reusable Event Tracker Utility:

   const eventTracker = (eventName, eventData = {}) => {
     const key = 'eventCounts';
     const existing = JSON.parse(localStorage.getItem(key)) || {};
     existing[eventName] = (existing[eventName] || 0) + 1;
     localStorage.setItem(key, JSON.stringify(existing));
     const event = {
       name: eventName,
       data: eventData,
       timestamp: new Date().toISOString(),
     };
     console.log('Tracked Event:', event);console.log('Event Counts:', existing);};
   

    

2. Wherever event happen add in below format(e.g: form submit)

   eventTracker('Form Submitted', { name, email });

    

3. To view any event tracker count and which event it is, we can do as per below code.

   export const getEventCount = (eventName) => {
     const counts = JSON.parse(localStorage.getItem('eventCounts')) || {};
     return counts[eventName] || 0;
   };
   
   

    

4. Usage in dashboard

   import { getEventCount } from '../utils/eventTracker';
   
   const formSubmitCount = getEventCount('Form Submitted');
   const inputChangeCount = getEventCount('Input Changed');
   const pageViewCount = getEventCount('Page Viewed');
   const scrollEventCount = getEventCount('Scroll Event');
   
   

   This allows you to monitor how many times each event has occurred during the users session  (if local storage is retained).

Advantages of Custom Event Tracker:

1. Full Control – Track only what matters, with custom data structure
2. Data Privacy – No third-party servers, easier GDPR/CCPA compliance
3. Cost Effective – No subscription, suitable for POCs and internal tools
4. Custom UI – Fully customizable dashboard with React and Bootstrap
5. No External Dependencies – Works offline or in secure environments
6. Easy Debugging – Transparent logic and flexible debugging process

Conclusion:

1. If your focus is flexibility, cost-saving, and data ownership, a custom event tracker built in any framework or library (like your POC) is a powerful choice—especially for MVPs, internal dashboards, and privacy-conscious applications.
2. However, for quick setup, advanced analytics, and visual insights, third-party tools are better suited—particularly in production-scale apps where speed and insights for non-developers matter most.

• Use custom tracking when you want control.
• Use third-party tools when you need speed.

Databricks supports a wide range of compliance standards to meet the needs of highly regulated industries, including:

• HIPAA (Health Insurance Portability and Accountability Act)
• PCI-DSS (Payment Card Industry Data Security Standard)
• FedRAMP High & Moderate
• DoD IL5
• IRAP (Australia)
• GDPR (EU)
• CCPA (California)

However, I was surprised to read that Databricks Serverless workloads are not covered for PCI-DSS (Databricks PCI DSS Compliance | Databricks) and became curious about the reason behind it. Based on my research, I have convinced myself of the reason and would like to share it here.

To begin with, let’s understand different Databricks SQL Warehouse types and their capabilities,

Databricks SQL (Classic/Pro)

• In Databricks SQL (Classic/Pro) warehouses, compute resources in the customer account will be leveraged.
• When running workloads using Databricks SQL (Classic/Pro), data is processed by the compute resources, which are managed by the customers
• Customers will have more control and monitoring over the compute resources
• Data getting processed will also reside within the network boundary of the customer cloud account

Databricks SQL (Serverless)

• In Databricks SQL (Serverless) warehouse, compute resources in the Databricks account will be leveraged.
• Serverless compute operates on a multi-tenant architecture, where compute resources are shared across different customers
• Compute resources are entirely managed by Databricks, and customers will have less control and monitoring ability over the networking and compute resources.
• Different workload data is processed within the compute resources of the Databricks account.
• Though customers have less control over the compute, they can greatly benefit from the capabilities that Serverless warehouses exhibit

Final View

• PCI-DSS requires strict isolation of environments handling cardholder data, which is difficult to guarantee in a shared setup
• It mandates restricted and monitored network access, especially for systems handling payment data
• It requires fine-grained control and auditing, which is more feasible in dedicated or customer-managed environments.
• Databricks recommends using classic or pro clusters with dedicated VPCs, private networking, and enhanced security controls for PCI DSS-compliant workloads.
• Additionally, Databricks dedicates effort to bring in more isolation boundaries within Serverless compute

Let’s be honest, code reviews can be tedious. You open a pull request, scroll through hundreds of lines, spot a couple of obvious issues, and approve. Then, two weeks later, a bug shows up in production… and it’s traced back to a line you skimmed over.

Sound familiar?

That’s exactly why I decided to try Qodo AI, an AI-powered code review assistant that promises to help you review smarter, not harder. And after two months of using, I can confidently say: Qodo AI is a game-changer.

This blog walks you through:

•  What Qodo AI is
•  How to use it effectively

What is Qodo AI?

Qodo AI is an intelligent assistant that plugs into your Git workflows and automatically reviews pull requests. But it’s not just a smarter linter. It goes beyond style rules and dives deep into:

• Bug-prone patterns
•  Missed test coverage
•  Security vulnerabilities
•  Code cleanup and refactoring suggestions
•  Best practice recommendations

It’s like having a seasoned engineer on your team who never gets tired, misses nothing, always explains why something needs fixing.

How to Use Qodo AI (Step-by-Step)

1. Connect Your Repo

Qodo integrates seamlessly with GitHub, GitLab, and Bitbucket. I connected it to my GitHub repo in under 5 minutes.

You can configure it to scan all branches or just specific PRs.

2. Open a PR and Watch It Work

Once a pull request is opened, Qodo jumps into action. It adds inline comments and a summary report—highlighting issues, test gaps, and suggestions.

3. Act on Insights, Collaboratively

What sets Qodo apart is how clear and contextual its suggestions are. You don’t get vague warnings—you get:

• A plain-language explanation
• The rationale behind the issue
• Suggested fixes or safer alternatives

Our developers started using Qodo’s comments as mini code lessons. Juniors appreciated the clarity; seniors appreciated the time saved.

Final Thoughts: Qodo AI is the Real Deal

We often talk about tools that “shift left” or “boost developer productivity.” Qodo AI delivers on both fronts. It’s a powerful, practical, and collaborative solution for any dev or QA team that wants to ship better code, faster.

Would I recommend it?

Absolutely—especially if:

• You want faster, smarter code reviews
• You care about test coverage and edge cases
• You’re working in a security-conscious industry
• You mentor junior developers or maintain high-stakes codebases

Qodo AI didn’t replace our code review process. It enhanced it.

Ready to give it a shot?
Visit https://qodo.ai to explore more. Let me know in comments if you try it—or already have.