Creating an XDM Schema for Web Data with Adobe Experience Platform

Introduction

Welcome to the comprehensive guide on creating an Experience Data Model (XDM) schema for web data using Adobe Experience Platform Data Collection. As an Adobe Web SDK expert, I’ll walk you through the steps necessary to establish a standardized schema, ensuring your web event data is correctly formatted and easily integrated with Adobe Experience Platform and its associated applications.

Understanding XDM Schemas

Experience Data Model (XDM) schemas are fundamental in the Adobe Experience Platform. They serve as the framework for collecting and structuring data, allowing for seamless data integration and utilization across various Adobe Experience Cloud applications. By using XDM schemas, your web event data can be standardized and sent to the Platform Edge Network, making it accessible to applications like Adobe Analytics, Journey Optimizer, Real-Time Customer Data Platform, and more.

Why Model Your Data?

Modeling data is essential because every business has its unique terminology and data requirements. Whether you are in retail, finance, or travel, your data structure needs to reflect your specific business context. For instance, an e-commerce platform might track orders with properties like priceTotal, currencyCode, and purchaseOrderNumber. Standardizing these properties across similar businesses allows for better data exchange, easier integration with partners, and more effective use of machine learning for insights.

Here’s an example of a standardized order data model:

json

Copy code

{

  “order”: {

    “priceTotal”: 89.50,

    “currencyCode”: “EUR”,

    “purchaseOrderNumber”: “JWN20192388410012”,

    “payments”: [

      {

        “paymentType”: “gift_card”,

        “paymentAmount”: 50

      },

      {

        “paymentType”: “credit_card”,

        “paymentAmount”: 39.50

      }

    ]

  }

}

Benefits of Using XDM

Using XDM schemas in Adobe Experience Platform offers several advantages:

• Consistency: Standardize data across your organization and with external partners.
• Efficiency: Reduce the need for data transformation and interpretation.
• Scalability: Easily integrate with various Adobe Experience Cloud applications.
• Actionable Insights: Enhance machine learning capabilities and data visualization.

Creating an XDM Schema

Now, let’s dive into creating an XDM schema for web data in Adobe Experience Platform Data Collection.

Step-by-Step Guide:

1. Open Data Collection Interface: Access the Adobe Experience Platform Data Collection interface.
2. Select the Correct Sandbox: Ensure you are in the appropriate sandbox (development or production).
3. Navigate to Schemas: Go to the Schemas section in the left navigation panel.
4. Create a New Schema: Click the “Create Schema” button in the top right corner.
5. Choose Experience Event: Select “Experience Event” as the schema type and click “Next.”
6. Name Your Schema: Enter a descriptive name for your schema, such as “Luma Web Event Data.”
7. Add Field Groups:
   • Click “Add” in the Field Groups section.
   • Search for “AEP Web SDK ExperienceEvent” and “Consumer Experience Event.”
   • Check the boxes and add these field groups to your schema.

Key Field Groups:

• AEP Web SDK ExperienceEvent: Contains key-value pairs essential for web data collection.
• Consumer Experience Event: Provides fields for capturing consumer interactions.

These field groups ensure that your schema includes the necessary data points for effective data collection and integration.

IdentityMap Object:

The identityMap object is crucial for web-related data collection. It includes the Experience Cloud ID, which is vital for identifying users. This object also allows you to set internal customer IDs for authenticated users.

json

Copy code

{

  “identityMap”: {

    “ECID”: [

      {

        “id”: “1234567890”,

        “authenticatedState”: “loggedIn”,

        “primary”: true

      }

    ]

  }

}

Best Practices for Data Modeling

When building your web event schema, consider the following best practices:

• Use Pre-defined Field Groups: Whenever possible, use existing field groups to maintain consistency.
• Adopt Product-Agnostic Models: Ensure your data model is not overly specific to one product to enable broader use.
• Document Business Requirements: Similar to creating a Business Requirements Document (BRD) and Solution Design Reference (SDR), document your schema requirements to meet the needs of all downstream applications.

Additional Resources

For further learning and advanced schema configuration, consider exploring the following resources:

• Model Your Customer Experience Data with XDM: A detailed course on XDM schema creation.
• XDM System Overview: Comprehensive documentation on XDM standards and practices.

By following these steps and best practices, you can create an effective XDM schema that standardizes your web data collection, enabling you to leverage the full power of Adobe Experience Platform and its suite of applications. If you have any questions or need further assistance, feel free to reach out to our team of experts at QualifiedIQ.