Alby Documentation

What are Alby Microsites for?

Alby Microsites are for creating branded event web pages without building a separate website for every event. A microsite can be a simple public landing page, a livestream page, a registration page, a private event hub, a lead capture page, or a multi-page virtual event experience.

Use a microsite when you need one central event link for attendees, clients, sponsors or viewers. The microsite can hold event information, speaker details, agendas, sponsor content, livestreams, Zoom meetings, interaction tools, voting access and other embedded event content.

• For public events: create a branded page that anyone with the link can view.
• For controlled events: use password, registration, lead capture or invite-only access.
• For virtual and hybrid events: embed Zoom, livestreams, Alby Interact and Alby Vote into the event page.
• For client events: build a custom look and layout without needing a custom website project every time.

Listed and unlisted microsites

Microsite visibility controls whether an event can be discovered from public Alby listing areas, including the public Upcoming Events page. It is separate from the event access type, which controls who can actually enter the microsite.

Allow search engine indexing

The Allow search engine indexing checkbox controls whether Alby tells search engines they may index the public microsite pages for that event. When it is turned off, Alby adds a noindex instruction to the microsite pages so search engines should not include those pages in search results.

• On: search engines may index the published microsite pages, if the event is otherwise public and reachable.
• Off: Alby asks search engines not to index the microsite pages, but people with the correct event link can still open the event if the event is active and access rules are satisfied.
• Unlisted and invite-only events: indexing is disabled automatically because those events are not intended for public search discovery.

Page Builder

Page Builder is the visual editor used to design microsite pages. It lets event administrators place, resize and configure page elements on a canvas, then save, preview and publish the result.

• Desktop, tablet and phone views let you check how a page behaves on different screen sizes.
• Page settings control page-level options such as the page background and layout settings.
• Element properties appear when an element is selected and only show the settings relevant to that element.
• Preview shows the page as it will appear publicly without making unpublished changes live.
• Save stores the Page Builder layout. Saving alone does not necessarily make a page publicly available.

Microsite elements

Elements are the building blocks placed onto a microsite page. Common elements include text, images, buttons, navigation, embeds, livestreams and product-specific Alby tools.

Each element has its own settings. For example, a text element has rich-text and style settings, while a Zoom element has meeting and display settings. Select an element in Page Builder to edit its available options.

Publish and unpublish

Publishing controls whether a normal microsite page can be viewed by attendees. Saving a page and publishing a page are different actions: saving stores the design, while publishing makes the page available when the event itself is active and access rules are satisfied.

• Published pages can be viewed publicly when the microsite is active and the visitor has permission to access the event.
• Unpublished pages remain editable in Page Builder but are not shown to public visitors.
• Preview is for checking the page before making it live.
• System pages such as registration, lead capture, password and invite-only access are controlled by event settings rather than ordinary page publish buttons.

What makes a public link live?

A microsite link is only live when all of the required conditions line up. If any one of these is missing, the public visitor may see a 404, an access page, or an unavailable message.

• The Alby account must be active and not blocked by billing or account restrictions.
• The microsite event must be active, not draft, inactive, archived or deleted.
• The requested normal page must be published.
• The microsite can be listed or unlisted. Listed events can appear on the public Upcoming Events page. Unlisted events are not discoverable in public Alby listing areas, but direct links can still work.
• The event must not be invite-only to appear on the public Upcoming Events page. Invite-only/private microsites are excluded from public listings.
• The Allow search engine indexing setting does not make a page live by itself. It only controls whether search engines are told they may index the public microsite pages.
• The visitor must satisfy the event access type: open, password, registration, lead capture or invite-only access.
• Any embedded products used on the page, such as Zoom, Interact or Vote, must also be active and correctly configured.

For registration, lead capture and invite-only events, the public journey may start at a system access page before the attendee reaches the published microsite content. For password-protected events, visitors must enter the event password before viewing protected pages.

Microsite event types

Microsite event types control how attendees access an event, whether Alby captures attendee identity, and which system pages are used. Choose the event type before publishing because it affects registration, access links and attendee data.

Open / public microsite

An open microsite can be viewed by anyone with the published page link. This is best for public livestream pages, event landing pages, sponsor information pages and general event websites where individual attendee access does not need to be controlled.

