Adobe Experience Platform(AEP) Online Training Demo Session | AEP For Beginners| +91 8106000433

Getting Started with Adobe Experience Platform

Overview of Adobe Experience Platform

• The session covers the Adobe Experience Platform, including Journey Optimizer (AJO) and Customer Data Platform (CDP).

• AJO is a separate platform that utilizes data from the Adobe Experience Platform.

• CDP features will be discussed in detail, while AJO will only be briefly mentioned.

Recap of Previous Session

• The previous session focused on features and benefits of the Adobe Experience Platform.

• Discussed how data is exchanged from digital properties using tools like Omnipug.

• Transitioning to use cases for better understanding of the platform's applications.

Use Cases for Adobe Experience Platform

Real-Time Customer Data Management

• Real-time CDP addresses challenges like fragmented data and inconsistent experiences.

• Centralizes data from various sources to enhance marketing initiatives.

Instant Personalization

• Enables personalized messaging across channels, improving marketing performance.

Customer Journey Intelligence

• Leverages collected data for real-time decision-making during customer interactions.

Understanding Adobe Experience Platform

• The query service allows data extraction, focusing on theoretical concepts before diving into practical applications.

• Initial sessions cover foundational concepts and use cases before exploring the platform in detail.

• The platform enables consistent cross-channel experiences using integrations with products like Adobe Target and Customer Journey Optimizer.

Real-Time Customer Profile Updates

• Marketers can create consistent experiences across channels, utilizing event-driven targeting based on customer actions.

• Example: A customer's profile can be updated in real-time when they make significant purchases, enhancing personalization efforts.

• The system listens for transactions to trigger updates, such as moving a customer from a silver to a gold status.

Clarifying Hypothetical Use Cases

• Discussion on how customer profiles are updated within the Adobe Experience Platform rather than backend systems.

• Clarification that upgrades are virtual decisions made by marketing teams based on purchase history and behavior.

Understanding Adobe Journey Optimizer

• Explanation of Adobe Journey Optimizer and its canvas for defining customer journeys.

• Conditional statements determine actions like sending emails based on customer qualifications.

• Real-time profile updates are possible, syncing data depending on project implementation.

Adobe Launch vs. Data Collection

• Clarification that Adobe Launch is now referred to as Data Collection, a tag management system.

• Data Collection integrates seamlessly with the Adobe Experience Platform and other products.

Adobe Experience Cloud Ecosystem

• Overview of the Adobe Experience Cloud, including key products like Analytics, Target, and Campaign.

• Mention of Marketo and Audience Manager for personalization and activation features.

• Introduction to Adobe Journey Optimizer for creating targeted customer journeys.

Data Integration in Adobe Experience Platform

• Real-time identification of customers from anonymous to known status within the platform.

• All collected data can be accessed by other products for targeting and personalization purposes.

Key Features of Adobe Experience Platform

• Identity creation involves linking incoming identities to build customer profiles.

• Segmentation groups customers into cohorts based on shared characteristics or behaviors.

Data Collection Features

• The data set allows for unlimited dimensions, functioning like a nested JSON object.

• Unlike Adobe Analytics, there are no limitations on the number of eVars and props; data can be expanded freely.

• AI and ML features include Jupyter notebooks for running pre-built models tailored to specific data.

Privacy and Governance

• Users can flag sensitive data (PII) to prevent its use in marketing efforts.

• Flagged data cannot be utilized for targeting products, ensuring compliance with privacy standards.

• Integration with various marketing platforms like Adobe Target and Google Marketing is supported.

Client Transition to Adobe Experience Platform

• Discussion on reasons clients should consider moving to Adobe Experience Platform from existing applications.

• Example of a hypothetical company using multiple Adobe products without real-time experience highlights the need for consolidation.

• Consolidation into one library (Alloy.js) reduces site load and improves performance.

Real-Time Personalization Benefits

• Real-time personalization capabilities allow immediate actions on websites within seconds.

• Improved connectivity with other marketing platforms enhances functionality compared to previous systems.

