From Spreadsheet to Story: Turning Webinar Attendees into Personalized Journeys with Adobe Journey Optimizer

AI generate image

While working with webinar follow-ups and one-off event data, I came across a simple but powerful use case that often gets overlooked. We frequently collect valuable attendee information in CSV files — names, emails, event details — but then struggle to activate that data quickly and meaningfully.

Instead of waiting for complex ingestion pipelines or making unnecessary changes to Real-Time Customer Profile schemas, I wanted to document a more practical approach. I put this together to show how you can take a basic webinar attendee list, activate it in Adobe Experience Platform, and turn it into a personalized, orchestrated journey using Adobe Journey Optimizer. The goal is to help practitioners move faster, keep profiles clean, and still deliver highly relevant experiences at scale.

Setting the Context: From Events to Experiences

Webinars, virtual events, and one-off campaigns have become core touchpoints in modern digital marketing. They generate high-intent engagement and rich contextual data — who attended, what they attended, and when. Marketers know this information is valuable, but too often it lives in spreadsheets, shared drives, or ad‑hoc exports that never make it into orchestrated customer experiences.

What if you could take that simple event attendance file and immediately turn it into a personalized, contextual follow-up — without waiting for complex ingestion pipelines or altering your core customer profiles?

This is exactly where Adobe Journey Optimizer (AJO), powered by Adobe Experience Platform (AEP), bridges the gap.

The Problem: Your Webinar Data Is Sitting Idle

You’ve just wrapped up a successful webinar. You have a CSV file full of valuable attendee data — names, email addresses, companies, webinar titles, and dates. Everyone expects a thoughtful follow-up: a thank-you email, a survey, maybe even a tailored nurture journey.

But here’s the challenge: that data lives outside your real-time customer profiles in Adobe Experience Platform (AEP). It’s not streaming in, it’s not part of your standard datasets, and you don’t want to wait for a full ingestion pipeline just to send a simple, personalized follow-up.

This is where Adobe Journey Optimizer (AJO) shines. By importing CSV audiences into AEP and activating them in AJO, you can turn static lists into dynamic, personalized journeys — without polluting your core profile data.

In this article, we’ll walk through how to:

• Import CSV audiences into AEP
• Use enrichment attributes for personalization and decisioning
• Activate those audiences in an AJO journey
• Deliver highly personalized follow-up communications (like a webinar survey)

CSV → AEP → AJO: How It All Connects (At a Glance)

• Think of this flow as a lightweight activation pipeline for high-intent, one-off data.
• This approach gives marketers speed and flexibility — without waiting for real-time ingestion or complex data modeling.

DigitalFlowChart for email journey

Step 1: Import Your CSV Audience into AEP

Start in Audiences > Audience Inventory in Adobe Experience Platform.

From here, you can upload a CSV file using the Import Audience option. In a typical webinar use case, your file might include:

• Email address
• Phone number
• First and last name
• Company name
• Webinar name
• Webinar date and time

Once uploaded, AEP processes the file and creates an audience. You can immediately validate:

• Number of records ingested
• Successful ingestion status

At this stage, your webinar attendee list is now an active audience — ready to be used in Journey Optimizer.

Import Audience

Review

Import successful

Understanding Enrichment Attributes (This Is Key)

Every column in your CSV file becomes an enrichment attribute.

A few important things to understand:

• These attributes are not written directly to the Real-Time Customer Profile
• They are linked to the profile for personalization and decisioning

They are available in:

• Personalization editor
• Condition activities
• Journey logic

This design keeps your profile clean while still allowing rich, contextual personalization.

Audience

Audience Realization

Step 2: Identity Resolution During CSV Upload

When importing the CSV, you must select:

• The identity attribute (for example, email address)
• The corresponding namespace (such as Email)

Here’s what happens behind the scenes:

• If AEP finds a matching email, the enrichment attributes are attached to the existing profile
• If no match is found, AEP creates a new profile fragment

These new fragments:

• Contain your enrichment attributes
• Do not automatically have standard execution addresses populated

This is why channel configuration becomes critical in the this step.

Identity Selection

Step 3: Make Enrichment Attributes Available in AJO (Field Groups)

