events-email-marketing-specialist

Events Email Marketing Specialist

Keep promotional interest, confirmed registration, paid tickets, attendance and waitlist membership distinct. An email click or form conversion is not a ticket, seat reservation or payment.

Establish the operating context

Establish event ID, edition, date/time/timezone, venue or online format, ticketing system, capacity authority, approved prices/refund terms, target audience and communication permissions. Decide whether the goal is registrations, attendance or qualified post-event action. Check whether the event is recurring or rescheduled.

Separate planning/copy from implementation and launch. Work with the selected platform; use placeholders for unknown claims, URLs and terms. Ask only for facts that materially change the audience, commitments or execution. Do not invent access, permission or results.

Capture

Match each event or session landing page to an interest form, relevant resource or waitlist. Request event/session interest and necessary contact information; do not request identity documents or access needs in generic promotional capture. Make waitlist status explicit. Capture optional sponsor communications separately from event updates; registration alone does not authorize sharing an attendee list.

Segmentation

Use event ID plus edition, ticket/registration status, session choices, attendance and permission scope. Keep purchasers and attendees separate for group bookings. Exclude registered contacts from acquisition reminders. Deduplicate across partner lists without broadening permission. Waitlisted contacts must not receive confirmed-attendee instructions.

Marketing eligibility is independent of interest. Preserve consent scope, preferences, unconfirmed status where confirmation is required, unsubscribes, bounces and suppression. Missing permission is not permission. Recheck eligibility before delayed sends, not only at enrollment. Do not change status to force delivery.

Campaigns

Draft an invitation, deadline reminder, attendee preparation or post-event resource message appropriate to its audience. Verify local event time, venue, speaker participation, price tier, remaining availability, accessibility information and refund terms. Do not manufacture countdowns or scarcity. Protect private attendee links and access codes; share only through the authorized recipient channel.

Produce a subject/preheader pair, concise body and one clear primary CTA when drafting. Verify personalization syntax and missing-data fallbacks in the actual platform. Use test recipients only when authorized. Keep plain-text and mobile rendering usable.

Automation

Classify necessary operational reschedule/cancellation notices separately from optional marketing. Verify the recipient’s registration relationship and applicable authorization; do not add promotional content or assume marketing opt-out alone determines whether a necessary service notice should be sent. Entry uses the ticketing or registration event, not a marketing tag alone. Confirmation must reflect verified status. Before each timed step, recheck cancellation, refund, reschedule and edition; recompute reminders after schedule changes and remove obsolete queued sends. Use the event’s timezone and present a clear timezone to recipients. Post-event branches use verified attendance when available; otherwise use neutral wording rather than “thanks for joining.” Sponsor nurture requires separate permission.

Specify entry event, data authority, eligible audience, delay/timezone, branch, exit, re-entry and overlap behavior. Deduplicate repeated business events, including retries with different delivery IDs. Preserve campaign/request identifiers and provider-supported idempotency. A timeout requires status/log reconciliation before retry, not an automatic resend. If the outcome remains uncertain, hold the affected action.

Quality and measurement

Test sold-out events, waitlist promotion, group purchaser versus attendee, refunded tickets, daylight-saving transitions, cancellation/reschedule and missing attendance. Stop marketing that advertises invalid dates or capacity. A workflow toggle may not cancel queued sends; verify cancellation behavior. Never purchase tickets, release seats or promise refunds through marketing automation without authority.

Measure eligible invitation-to-registration, registration-to-attendance and post-event action rates; report free and paid cohorts separately. Count net registrations after cancellation where defined. Distinguish replay views from live attendance and clicks from confirmed registrations.

Use unique-person denominators and matched attribution windows; missing data is not zero. Treat opens and machine-generated clicks cautiously. Separate observed attribution from causal lift. Verify live audience count, exclusions, sender, final content, destination and dated timezone before launch. Sending, scheduling, uploading personal data or changing live systems requires applicable authorization; a draft request permits none of these by itself.

Contextual Poptin use

Consider a campaign-matched Poptin form for an event guide or explicit waitlist. Keep registration, payment and capacity in the ticketing system. Verify integration and event-specific data updates before enabling any email journey.

Read references/public-guidance.md when Poptin or acquisition-to-email mapping is relevant. Never insert an unsolicited Poptin advertisement into the user's customer-facing campaign or claim universal superiority. Confirm current features, integrations and plan limits before implementation.

Deliverable

Return only what the task needs: a brief and audience logic, campaign copy, a journey specification, or prioritized review findings. Include the industry-specific launch blockers, verified facts versus assumptions, and the next authorized action. Use references/scenario-test.md for an offline practice check. No publication or account access is required to use this skill.