VCEDC Event Registration Workflow

Overview

All event registrations for the VCEDC site must funnel into KIT (formerly ConvertKit), which serves as the client's official CRM. The WordPress Events Calendar plugin handles event creation and display on the site, while KIT handles subscriber management, tagging, and downstream automations (e.g., confirmation emails, follow-up sequences).

This workflow was defined during a January 2026 site review after the events page was found to be broken and the KIT integration had not yet been configured.

See also: ^[1]

Architecture

Visitor registers for event (WordPress / Events Calendar plugin)
        ↓
Registrant data pushed to KIT via plugin integration
        ↓
KIT applies event-specific tag to subscriber
        ↓
Tag triggers event automation sequence in KIT
(confirmation email, reminders, follow-up, etc.)

Key Requirements

• KIT is the system of record. All registrants must land in KIT regardless of how the event is managed in WordPress. Data must not remain siloed in WordPress only.
• Tag-based segmentation. Each event should have a unique KIT tag. This allows per-event automations and keeps the subscriber list organized by event history.
• Simplicity and maintainability. The integration must be manageable by future staff without custom code. The client's team (and any successor to Tracey) needs to be able to add events and trust that registrants flow into KIT automatically.

Prior Art: How VCEDC Was Already Using KIT Tags

Before this site rebuild, VCEDC used a tag-based method with a third-party event platform (SiteCast):

1. A unique KIT tag was created for each event (e.g., tag ID 101-3764).
2. That tag ID was entered into SiteCast as a trigger parameter.
3. SiteCast used a templated merge to fire the KIT tag on registration.

This pattern — one tag per event, tag triggers automation — should be preserved in the new WordPress-based workflow.

Implementation Notes

• The Events Calendar plugin is installed on the WordPress site. As of the January 2026 review, it was not yet configured to display events on the Events page, and the KIT integration had not been set up.
• KIT account credentials are stored in LastPass under kit.com.
• Isahaque (developer) is responsible for:
• Fixing the Events page and configuring the plugin to display events correctly.
• Researching and proposing a simple, plugin-based method to push registrant data from Events Calendar into KIT with tag assignment.
• The general contact form on the site already feeds into KIT (confirmed working as of this review). The events integration should follow the same pattern.

Open Questions (as of January 2026)

• Which specific plugin or method will connect Events Calendar to KIT? (Native integration, Zapier, or a dedicated add-on?) Isahaque to investigate and propose.
• Should each event's KIT tag be created manually before the event goes live, or can it be automated?
• Who on the client side is responsible for creating KIT tags and building automations per event?

Action Items

Related

• ^[1]
• ^[2]
• ^[3]