• No shared password is required.
• No registration is required before viewing the page.
• Attendee identity is not captured unless another feature collects it separately.

Password-protected microsite

A password-protected microsite requires visitors to enter a shared event password before they can access the published pages. This is useful for semi-private events where a simple shared gate is enough.

• All approved viewers use the same event password.
• This is simpler than registration but does not provide strong individual identity control.
• It is suitable for low-risk private links, internal previews or client-only information pages.

Registration microsite

A registration microsite requires attendees to complete an Alby registration form before they receive access to the event. Registration can capture required attendee details and custom event fields configured by the event administrator.

• Best for webinars, conferences, tracked livestreams and events where attendee details are needed.
• Registered attendee identity can be used by supported Alby features such as Zoom, Interact and Vote where those features are enabled.
• Registration fields and confirmation emails are controlled by the event setup.

Lead capture microsite

A lead capture microsite collects visitor details before showing event or content pages. It is lighter than a formal registration workflow and is useful when the goal is to capture contact information or interest before allowing access to content.

• Best for marketing pages, product demos, content gates and informal viewer capture.
• Lead capture should not be used as the formal identity source for controlled voting.
• Use registration or invite-only access when attendee identity must be more tightly controlled.

Invite-only / private microsite

An invite-only microsite is for events where the administrator controls the attendee list. Attendees are normally uploaded or added by the event administrator and receive unique access links. Public self-registration is not used.

Invite-only/private microsites are excluded from the public Upcoming Events listing, even if other event details exist in Alby.

• Best for AGMs, internal meetings, board events, client-only events and controlled-access webinars.
• Each invited attendee can receive a unique access link.
• This is the strongest microsite access model when individual access needs to be controlled.

Choosing the right microsite type

• Use open/public when anyone with the link may view the content.
• Use password-protected when a simple shared access code is enough.
• Use lead capture when you want visitor details before showing content, but do not need a full registration workflow.
• Use registration when attendees should formally register and receive event access.
• Use invite-only/private when only a pre-approved attendee list should have access.

Lifecycle and page publishing

Microsite lifecycle status and individual page publishing work together. Draft, inactive or archived events are not publicly available. Normal microsite pages can be published or unpublished individually, while system pages such as registration, lead capture, password and invite-only access are controlled by the event settings.

Embedded tools and attendee identity

Some embedded Alby tools can use attendee identity from the microsite access flow. Zoom may receive the attendee name and email address for meeting join identity, Interact can associate chat or Q&A activity with the attendee where enabled, and Alby Vote can use approved voter access when configured for the event.

For formal voting events, use the dedicated Alby Vote setup and approved voter records rather than relying on lead capture alone.

Zoom Element

The Alby Zoom Element lets an Alby account owner or administrator embed a Zoom meeting into an Alby microsite page using the Zoom Meeting SDK.

1. Connect a Zoom account from Account Settings.
2. Add a Zoom element in Page Builder.
3. Enter the Zoom meeting ID and passcode.
4. Choose the default Zoom view and whether to hide the attendee Zoom view selector.
5. Save and publish the microsite page.

When an attendee opens a published microsite page containing a Zoom element, Alby loads the Zoom Meeting SDK inside the page and joins the configured meeting. If the event uses registration, invite-only access or lead capture, Alby may pass the attendee name and email address to Zoom so the attendee is identified correctly.

Zoom troubleshooting

• Meeting has not started: start the meeting as host in Zoom, then reload the microsite page.
• Zoom account not connected: reconnect Zoom from Alby Account Settings.
• Wrong Zoom account connected: disconnect Zoom in Alby, sign out of Zoom or switch Zoom account, then connect again.
• External/customer Zoom account cannot authorize the app: the Zoom app may need production or beta sharing approval before accounts outside the developer account can connect.
• Layout issues: confirm the page has been saved and published after editing the Zoom element size and display settings.

Data handled by the Zoom integration

Alby stores limited Zoom connection metadata and encrypted OAuth refresh tokens so the connected Zoom account can remain linked. Alby does not store Zoom meeting audio, video, screen sharing content, recordings, transcripts, Zoom chat history or Zoom participant content.

More detail is available in the Privacy Policy and Terms of Service.