Identity Services and Data Management

• Adobe and other products lack centralized identity services; building a system requires significant engineering.

• Adobe Experience Platform offers a value proposition by integrating data from various sources seamlessly.

• Real-time Customer Data Platform (CDP) is part of the application, not a separate entity.

Data Flow and Event Handling

• Real-time data storage allows immediate access to user interactions, such as page views.

• Apache Services listen for events, creating profiles for anonymous users once they log in.

• The system identifies returning customers quickly after login based on previous browsing behavior.

Future Sessions and Features

• Future sessions will cover data collection processes and feature demonstrations in detail.

• Preparing for platform access may delay comprehensive coverage of features in current session.

• Understanding differences among numerous features depends on specific client use cases.

User Roles and Responsibilities

• Client needs dictate whether they require real-time profiles or simple data injection capabilities.

• Multiple user roles exist, including marketers focused on data consumption by marketing tools.

• Data engineers manage data scraping through tag management solutions like Adobe Launch or Google Tag Manager.

Complexity of the Platform

• Various roles include mobile app developers who implement different strategies for app integration.

• Governance roles depend on management structures within organizations using the platform.

• Many personas can interact with the platform, highlighting its complexity.

APIs and Third-party Integration

APIs and Adobe Experience Platform

• APIs are available to expose data from the Adobe Experience Platform to third-party systems.

• Example of API connectivity includes webhooks and endpoints for data reading and exporting.

• Adobe I/O can be used to integrate other systems with the Adobe platform.

Understanding Sensei's Role

• Sensei is an AI feature integrated into various Adobe products, enhancing automation capabilities.

• It operates across multiple platforms like Adobe Analytics and Audience Manager, providing features like anomaly detection.

• Sensei activates based on user actions rather than being a standalone service.

Overview of Data Ingestion Methods

• The session transitions to an overview of the Adobe Experience Platform ecosystem.

• Data can enter the system through streaming or batch methods, depending on user engagement sources.

• Streaming data refers to real-time interactions from digital properties; batch data involves scheduled uploads from systems like CRM.

Batch Connectors and Workflows

• Batch connectors read data from FTP or CRM systems regularly for updates.

• Workflows allow configuration for continuous data reading from various platforms including cloud-based stores.

• Pre-baked connectors facilitate integration with applications such as Adobe Analytics and Target.

Streaming Data Connections Explained

• Clarification on differences between streaming data connecting to Edge vs. direct connections.

• Edge refers to implementation via Adobe Launch, collecting information before sending it to the Edge Network.

Understanding Data Collection and Ingestion

• Adobe Launch is discussed as a key component in data collection, differentiating between top-line data from connectors and bottom-line data without tag management solutions.

• The concept of ingestion is introduced, highlighting its role in the overall data collection process.

• Clarification on online vs offline data sources; online data comes from launch while offline may come from applications not accessible to end users.

Data Categorization

• Online data flows through Edge Network via Adobe Launch; offline data includes information from systems like point of sale.

• Data can be categorized as streaming or batch based on how it is processed within the system.

• Emphasis on ensuring accurate categorization to avoid misinformation regarding data flow.

Web SDK Implementation

• New web SDK installation depends on existing infrastructure; migration projects are common for legacy systems.

• Legacy systems use extensions for each product, while new implementations redirect all collected data into the Edge Network.

• Migration evaluation should consider load and effort before transitioning to web SDK.

Data Stream Configuration

• Typical implementation involves sending collected data to a tracking server before reaching Adobe Analytics via Alloy.js.

• Data streams must be configured in Adobe Launch to identify where incoming data will be sent.

Adobe Target Data Integration

• Adobe Target data will be sent to the Adobe Experience Platform, contributing to the dataset.

• Evaluation and discovery of the current infrastructure are essential for optimal migration routes.

• Upcoming session will cover data upload processes and address questions regarding Adobe Launch.

Data Handling in Adobe Launch

• The agenda includes a high-level overview of topics related to data handling.