Stop juggling external tools and messy CSV exports for your event registration! 

Join Cory Frey from Cloud Adoption Solutions as he walks you through how to build a custom-branded event microsite natively within Salesforce using the power of Experience Cloud (LWR). Tradeshow season is upon us, so we’re here to ensure that this is the most successful & plentiful season yet! By keeping your event data native, you eliminate lag, avoid complex integrations, and ensure your data stays exactly where it belongs: in your CRM.

What you’ll learn in this 3-step walkthrough:

Step 1: The Shell – Setting up your Experience Cloud site using the Lightning Web Runtime (LWR) template.

Step 2: Data Binding – How to pull data directly from Salesforce objects (like Campaigns) without complex CMS setups.

Step 3: The Flow – Creating a Screen Flow to handle registrations, check capacity, and create Campaign Members automatically. 

Get ready and go native now for real-time data, better user experience, simplified reporting & ROI tracking, and total branding control!

Let us know if you have any questions or if you have any requests for our next CAS Come and See Video!

VIDEO TRANSCRIPT:

 Are you tired of event registration, headaches, juggling external tools, messy CSV exports and disconnected data?

I’m Cory Frey with Cloud Adoption Solutions and today we’re building a custom branded event, microsite natively in Salesforce. No integrations, no lag, just pure experience cloud power. Let’s do it in three steps.

Step one is the shell and we’re heading into experience folder. So I’m in setup under digital experiences. I’ve gone to all sites and I’m gonna make a new site and we’ll see all the templates here for the digital experiences. And for this example, we’re gonna build our own. So we’re gonna choose the build our own LWR or Lightning Web Runtime, and then we’ll click get Started.

So we’ll just give it a name here and then click create.

And once the site is provisioned, we’ll have a blank canvas, but this canvas is directly plugged into the Salesforce work. All right, so built our site. Step two is gonna be bringing in the data. And in the past you needed a complex CMS setup, but with enhanced LWR, we can bind directly to Salesforce objects.

So here’s the dummy data that I brought into the campaign object. I’m reusing the campaign object as an event sessions object. Um, instead of creating a new object, um, just to reuse the campaign object for this demo, I added some custom fields and then I imported this data and back in the workspace. I’m gonna go into the builder and I’m going to drag a grid component.

And over in the right side under Data Source, we’re going to select record list. An object is going to be campaign. And then under the record list we will select sessions. And this is just the list view I have of the sessions.

Once we have the grid settings how we want them, then we will add a text block component, and then on this, we’ll click on the text box block and then select the item name.

This pulls in those campaign names. And we’re going to add another text block right underneath this, and this will be the speaker. Then we’ll add another text block.

And we will pick the session start, date and time for that one. And so here we’re not hard coding any of this. This is all dynamic based on the data in Salesforce. So now we have the outline of our agenda. So for step three, the beyond registration part where we need people to actually sign up, we have to create a screen flow.

And this is the event registration screen flow that I built. Um, it’s very basic, but it gets the contact ID and the campaign id and here I’ve called it Session id not Campaign id. Sorry about that. So we have this input variable session id, and then I have this record contact ID variable. That’s also available for input.

And another way we could do this is we could have the user id, most likely the person wouldn’t be logged into the experience site. Um, so we can use this user ID field instead, and we’ll just make this text available for input beyond the registration part. We need people to actually sign up, so we need to do that with a screen flow.

I’ve built this very basic screen flow here. That takes the session ID or the campaign ID and the user ID and it checks if the session’s at capacity creates a campaign member, and then we will display a success message back in the experience site builder. We will add a flow component to the grid. Then we’ll pick the native event registration flow in the flow component. We’ll map the session ID and then the user id.

And then that makes that button smart. So it maps the flows input variable to item id, which gets mapped to the campaign id, and the user ID will then map to that user ID variable in the flow as well. And of course, you would add your own branding to this. Anything else that you’d. Want to show on the micro site and then you would publish it.

And after the site publishes successfully, we can navigate to the site. And here we see the sessions and the screen flow. Of course there’s more nuance and customization to this than what I’ve shown in this demo, but if you’d like to learn more, please reach out to us.