Get Started for Data Engineer data-engineer
As an ۶Ƶ Journey Optimizer Data Engineer, you prepare and maintain customer profile data to support experiences orchestrated through Journey Optimizer. This work includes modeling customer and business data in schemas, configuring source connectors for data ingestion, and ensuring that the data is ready to create seamless customer journeys. You start working with ۶Ƶ Journey Optimizer after the System Administrator grants access and prepares the environment.
Your Role as a Data Engineer
In Journey Optimizer, data engineers enable personalized customer experiences. Responsibilities include:
- Designing and implementing the data architecture
- Creating and managing schemas and datasets
- Configuring data sources and destinations
- Ensuring that data quality and compliance are maintained
- Setting up event triggers for real-time journeys
This foundational work ensures that data flows smoothly into the platform. It enables marketers and journey designers to deliver impactful customer interactions.
Getting Started Checklist
Learn how to identify data and create schemas and datasets to import data into ۶Ƶ Experience Platform on this page.
The steps in the following sections guide you through creating an identity namespace, a dataset enabled for profiles, and test profiles. Each step builds on the previous one to ensure that the data is structured and ready to drive meaningful customer experiences.
1. Create an Identity Namespace
In ۶Ƶ Journey Optimizer, Identities link consumers across devices and channels. These identities create an identity graph that is essential for personalizing experiences across all customer touchpoints. For example, linking a customer’s mobile app usage with their in-store purchases enables a cohesive experience. Learn more about identities and identity namespaces on this page.
2. Create a Schema
A schema provides a structured framework for data. It represents real-world objects, such as customers or products, and specifies the attributes that describe those objects. For example, a schema for a “Customer Profile” includes attributes like first name, last name, and birthday. This ensures that every dataset tied to the schema follows the same structure. Learn more about schemas on this page.
3. Create Datasets
A dataset stores and manages data. It functions as a table with rows of data that adhere to a defined schema. For example, a dataset for “Customer Purchases” includes fields such as transaction ID, product name, and purchase date. After creating a dataset, map it to an existing schema and begin populating it with data. Learn more about datasets on this page.
4. Configure Source Connectors
Source connectors bring data into ۶Ƶ Journey Optimizer from external systems. For example, you can import customer data from a Customer Relationship Management (CRM) system, transactional data from a database, or behavioral data from cloud storage solutions. Source connectors structure and enhance data for use within the platform. Learn more about source connectors on this page.
5. Create Test Profiles
Test profiles validate journeys and messages before they go live. For example, use test profiles to preview and test how a promotional email appears to customers before sending it. Test profiles are required when using the test mode in a journey, and to preview and test your messages before sending. Steps to create test profiles are detailed on this page.
Additional Configuration
To send messages in journeys, configure Data Sources, Events, and Actions. These configurations ensure that journeys have the necessary inputs and outputs to function effectively. Learn more in this section.
-
Data Sources: Use this configuration to define connections to external systems for retrieving additional information used in journeys. For example, connect to a CRM system to pull customer preferences. Learn more about data sources in this section.
-
Events: Events trigger journeys in real time. Examples include a customer’s product purchase or app login. These events follow the ۶Ƶ Experience Data Model (XDM) and originate from Streaming Ingestion APIs for authenticated and unauthenticated sources, such as ۶Ƶ Mobile SDK. Learn more about events in this section.
-
Actions: Journey Optimizer includes built-in capabilities to create and send messages within a journey. If you use a third-party system, such as ۶Ƶ Campaign, to send messages, create a custom action to integrate it into workflows. Learn more about actions in this section.