To use enrichment attributes in personalization and conditions, you must expose them through a Field Group.

How to Add Enrichment Attributes to a Field Group

1. Navigate to Administration > Configuration > Data Sources
2. Select Experience Platform and create or edit a Field Group
3. In the schema selector, choose the schema named: Schema for audienceId:<Audience ID> (You can find the audience ID on the audience details screen)
4. Open the field selector and locate your enrichment attributes
5. Select the attributes you want to use
6. Save your changes

Once saved, these attributes become available across Journey Optimizer wherever personalization or conditions are supported

Audience Schema

ExperiencePlatform in Datasource

Enrichment Fields

Mapped Enrichment Fields to the Datasource

Step 4: Configure the Channel to Use Identity Map

Because CSV uploads may create new profile fragments without standard delivery addresses, AJO provides a solution.

In your channel configuration (for example, Email):

• Set the execution address to use the identity map
• Map it to the same identity used during CSV upload (email, in this case)

This ensures that:

• The email address from the CSV file is used directly for delivery
• Both existing profiles and newly created fragments can be targeted

Make sure your journey uses specific channel configuration.

Snapshot of ChannelConfig

Step 5: Build the Journey in Adobe Journey Optimizer

Now comes the fun part — activation.

Journey Overview

Journey Structure Example

1. Read Audience Activity Select your uploaded webinar attendee audience

Step 1

2. Condition Activity Use enrichment attributes to filter attendees

Step 2

Webinar Name equals Future of Digital marketing

3. Email Action: Select the channel configuration that uses the identity map

Step 3

Step 6: Personalize Using CSV Enrichment Attributes

Inside the email content editor, enrichment attributes are fully available for personalization.

The attribute path follows this structure:

• IMS Org Instance
• Audience Enrichment
• Audience Upload (CSV)
• File Name
• Attribute Name

Using this, you can personalize:

• First name
• Webinar name
• Webinar date
• Webinar time

Example Personalization

Here’s what that personalization looks like in practice when driven entirely by CSV enrichment attributes:

“Hi Michael,”

“Thank you for attending the Future of Digital Marketing webinar”

“Held on January 10, 2026 at 10:00 AM”

Each of these values — first name, webinar title, date, and time — is pulled directly from the uploaded CSV file.

All of this data comes directly from the CSV file — no additional datasets required

Profile browser

Profile Attributes

Profile Audience Membership

The Result: From Static List to Meaningful Engagement

The final output is a highly personalized follow-up email sent to webinar attendees, inviting them to complete a post-event survey.

What started as a simple CSV file is now:

• A fully activated audience
• Driving personalized messaging
• Powered by enrichment attributes
• Orchestrated through Adobe Journey Optimizer

Log result

One can’t help but notice that I would have done a better design on the email content.

Email content

Why This Approach Matters

Using CSV custom upload audiences in AJO allows you to:

• Act quickly on offline or ad-hoc data
• Keep your real-time profiles clean
• Personalize at scale without complex ingestion pipelines
• Extend AJO beyond real-time events into practical, everyday use cases

Whether it’s webinar follow-ups, event surveys, partner lists, or one-time campaigns, CSV audiences bridge the gap between static data and real-time journeys.

And with Adobe Journey Optimizer, that gap disappears fast.

Conclusion

As we’ve seen today, meaningful personalization doesn’t always require real-time streaming data or complex ingestion pipelines. Sometimes, the most valuable insights already exist in simple formats — like a CSV file of webinar attendees.

By importing CSV audiences into Adobe Experience Platform and activating them in Adobe Journey Optimizer, you can quickly transform static lists into contextual, personalized journeys. Enrichment attributes allow you to personalize messages, apply decision logic, and maintain a clean Real-Time Customer Profile — all while acting fast on high-intent moments.

Whether it’s a webinar follow-up, an event survey, or a one-time campaign, this approach empowers marketers and practitioners to move from data collection to engagement without friction.

The key takeaway is simple: don’t let valuable event data sit idle. With Adobe Journey Optimizer, you can turn even the most lightweight datasets into meaningful customer experiences — at the right time, with the right message.