मुख्य सामग्री पर जाएँ

मीटअप

वेबिनार, सम्मेलन और आमने-सामने के मीटअप चलाएँ, और देखें कि किसने पंजीकरण किया, कौन आया और किसने रद्द किया।

A meetup

Meetups sits under Engage and lists every webinar, conference and in-person meetup with its kind, when it starts, how many people registered and attended, the campaign that groups it and where it comes from. The start is shown in the meetup’s own time zone, and the attended count stays empty until the meetup has started. New meetup takes a name, a kind (webinar, conference, in person or other), a time zone, a start and an end, and optionally a link, an organiser and a description. The start and end are typed as the clock reads in the time zone chosen, the end is at or after the start, and the link is an http or https address.

Who registered and who came

A meetup opens on its own page. People shows four numbers (registered, attended, the attendance rate, which is attended over registered, and cancelled) over one list of everyone on the meetup. Each person appears once, with a status, the day they registered and how long they stayed. A person who came reads attended; otherwise a person whose latest cancellation is not followed by a new registration reads cancelled; otherwise they read registered. A filter narrows the list to one status. Add people records any of the three: paste one email address per line, choose what to mark them as and, for people who attended, the minutes they stayed when known. An address not yet in People creates the person, and each record lands on that person’s timeline as $marketing_event_registered, $marketing_event_attended or $marketing_event_cancelled.

Changing and cancelling

Settings holds the same fields as New meetup and saves changes to them. Cancel meetup asks first, then takes the meetup off the list; the people who registered and came stay on it, nobody new can be recorded while it is cancelled, and it can be restored. When a campaign holds the meetup as an asset, the campaign’s Overview shows its registered and attended counts, as the Campaigns page describes.

Meetups from Zoom, GoToWebinar and Eventbrite

Connect Zoom, GoToWebinar or Eventbrite opens Integrations, where an account on any of the three is connected. Its events then appear in Meetups with the provider as their source, and their registrations and attendance are read from the provider. A meetup that comes from a provider is read only here: its page says where its people come from, has no Add people and no Cancel meetup, and its name, times and link are changed in the provider.

Permissions, API and agents

Reading meetups and their people needs prodantix.marketing_events.read; creating, changing, cancelling and recording people needs prodantix.marketing_events.manage. Meetups are served over REST under /v1/projects/{projectId}/marketing-events, over GraphQL (marketingEvents, marketingEvent, marketingEventPeople, createMarketingEvent, updateMarketingEvent, cancelMarketingEvent, restoreMarketingEvent, deleteMarketingEvent, recordMarketingEventRegistration, recordMarketingEventAttendance, recordMarketingEventCancellation, marketingEventChanges), and to agents over MCP (prodantix.marketing_events.list, prodantix.marketing_events.get, prodantix.marketing_events.people, prodantix.marketing_events.create, prodantix.marketing_events.update, prodantix.marketing_events.cancel, prodantix.marketing_events.restore, prodantix.marketing_events.delete, prodantix.marketing_events.record_registration, prodantix.marketing_events.record_attendance, prodantix.marketing_events.record_cancellation). The people of a meetup are read a page at a time, at most 500 to a page, with the total across every page.