Dynamics Community Forum Thread Details

I am working on a solution architecture for a retail brand focused on kickboxing pads, and I need some advice on the best practices for data integration.

We are planning to connect our external e-commerce storefront with Dynamics 365 Customer Insights to achieve a 360-degree view of our customers. My specific concerns are:

Data Ingestion: What is the recommended way to bring real-time web behavioral data (like abandoned carts or page views from the kickboxing pads storefront) into Customer Insights? Should we use the Azure Data Lake Storage (ADLS Gen2) approach or a custom Web SDK?

Profile Unification: Since we have customer data in both our e-commerce database and Dynamics 365 Sales, what are the best unification rules to ensure we don’t create duplicate profiles for customers purchasing kickboxing pads?

Real-time Journeys: Once the integration is complete, how can we trigger a real-time journey in Dynamics 365 for a customer who just purchased a specific type of kickboxing pads from the storefront?

I would appreciate it if anyone could share a high-level roadmap or any documentation links that cover this type of retail integration scenario.

Best regards,
[ kickboxing pads]

Categories:

Dynamics 365 Sales

CU15020427-0,

1) Issue
Designing a solution architecture to integrate an external e-commerce storefront for kickboxing pads with Dynamics 365 Customer Insights, ensuring real-time behavioral data ingestion, accurate profile unification, and triggering real-time journeys after purchases.

Observed needs:
- Capture real-time events such as page views and abandoned carts
- Avoid duplicate customer profiles across e-commerce and Dynamics 365 Sales
- Trigger immediate engagement after a purchase event
- Establish a scalable and best-practice integration architecture

2) Reason
There is no single out-of-the-box pattern that fits all retail scenarios, and multiple integration approaches exist in Dynamics 365 and Azure, each suited for different latency, scale, and complexity requirements.

Potential contributing factors include:
A) Multiple ingestion patterns available
- Customer Insights supports batch ingestion via ADLS Gen2 and real-time ingestion via APIs or SDKs
- Choosing the wrong method can lead to delayed or incomplete behavioral insights

B) Identity resolution complexity
- Customer data exists in multiple systems with different identifiers
- Without strong matching rules, duplicate unified profiles are created

C) Event vs transactional data differences
- Web behavioral data is high volume and event-driven
- CRM and order data is structured and transactional
- These require different ingestion and processing strategies

D) Real-time journey dependency on event triggers
- Customer Insights Journeys requires properly structured real-time events
- Incorrect schema or delayed ingestion prevents timely journey execution

E) Integration architecture fragmentation
- E-commerce platform, Azure services, and Dynamics 365 must be aligned
- Lack of a unified architecture leads to inconsistencies and latency

3) Resolution
Step 1: Design a dual-ingestion architecture
- Use Azure Data Lake Storage Gen2 for batch ingestion of:
- Orders
- Customer master data
- Product catalog
- Use a real-time event ingestion approach for behavioral data:
- Implement a custom Web SDK or API-based ingestion
- Send events such as:
- Page views
- Add to cart
- Abandoned cart
- Stream events via:
- Azure Event Hubs or Azure Stream Analytics
- Then push into Customer Insights in near real time

Step 2: Implement real-time behavioral tracking
- Use a lightweight JavaScript tracking layer on the storefront
- Capture user activity with identifiers such as:
- Email
- Login ID
- Cookie or device ID
- Push events into Dataverse or Customer Insights event tables
- Ensure event schema matches Customer Insights requirements

Step 3: Define strong identity resolution rules
- Configure Customer Insights unification rules using:
- Email address as primary identifier
- Phone number as secondary
- Customer ID from e-commerce and CRM mapped together
- Use deterministic matching first, then probabilistic if needed
- Normalize data formats:
- Lowercase emails
- Standardized phone formats
- Test and monitor match confidence to reduce duplicates

Step 4: Align data model across systems
- Map e-commerce customer and order schema to Dataverse entities:
- Contacts
- Accounts (if B2B scenarios exist)
- Orders and products
- Ensure consistent identifiers between systems
- Use integration middleware if needed such as Azure Data Factory

Step 5: Enable real-time journeys in Dynamics 365
- Use Customer Insights Journeys real-time marketing capabilities
- Define trigger events such as:
- Purchase completed
- Specific product purchased like premium kickboxing pads
- Configure journey triggers based on event ingestion
- Add conditions for segmentation:
- First-time buyer
- High-value customer
- Deliver actions such as:
- Confirmation email
- Cross-sell campaigns
- Loyalty onboarding

Step 6: Activate insights into Dynamics 365 Sales
- Push unified profiles and segments into Dataverse
- Provide sales with:
- Recent purchase history
- Behavioral signals
- Customer scoring
- Enable follow-up actions based on purchase or engagement

Step 7: Implement governance and monitoring
- Set up data quality rules and duplicate detection
- Monitor ingestion pipelines and event latency
- Track journey performance and response rates

---

Recommended high-level architecture
- E-commerce frontend sends real-time events via Web SDK
- Events flow through Azure Event Hubs
- Stream processed into Customer Insights
- Batch data loaded via ADLS Gen2
- Customer Insights performs unification and segmentation
- Results activated into:
- Dynamics 365 Sales
- Customer Insights Journeys
- Power BI for analytics

---

Documentation and reference guidance
- Follow Microsoft patterns for:
- Customer Insights data ingestion and unification
- Dataverse real-time event integration
- Customer Insights Journeys trigger-based orchestration
- Align with Azure Well-Architected Framework for scalability and reliability

For a more detailed answer, please provide more information.

Rg,

Alexander

*Due to the complex and different possibilities of deploying Dynamics 365 I highly recommend not to setup the application without some expert/partner or support. (For more information contact me under anassl@inno-solutions.info or visit www.inno-solutions.de)

*The Information comes directly from the manufacturer or provider and are validated (not guaranteed) up to date of creation of the posting.

References:

Microsoft Licensing Guide
Microsoft Doc`s/Learn

Community site session details

Integration of e-commerce storefront for "Kickboxing Pads" with Dynamics 365 Customer Insights.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Meet the Microsoft Dynamics 365 Contact Center Champions

Congratulations to the April Top 10 Community Leaders

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates