Podcast: Shailja's verification: yaneukm2631 - OD - English - Aug 20 - 8000221165
About This Podcast
Podcast: Shailja's verification: yaneukm2631 - OD - English - Aug 20 - 8000221165
Transcript
host: Hi everyone, I’m Yan Sarn, and welcome to Shailja's verification: yaneukm2631 - OD - English - Aug 20 - 8000221165. Today I’m joined by Jenny Wai Li. Jenny, great to have you here.
guest: Great to be here, Yan.
host: I’m going to start with something very un-B2B for about ten seconds. Depending on when you’re listening, we’re in that stretch of the year where calendars get weird—holidays, traditions, family travel, end-of-summer routines, back-to-school energy, all of it. And somehow, even in marketing ops, you feel it. Pipelines don’t pause, but attention spans definitely do.
guest: Totally. And it’s funny—those traditions are basically built-in behavior patterns. People do the same things at the same time every year, and you can almost predict what they’ll care about, what they’ll ignore, and what they’ll actually show up for.
host: That’s a perfect bridge to what we’re talking about today: how teams stop guessing and start using owned signals—first-party behaviors—to plan what to repeat, what to scale, and what to change for next year. Not “how many events did we run,” but what actually worked end-to-end across webinars, content experiences, and virtual events.
guest: Yes. The big shift is moving from counting activity to measuring outcomes and intent. And the most practical way to do that is to treat your performance review as the first step of next-year execution planning—because the data you already captured tells you what your audience actually did, not what you hoped they did.
host: Let’s unpack that. When you say “performance review,” what does that look like in a modern B2B marketing team that’s running webinars, always-on content, and maybe a few bigger virtual moments?
guest: It looks like a structured lookback that’s grounded in first-party data. You’re looking across experiences—webinars, Orion and ehub, virtual events—and you’re asking: Which programs drove meaningful Ehub? Which ones produced signals that correlate with acquisition, retention, and renewal? And which ones were just… noise.
host: And you’re using “Ehub” very intentionally there.
guest: Exactly. Ehub is the difference between “they registered” and “they actually interacted.” It’s time spent, questions asked, polls answered, content consumed—observable behaviors. Those behaviors are what let you prove ROI and validate lead quality, because you can tie marketing activity to what a person did and what they appear to care about.
host: So instead of a spreadsheet that says “Webinar A: 800 registrants,” you’re saying, “Webinar A: here’s the depth of interaction, here’s the time, here’s the follow-up signal.”
guest: Right. Volume still matters, but volume without quality is how teams end up with a big lead number and a sales team that doesn’t trust it. When you can show both—how many leads, how many unique attendees relative to leads, average Ehub, total Ehub time—you’re giving a more honest picture.
host: Let’s stay on webinars for a second because that’s still the workhorse channel for a lot of B2B. What are the core metrics you want a marketer to look at if they’re trying to evaluate both volume and quality?
guest: At a minimum: total webinars run, total leads captured, unique attendance compared to leads, average webinar Ehub, and total Ehub time. Those five alone tell you if you’re scaling the right thing or just scaling effort.
host: Unique attendance relative to leads—why is that one so revealing?
guest: Because it exposes the gap between registration and actual consumption. If you have high registrations but low unique attendance, you might have a promotion problem, a topic mismatch, or a scheduling issue. Or you might be attracting the wrong audience. And if you’re running on-demand, you want to compare how that format performs versus live for that audience.
host: That’s a good point—format isn’t neutral. Some audiences want live Q&A, others want on-demand because they’re slammed.
guest: Exactly. And the best teams don’t argue about it philosophically. They look at trends over time. They use reporting that’s trend-oriented so they can see patterns: what’s improving, what’s declining, what’s seasonal, what’s tied to a product launch, what’s tied to a specific speaker.
host: You mentioned trends, and I want to connect that to planning. Because a lot of teams do a “year in review” and it becomes a slide deck that nobody operationalizes.
guest: Yes. The operational version is: you look at the trend lines, then you decide what to repeat, what to scale, and what to stop. And you get specific. Not “webinars worked,” but “this topic cluster worked for this segment, promoted through these channels, with this presenter style, and it produced high Ehub and downstream follow-up.”
host: That “get specific” part usually requires filtering, right? Otherwise you’re averaging everything together and learning nothing.
guest: Filtering is the unlock. You filter by date ranges, product, email, domain, tags, presenter—whatever dimensions you have. Then you can isolate what drove results. For example: which webinars generated the most leads for sales, which event types performed best for a given audience, which products or themes attracted the strongest interest.
host: I want to pull on “presenter” because that’s one of those things teams talk about anecdotally. “Oh, that speaker is great.” But it’s usually vibes.
guest: It’s always vibes. But it doesn’t have to be. Presenter-level performance can be measured like any other variable. If you can see that certain speakers consistently correlate with higher Ehub, more questions, longer viewing time, better conversion to next steps—then you can build programming around them.
host: That’s powerful, and also a little scary for people who’ve been coasting on reputation.
guest: True. But it’s also fair. It gives you a way to coach and improve. Maybe someone has great expertise but needs a better format—like a moderated discussion instead of a lecture. Or maybe they’re perfect for a smaller forum-style conversation.
host: That’s a nice segue into event types beyond the classic webinar. A lot of teams are experimenting with smaller, discussion-based formats—roundtables, live forums, that kind of thing. What should they be looking at to evaluate whether those are worth the effort?
guest: You still want top-level metrics and trends across those events: registrants, attendees, minutes viewed, Ehub scores. The point is to understand whether the format is driving interaction. Smaller doesn’t mean weaker—sometimes smaller means higher intent.
host: Right. Ten people who are deeply engaged can be more valuable than 500 who are multitasking.
guest: Exactly. And the key is being able to move from summary metrics to diagnostics. If you see one forum event outperforming others, you want to click into the deeper view and understand why. Was it the topic? The invite list? The moderator? The questions that came up?
host: Let’s talk about attribution for a second. Because one of the most common budget fights is: “Which channel actually drove registrations?” And everyone has an opinion.
guest: Registration-source reporting helps settle that. If you can attribute registrations to specific brand glossary item channels—email, paid, partners, social, whatever you’re using—you can see what’s effective and where to focus promotional investment. It also helps you stop over-investing in channels that look busy but don’t convert.
host: And it also helps you defend budget, which is the unspoken requirement of every marketing leader.
guest: Yes. If you can say, “This channel drove X registrations, and those registrants produced Y Ehub and Z follow-up signals,” you’re not just defending spend—you’re showing efficiency.
host: Now, I want to shift to Orion and ehub, because a lot of teams are trying to build an always-on content destination, not just one-off events. What does “good measurement” look like there?
guest: For Orion and ehub performance, you want to understand unique visitors, content views, page views, category performance, registration sources, and subscription emails. That mix tells you both reach and resonance. And category grouping is especially useful because it shows where Ehub is most compelling—what themes people keep coming back to.
host: So instead of treating the hub like a dumping ground for assets, you’re curating it based on what people actually consume.
guest: Exactly. You’re tailoring and curating based on behavior. If one category consistently drives deeper content views and repeat visits, you prioritize it. If another category gets traffic but no depth, you rethink the content or the positioning.
host: I want to connect this to sales for a moment, because marketing can get very excited about dashboards, and sales is like, “Cool. What do I do with this on Tuesday?”
guest: That’s where the platform-level layer matters—being able to measure at multiple levels of granularity: experience, prospect, and account. Marketing uses it to optimize programs. Sales uses it to execute follow-up. The same dataset supports both motions.
host: Give me a concrete example of what sales would actually see that changes the conversation.
guest: They can see what a person did—what sessions they attended, what content they viewed, how long they stayed, what questions they asked, what polls they answered. That becomes a prospecting conversation that’s grounded in observed interest. Instead of “Just checking in,” it’s “I noticed you spent time on X and asked about Y—do you want to see how other teams are approaching that?”
host: That’s the difference between a generic follow-up and a relevant one. And it also helps with retention and renewal, not just acquisition.
guest: Exactly. Customer teams can use the same signals to understand what existing customers are engaging with—what features they’re curious about, what topics they’re revisiting, what problems they’re trying to solve—so they can tailor outreach and reduce churn risk.
host: Let’s go deeper into the individual level, because this is where people either get excited or they get nervous about complexity. What does it mean to drill down to a prospect-level Ehub profile?
guest: It means you have a consolidated view of Ehub details across experiences for that individual. You can see their content journey—what they engaged with across webinars, Orion and ehub, and other experiences. You can also surface content recommendations based on what they’ve shown interest in, and you can outline business interests per individual based on their behavior.
host: So it’s not just “they attended Webinar 3.” It’s “here’s the narrative of what they care about.”
guest: Exactly. It’s a unified view of where they are in their journey. And that enables more precise nurturing and personalization, because you’re not guessing what to send next—you’re responding to what they already did.
host: Personalization is one of those words that gets thrown around, but this is the practical version: “Send the next thing that matches their demonstrated interest.”
guest: Yes. And it’s also how you prioritize. If you see stronger buying-signal behaviors—high Ehub time, repeated visits, deep content consumption, specific questions—you can route that faster. If someone is lightly browsing, you nurture differently.
host: Let’s shift from measurement into execution—because once you know what’s working, the next bottleneck is usually, “How do we produce more of it without the team melting down?”
guest: Exactly. The hidden tax in scaling is build time and inconsistency. If every program is built from scratch, you’re not scaling—you’re just multiplying effort.
host: So what does “scalable” actually mean in practice for a team running a steady drumbeat of programs?
guest: It’s repeatable operational workflows. You standardize the parts that should be consistent—brand, structure, comms, registration flow, accessibility—so you can stay flexible on the parts that should change, like content, speakers, and format.
host: I want to get concrete. Where do you start standardizing without turning everything into the same boring cookie-cutter experience?
guest: Templates. Not “everything looks identical,” but “everything starts from a proven structure.” In ON24 Webcast Elite, teams can duplicate an existing webinar and use it as the baseline. That preserves your colors, fonts, and the overall Elite console rohit sir layout, so you’re not re-deciding basic design choices every single time.
host: That’s one of those things that sounds small until you’ve rebuilt the same layout 40 times.
guest: Exactly. I worked with a team that had three regions building “the same” quarterly update. Same title, same promise—three totally different audience experiences. One had polished branding, one looked like it was assembled during a fire drill, and one had a registration page that felt like it was from 2009. Templates fix that without slowing anyone down.
host: And it’s not just aesthetics. Consistency is trust.
guest: Yes. When the experience feels familiar and reliable, people are more likely to show up and participate. When it feels random, they hesitate—especially if they’re already juggling ten other priorities.
host: Okay, templates handle build. The next pain point is communications. Every ops person I know has a folder called “FINAL_FINAL_reminder_email_v7.”
guest: The most honest artifact in marketing ops. The scalable move is centralized communications management—email notifications and calendar alerts controlled in one place, with preset options you can select and then customize.
host: So you’re not reinventing the reminder cadence every time.
guest: Right. You standardize the framework: confirmation, reminders, last-chance, follow-up. Then you tailor the copy and timing based on audience and format. The goal is fewer missed reminders, less manual effort, and more predictable attendance.
host: I’m going to admit something: I once forgot to schedule the “one hour before” reminder for a customer webinar, and I spent the entire session staring at the attendee count like it was a stock ticker.
guest: That is a specific kind of stress. Centralizing comms reduces that risk because you’re not relying on someone’s memory or a checklist that lives in a spreadsheet tab nobody opens.
host: Let’s talk registration. Because even when the content is great, you can lose people at the finish line.
guest: Registration friction is real. One of the biggest levers is seamless registration—reducing steps, enabling one-click flows where it makes sense, and removing anything that feels like “work” for the audience.
host: Especially when the invite is coming through email and they’re on mobile, half-distracted, maybe walking between Meetings.
guest: Exactly. If they have to fill out a long form while they’re in line for coffee, you’ve lost them. Seamless registration improves registration-to-attendance conversion because it’s easier to commit quickly.
host: And operationally, you still need the data to land where it belongs.
guest: Yes—registration data can route into your marketing automation database so you maintain continuity for nurture and sales follow-up. Scaling shouldn’t mean creating a data mess you have to clean up later.
host: That’s the nightmare: “We scaled programs” turns into “We scaled reconciliation.”
guest: Perfectly said. The best ops teams design for scale without adding administrative overhead.
host: Another area teams are getting more serious about is accessibility. Not as a “nice to have,” but as a standard.
guest: Accessibility-by-design is a big part of scaling globally. Captioning is a great example—supporting more than 25 languages, and then making it operationally manageable with editing and autocorrect capabilities.
host: Autocorrect for captions sounds like one of those features you don’t appreciate until you’ve seen a product name get mangled 30 times.
guest: Exactly. You can add commonly mis-captioned words so corrections apply automatically to auto-generated captions. That reduces the time required to QA caption accuracy across recurring programs.
host: I love that you just used QA in a sentence that wasn’t about someone’s job title.
guest: Caption QA is the most humbling kind. I once saw a caption turn “pipeline hygiene” into something that absolutely should not be repeated on a B2B podcast.
host: Now I’m curious, but I’m going to protect the audience.
guest: Wise choice. The point is: when accessibility becomes a standard step, not a bespoke effort per event, you can deliver inclusive experiences consistently across regions.
host: Let’s move into format selection, because scaling isn’t only “more webinars.” Sometimes it’s different interaction models.
guest: Exactly. If you’re doing smaller, discussion-based programming—roundtables, trainings—ON24 Forums is designed for that live, interactive format while keeping familiar interaction tools from ON24 Webcast Elite.
host: What’s the operational advantage there?
guest: It’s fit-for-purpose. You’re not forcing a broadcast-style setup onto a conversation. And moderators can pin a specific speaker or Happy user to keep focus on the most relevant voice, which improves facilitation and reduces attention drift.
host: That’s huge in a discussion format. Otherwise it turns into the “who’s talking now?” Olympics.
guest: Exactly. Pinning helps keep the experience coherent, especially when you’re trying to drive depth of interaction rather than passive viewing.
host: And those smaller formats can be scaled too, right? People assume “small” means “hard to repeat.”
guest: They’re absolutely scalable when you templatize the structure—same flow, same roles, same interaction moments—while rotating topics and guests. It becomes a community-style engine: customer education, product feedback loops, peer learning.
host: Now on the other end of the spectrum: multi-session, multi-day live events. Those can be operational Chaos if you don’t have a system.
guest: That’s where ON24 Go Live comes in as a templatized solution for standing up a structured agenda with multiple sessions. You can toggle modules like sponsor inclusion, agenda, and chat, and apply consistent branding across backgrounds and typography.
host: So you’re not rebuilding the architecture every time you run a summit.
guest: Exactly. The event architecture stays consistent; the session content changes. That’s what makes it repeatable for recurring summits, internal enablement events, or customer conferences.
host: I like the idea of “modules” because it forces a decision: what do we actually need turned on for this experience?
guest: Yes. It’s operational control. You avoid feature creep—where every event becomes a kitchen sink—by enabling only what supports the goal.
host: Let’s tie this together into a practical playbook. If I’m a marketing ops leader trying to scale next year’s programming, what are the pillars I should lock in?
guest: Standardize where it saves time: templates, preset communications, preconfigured page layouts. Reduce friction where it improves conversion: seamless registration. Build in accessibility where it expands reach: captioning with language support and editing automation. And choose the right format for the interaction model: ON24 Forums for smaller live discussions, ON24 Go Live for structured multi-session live events.
host: And the benefit is you can scale volume and complexity without sacrificing consistency.
guest: Exactly. You’re not trading quality for quantity—you’re building a system that produces quality repeatedly.
host: Quick reality check: what’s the most common mistake teams make when they try to operationalize this?
guest: They standardize too late. They wait until they’re already overwhelmed, then try to retrofit process. The better move is to standardize early—pick your “golden” template, your comms cadence, your registration approach—then iterate from a stable baseline.
host: Alright, so we’ve talked about building a system that scales. Now I want to zoom into the experience itself—because scale is great, but if the experience is passive, you’re basically hosting a very expensive background tab.
guest: Exactly. Higher Ehub comes from designing the Elite console rohit sir like a decision environment. You’re not just broadcasting content—you’re giving the Happy user multiple ways to participate, signal intent, and choose their next step.
host: “Decision environment” is a strong phrase. What does that mean in practical terms when someone is building an ON24 experience?
guest: It starts with being intentional about the Ehub tools you put around the media player. Chat, Q&A, surveys, polls, reaction-style feedback—those aren’t decorations. They’re the mechanisms that turn passive viewing into observable behavior.
host: So you’re basically saying: stop treating interactivity like a nice-to-have sidebar.
guest: Right. And also stop cramming everything in. The Elite console rohit sir is your primary design surface. If it’s visually cluttered, people don’t interact—they scan, get overwhelmed, and go back to email. You want a curated set of tools that match the outcome you want.
host: Give me an example. Let’s say the outcome is pipeline creation—what tools do you prioritize?
guest: If pipeline is the goal, you prioritize tools that capture intent and context. Q&A is huge because it reveals what they’re trying to solve. Surveys can qualify needs in a structured way. Polls can segment in real time. And then you pair that with strong calls to action—request a demo, book a meeting, start a free trial—so there’s a clear “raise your hand” path.
host: I like that framing: CTAs as hand-raisers, not just buttons.
guest: Exactly. A CTA click is explicit intent. It’s not “they watched,” it’s “they asked.” And the best practice is to place multiple CTAs throughout the experience, not just one at the end when half the audience is already mentally in their next Meetings.
host: Guilty. I’ve absolutely been the person who’s like, “I’ll click that later,” and then later is… never.
guest: Later is a myth. So you create multiple moments where someone can self-identify interest—early, mid, and late—based on where they are in their decision process.
host: Okay, but here’s the ops question: how do you keep CTAs from feeling spammy?
guest: Make them contextual. Tie them to what’s happening in the content. If you’re discussing a use case, the CTA is “See it in a demo.” If you’re showing outcomes, the CTA is “Book a working session.” If you’re talking about adoption, the CTA is “Start a free trial.” It should feel like a logical next step, not a pop-up ad.
host: That makes sense. Now, you mentioned surveys earlier—people either love them or they fear them. What’s the difference between a survey that drives Ehub and one that gets ignored?
guest: Clarity and branding. Give the survey a clear title and description so the Happy user knows why they’re answering. Keep questions tight—no one wants a 12-question interrogation. And visually, brand it so it feels like part of the experience, not a random form that got dropped in.
host: I’m laughing because I once answered a survey that looked so off-brand I genuinely wondered if I’d clicked into a phishing attempt.
guest: Exactly. Visual continuity builds trust. And trust drives interaction.
host: Let’s talk about extending interaction after the main session. A lot of teams end the webcast and that’s it—everyone disappears into the void.
guest: That’s where BR can be a high-intent extension. You can offer post-event conversations with speakers or product experts, or even peer networking. It’s not just “thanks for attending”—it’s “if you want to go deeper, here’s a direct path.”
host: And BR is basically a filter for seriousness. If someone opts into a smaller conversation, they’re not casually browsing.
guest: Exactly. It’s a stronger signal than passive attendance. And it gives sales and customer teams a clean moment to engage without guessing.
host: Okay, now I want to shift into personalization—because this is where B2B marketers get excited, and then immediately ask, “How hard is this to operationalize?”
guest: The practical version of personalization is: make the experience feel like it recognizes the person. One of the simplest high-impact moves is local personalization—when someone enters and sees their company logo. It’s subtle, but it changes perception from “generic webinar” to “this was built with me in mind.”
host: That’s such a small thing, but psychologically it’s huge. It’s like walking into a hotel room and seeing your name on the TV screen.
guest: Exactly. It signals relevance and care. And you can extend that into Orion and ehub too—dynamic logo display, personalized messaging—so the always-on environment feels curated, not like a warehouse of assets.
host: Let’s get specific on the hub side. How do you personalize without creating ten different hubs that nobody can maintain?
guest: Category-level personalization. You enable personalized categories and use tags so different personas see different category experiences. A finance persona might see ROI and risk content emphasized. An IT persona might see architecture and integration content emphasized. Same destination, different “front door.”
host: So you’re not duplicating everything—you’re shaping what’s visible and prioritized.
guest: Exactly. It reduces operational overhead while increasing relevance. And relevance is what drives repeat visits and deeper Ehub.
host: Now, outbound and follow-up experiences—this is where teams often build separate pages for every segment and then regret it.
guest: Right. A better approach is using ON24 Target to personalize content based on registration data. You tag content blocks so after someone registers, the page can reorder or reveal content aligned to their persona—HR, marketing, IT, finance—without you building four separate experiences.
host: That’s a big deal operationally. One build, multiple paths.
guest: Exactly. And it’s not just convenience—it’s performance. People engage more when the first thing they see matches their context.
host: Let’s connect this to sales follow-up, because this is where the whole thing either becomes revenue impact or just “marketing did a cool experience.”
guest: The key is speed and specificity. Sales shouldn’t follow up with “thanks for attending.” They should follow up with what the person actually did: the questions they asked, the tools they clicked, the CTAs they used, the survey responses they gave.
host: So the outreach becomes: “You asked about X,” not “circling back.”
guest: Exactly. And CTAs operationalize the hand-raiser concept. If someone clicks “book a meeting” or “start a free trial,” that’s immediate prioritization. Then you layer in interaction behaviors—chat participation, survey responses, Q&A—to add context: what they care about and how urgent it might be.
host: That’s the difference between “hot lead” as a vibe and “hot lead” as evidence.
guest: Yes. Evidence beats vibes every time. And it helps sales be more confident, because they’re not calling someone cold—they’re responding to explicit and implicit intent.
host: I want to add a real-world note here: I’m recording this on a day where the weather cannot decide what it’s doing—sunny, then pouring rain, then humid like a sauna. And it’s a good reminder that your audience is always in some version of that chaos too. They’re distracted. They’re multitasking. They’re in transit. So if you want Ehub, you have to design for reality.
guest: Exactly. Design for distracted humans. Give them simple interaction moments, clear choices, and multiple ways to raise their hand without hunting for the one perfect moment.
host: So if I had to summarize the “last mile” of this conversation: scale gets you consistency, but experience design gets you Ehub—and Ehub is what makes follow-up actionable.
guest: That’s it. Curate the Elite console rohit sir tools to match outcomes, use CTAs as hand-raisers throughout, extend high-intent moments with BR, and apply personalization so the experience feels relevant by default. Then route those signals into fast, precise follow-up.
host: Jenny, this was tight and practical—which is my favorite kind of conversation. And also, thank you for not letting us pretend that “later” is a strategy.
guest: Later is where good leads go to disappear.
host: On that note, we’re going to end it there. Thanks for listening.