Adobe Defined Functions
- Topics:
- Queries
CREATED FOR:
- Beginner
- Developer
Learn how to use Adobe-defined functions in Adobe Experience Platform Query Service to perform common business-related tasks on Experience Event data. For more information, please visit the Query Service documentation.
Transcript
Hi there, Adobe Experience Platform in just data from a wide variety of sources. A significant challenge for marketers, is making sense of this data to gain insights about their customers. Adobe Experience Platform Query Service facilitates that by allowing you to use standard SQL to query data in platform, using a user interface. On top of the standard SQL capabilities, Adobe provides predefined functions in Adobe Experience Platform Query Service that help perform common business-related tasks on Experience Event Data. These include functions for sessionization and attribution like those found in Adobe Analytics. In this video, let’s use an Adobe defined function, Sessionization, to explore Experience Event Data. From your Experience Platform homepage, navigate to data sets under data management. For this video, we are using a fictional retail brand called Luma. Luma loyalty data set contains information about customers, loyalty details, geographic details, et cetera. Luma web data contains web traffic information about customers interaction on the Luma site, including products viewed by a customer, visited pages, products purchased, et cetera. Now let’s explore how we can query the data set, using Platform Query Service. From the left navigation bar, click on queries under data management. Let’s click on the create query button, and you can see a query editor window opens up. Query editor enables you to write and execute queries without using an external client. When you’re working with experience event data, originating from a website, mobile application, interactive voice-response system, or any other customer interaction channel, it helps if events can be grouped around the related period of activity. Typically, you have a specific indent driving your activity, like researching a product, paying a bill, checking out balance, filling out an application, and so on. This grouping or sessionization of data helps associate the events to uncover more context about the customer experience. Let’s create a query to perform a sessionization for the Luma web data set. In the session timeout function, we provide two parameters, timestamp and expiration in seconds. Expiration in seconds denotes the number of seconds needed between events to qualify the end of the current session and the start of the new session. For the sample query, the results are given in the session column. The session column is made up of the following components, timestamp difference, number, is_new, and depth. Timestamp difference, the difference in time in seconds between the current record and the prior record. Number, a unique session number starting at one, for the key defined in the partition by of the window function. Is_ new a Boolean used to identify whether a record is the first of a session. Depth, the depth of the current record within the session. I hope I was able to give you a quick overview of how to use predefined functions in Adobe Experience Platform Query Service that help perform common business-related tasks on Experience Event data. Explore the documentation to check out other Adobe-defined functions. -
Experience Platform
- Platform Tutorials
- Introduction to Platform
- A customer experience powered by Experience Platform
- Behind the scenes: A customer experience powered by Experience Platform
- Experience Platform overview
- Key capabilities
- Platform-based applications
- Integrations with Experience Cloud applications
- Key use cases
- Basic architecture
- User interface
- Roles and project phases
- Introduction to Real-Time CDP
- Getting started: Data Architects and Data Engineers
- Authenticate to Experience Platform APIs
- Import sample data to Experience Platform
- Administration
- AI Assistant
- Audiences and Segmentation
- Introduction to Audience Portal and Composition
- Upload audiences
- Overview of Federated Audience Composition
- Connect and configure Federated Audience Composition
- Create a Federated Audience Composition
- Audience rule builder overview
- Create audiences
- Use time constraints
- Create content-based audiences
- Create conversion audiences
- Create audiences from existing audiences
- Create sequential audiences
- Create dynamic audiences
- Create multi-entity audiences
- Create and activate account audiences (B2B)
- Demo of streaming segmentation
- Evaluate an audience rule
- Create a dataset to export data
- Segment Match connection setup
- Segment Match data governance
- Segment Match configuration flow
- Segment Match pre-share insights
- Segment Match receiving data
- Audit logs
- Data Collection
- Dashboards
- Data Governance
- Data Hygiene
- Data Ingestion
- Overview
- Batch ingestion overview
- Create and populate a dataset
- Delete datasets and batches
- Map a CSV file to XDM
- Sources overview
- Ingest data from Adobe Analytics
- Ingest data from Audience Manager
- Ingest data from cloud storage
- Ingest data from CRM
- Ingest data from databases
- Streaming ingestion overview
- Stream data with HTTP API
- Stream data using Source Connectors
- Web SDK tutorials
- Mobile SDK tutorials
- Data Lifecycle
- Data Science Workspace
- Overview
- Architecture
- Load data in JupyterLab notebooks
- Query and discover data in JupyterLab notebooks
- Exploratory Data Analysis
- Recipes, models, and services overview
- Build a model using the recipe builder template
- Analyze model performance
- Create and publish a trained model (UI)
- Schedule automated training and scoring for a service
- Enrich Real-Time Customer Profiles with machine learning insights
- Package source files into a recipe
- Import a packaged recipe (UI)
- Import a packaged recipe (API)
- Destinations
- Destinations overview
- Connecting to destinations
- Create destinations and activate data
- Activate profiles and segments to a destination
- Configure a dataset export destination
- Integrate with Google Customer Match
- Configure the Azure Blob destination
- Configure the Marketo destination
- Configure file-based cloud storage or email marketing destinations
- Configure a social destination
- Activate through LiveRamp destinations
- Adobe Target and Custom Personalization
- Activate data to non-Adobe applications webinar
- Identities
- Intelligent Services
- Monitoring
- Partner data support
- Profiles
- Understanding Real-Time Customer Profile
- Profile overview diagram
- Bring data into Profile
- Customize profile view details
- View account profiles
- Create merge policies
- Union schemas overview
- Create a computed attribute
- Pseudonymous profile expirations (TTL)
- Delete profiles
- Update a specific attribute using upsert
- Privacy and Security
- Introduction to Privacy Service
- Identity data in Privacy requests
- Privacy JavaScript library
- Privacy labels in Adobe Analytics
- Getting started with the Privacy Service API
- Privacy Service UI
- Privacy Service API
- Subscribe to Privacy Events
- Set up customer-managed keys
- 10 considerations for Responsible Customer Data Management
- Elevating the Marketer’s Role as a Data Steward
- Queries
- Overview
- Query Service UI
- Query Service API
- Explore Data
- Prepare Data
- Adobe Defined Functions
- Data usage patterns
- Run queries
- Generate datasets from query results
- Tableau
- Analyze and visualize data
- Build dashboards using BI tools
- Recharge your customer data
- Connect clients to Query Service
- Validate data in the datalake
- Schemas
- Overview
- Building blocks
- Plan your data model
- Convert your data model to XDM
- Create schemas
- Create schemas for B2B data
- Create classes
- Create field groups
- Create data types
- Configure relationships between schemas
- Use enumerated fields and suggested values
- Copy schemas between sandboxes
- Update schemas
- Create an ad hoc schema
- Sources
- Use Case Playbooks
- Experience Cloud Integrations
- Industry Trends