From First Segment to Final Report: How a Marketing Manager Runs an Entire Event in One Marketing OS

How a Singapore-based Marketing Manager plans, promotes, runs, and reports on an event over six weeks — using one Marketing OS instead of six disconnected tools

Camille, Marketing Manager at a mid-sized fintech expanding into Southeast Asia, gets a Slack message from her CMO: "What's the plan for the event on the 14th?" The event is eight weeks out. Nothing has been built yet. That's exactly on schedule — except in the old stack, "on schedule" meant four different tools, three of which wouldn't fully agree with each other until the week before.

Marketing Manager using Good Bards Marketing OS in Singapore

This time she opens one tab and starts the way she always should have: with the audience, not the invite.

CDP Audience Segmentation: Building the Guest List Before the Event Exists

Eight weeks out, she opens Good Bards, a Singapore-headquartered Marketing OS, and goes straight to the Customer Data Platform. Every touchpoint a customer has ever had — a website visit, a past event, an opened email, a note from sales — is already sitting in one profile. No CRM export, no crossed fingers that it's up to date.

She builds the segment: mid-market clients in APAC with an engagement score above 70, plus everyone who showed up last year. The score matters here — it's dynamic, weighted toward recent behaviour, so the list reflects who's actually paying attention this month, not who filled out a form back in the spring.

This segment is going to do a lot of work over the next two months. It's also, in miniature, the whole difference between marketing automation and a Marketing OS — automation fires on a schedule, but this list only exists because the platform actually knows who these people are.

Event Registration Page and Public Event Listing

By the end of that first week, the segment is locked and she builds the event itself — inside her existing campaign, not off to the side in some other tab — and puts together the form: name, company, dietary restrictions, which session they actually care about.

Registration goes live seven weeks before the event, and the page shows up in two places at once — Good Bards' own listing and embedded on the company website — without a single ticket filed with the dev team. The old way meant three days waiting on a Jira ticket she'd inevitably have to chase down herself, which on a compressed timeline was three days she didn't have. The confirmation email carries an "Add to Calendar" button, because half the no-shows she's ever dealt with weren't people who changed their minds — they just forgot an event that was seven weeks away when they signed up.

Email Marketing by Audience Group

Registration doesn't fill itself, so over the following weeks Camille runs a drip, not a single blast, all under the same email marketing umbrella:

• Week 7 out: the save-the-date and invite go to her core segment

• Week 5 out: a sharper nudge to the high-value accounts who still haven't opened anything

• Week 3 out: a softer, almost-lazy note to last year's attendees, who barely need convincing

Every send updates the same lead record instead of quietly drifting into its own list somewhere. Before, keeping track of who'd already been emailed — and who'd already registered, so she wasn't re-inviting someone who'd signed up two weeks earlier — meant checking three different tools. Now it's one thread, checked once a week instead of stitched together the night before each send.

Tracking Invited, Registered, and Attending Status Over Time

Across those same six or seven weeks, RSVPs trickle in unevenly — a slow first fortnight, then a real jump after the week-5 nudge, another after the early-bird deadline. She doesn't need a spreadsheet to sort out who's invited versus who's actually registered; the event record tracks status, cancellations, and all of it in one place, and every change updates the lead's score in the CDP in real time. By week 2 out, she can see exactly who's warming up and who's gone quiet — which is what tells her the reminder sequence needs to start soon, not just who to chase.

Automated Event Reminders

One week out, she sets the reminder sequence and lets it run — a first nudge seven days before, a second forty-eight hours before, timed against each person's own registration date rather than one blanket blast to everyone on the same clock. It's the kind of task that always slipped before, not because it's hard, just easy to lose in a week already full of last-minute logistics: catering counts, badge printing, confirming the AV vendor showed up on the calendar too.

QR Code Check-In for Event Attendance

On the day itself, she's running the door — the part of any event she used to dread most. A laptop that couldn't hold the venue Wi-Fi, a colleague squinting at a printed list, someone's name spelled wrong and a five-minute argument about whether they're actually registered. This time every attendee gets a unique QR code, and check-in is just a phone and a scan. The very first one doesn't read — smudged screen, bad lighting, the usual — and for a second she braces for the old chaos. Instead she just types the name in, checks him in manually in three taps, and the line doesn't even notice. Attendance lands in reporting and lead scoring the moment someone walks through the door, and any no-shows get their seats auto-filled from the waitlist.

Post-Event Communication and CSAT Survey Feedback

She doesn't wait until the event is actually over to plan what happens next — both of these were built the week before, so they fire on their own without her touching anything on the day itself.

The morning after, a thank-you and follow-up goes out to everyone who checked in — nothing groundbreaking, but it lands while the event is still fresh instead of two weeks later when nobody remembers going.

Three days after, the survey follows. She's doing a CSAT survey to see how the sessions actually landed, and let the AI draft a first pass of questions the week before rather than starting from a blank form on the day. What she likes is that responses don't just pile up in a report somewhere as they trickle in over the following week — a low score can trigger something different, a flag, a follow-up, without her having to notice it herself and act. And because registered-but-didn't-show is its own status, that group gets a different message entirely, sent the same week: not a thank-you, but a gentle "sorry we missed you."

Event Reporting and Analytics

About ten days after the event, once most of the survey responses are in, she pulls the final report — and she's never building it from six exported CSVs. Registrations, attendance, follow-up engagement, and survey results are already sitting in one report, tied back to each lead's history in the CDP. When her CMO finally asks how it went, it's not "let me pull that together by Friday." It's a link.

Marketing OS vs. Marketing Automation: Why This Matters

Nothing about this event — not the segmenting, the form, the seven weeks of emails, the reminders, the check-in, the survey, or the report — ever required switching tools or exporting a list to reconcile against another list. It's all the same customer data, read and written by the same system for two straight months. That's what a Marketing OS actually gets you over plain marketing automation: not faster emails, but one connected picture of an event that holds together from the first segment eight weeks out to the last survey response ten weeks later.

It matters more for teams working out of Singapore and across Asia, where marketing has to run across languages and a stack that's usually more fragmented than the US or Europe equivalent, and where an eight-week runway rarely survives four disconnected tools without something falling through. It's also why more teams are moving past standalone email marketing toward something built to hold an entire campaign together, not just send the emails inside it.

Camille's event didn't come together because she moved faster during crunch week. It came together because every piece of it, from the segment she built eight weeks out to the survey response that landed ten weeks later, never left the same system.