Upload audiences into Adobe Experience Platform
- Topics:
- Segments
CREATED FOR:
- Beginner
- User
Learn how to upload audiences in CSV format into Adobe Experience Platform. For more information, please see the Segment Builder documentation.
Transcript
In this video we’re going to be going over the audience upload feature that’s part of reimagining audiences with an Adobe Experience platform. This exciting new feature makes it easier than ever to bring in audiences from any source, especially those outside of the Adobe ecosystem. Plug them straight in and get them going in your marketing efforts. In order to understand how this works, let’s first start by talking about how an audience is made. No matter where they come from, audiences all have the same basic construction. We start with some base data, for example data from Adobe’s real-time customer profile. Then we apply to that a segment definition. Remember this is simply an expression or a query we’re going to apply to that base data. The result is what we call an audience. That’s a group of profiles, people in this example, who all meet the criteria expressed in the segment rules. Because most marketing systems share these same basic elements, establishing audiences as a currency makes a lot of sense and provides more flexibility in how audiences are used in customer interactions. Historically, Experience platform customers have started by loading all their relevant base data into platform, constructed segment definitions, and produced audiences all within that AEP ecosystem. That’s still the right option for a lot of cases, but say you’ve got some audiences you’ve already created somewhere else, and for cost, security, or technical reasons, it just doesn’t make sense to try and redo all that work in a new system. With standardized audiences, that’s no longer necessary, and there’s an option to leave the base data and segmentation logic right where it is, and simply bring the resulting audience into Experience platform. As long as the identities for the profiles you’re bringing in have been configured for AEP, you’ll be able to activate your custom audience right alongside any audiences native to Experience platform.
Now let’s see what this looks like within the Experience platform interface. I can go to import audience, where I get the option to either select from files or just drag and drop a file straight from my machine. When the upload starts, I get a quick preview of the file that I’ve just uploaded so I can check and make sure that everything looks the way that I expect. When I hit next, the file name from this will automatically populate in the audience name. I can change that at a description, but the two most important fields here are to tell the system which column contains the ID and what kind of ID that is. I’ve got some advanced options I can look through, or I can just say next from here. I get a nice preview of what I’ve done with all the audience metadata, some sample rows so I can make sure everything looks like I want, and then I can click finish. And just like that, the audience metadata gets published and is ready to be combined, refined, or even used as is. The underlying data, of course, will take a little bit of time to get ingested, but that process has already started and I don’t have to wait for it to continue my work. I can also click into the audience details to get more information about how the ingestion is going, the current status, and the data set and batches associated with this audience. Here are a few things you’re going to want to keep in mind as you use this feature. First of all, there’s a 1 gigabyte file limit from the UI. We’re working on an S3 connector for bigger files, but that’ll be coming later. When you upload your files, make sure you’ve got less than 10 columns. You shouldn’t need that many anyway, because additional columns should not be durable profile attributes like first name, last name, etc. They should really be temporary contextual data used for personalization. In our example, that was things like the flight number, the cancellation date, the weather at the time, can also be promo codes or any other personalization that’s specific to the audience. When you upload an audience, you can augment existing profiles or create new ones, depending on whether or not that ID has been seen before by the profile service. So be aware of it, that might affect your organization’s profile counts and richness. Finally, this is not yet available as is for AGO campaigns or journeys, but should work great for all RTCDP destinations. We hope this video has given you a glimpse into the exciting new capabilities coming with this audience upload feature within Adobe Experience Platform. Thanks for watching.
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
- Import sample data to Experience Platform
- Administration
- AI Assistant
- APIs
- Audiences and Segmentation
- Audience Builder
- Introduction
- Upload audiences
- 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 batch audiences on demand
- Federated Audience Composition
- Segment Match
- Tutorials
- Audience Builder
- Audit logs
- Data Collection
- Collaboration
- 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
- Destinations
- Destinations overview
- Connect to destinations
- Create destinations and activate data
- Activate profiles and audiences to a destination
- Export datasets using a cloud storage 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 the 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 and Data Distiller
- 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