Event pages

Event pages

Event pages let you publish a structured event destination directly inside Nimriz. Each page gets its own branded short link and QR code, so you can share event details, collect RSVPs, and keep the public destination updated without rebuilding or reprinting your QR.

Because the page is tied to a standard Nimriz short link, you can update the schedule, venue details, hero image, or RSVP settings after you share the link. The outward-facing share object stays the short link and QR, while the page itself is served on a Nimriz page URL.

---

Plan availability

Event pages are available across plans within the workspace's shared hosted-page cap. RSVP records count toward the workspace's hosted-page response pool.

---

Before you start

Have these details ready before you create an event page:

• A connected short-link domain in your workspace.
• The event title, schedule, and location details.
• The public description you want people to read before they RSVP.
• An optional hero image sized for mobile-friendly sharing.

Event pages always create and own their own short link. Share that short link or its QR code rather than the direct public page URL so campaign and scan analytics stay attached to the same Nimriz link.

---

What an event page includes

Each event page includes:

• The event name
• A structured date and time
• A structured location
• A detailed description
• An optional hero image
• Optional RSVP collection
• A branded short link
• A downloadable QR from the owning short-link record
• A Nimriz-hosted public page URL

The short link remains the recommended share surface because it preserves standard Nimriz tracking and QR behavior.

---

Creating an event page

1. Go to Pages in the sidebar.
2. Click New page, then pick the Event with RSVP starter from the Pick a starting point picker-or choose Build from scratch and select Event page as the page type.
3. In Build, select the Domain, optional custom slug, and QR preset for the short link that will own the page.
4. Add the Page title and event description.
5. Set the start time and any optional end time or time-zone label.
6. Add the venue and optional map link.
7. Turn RSVP on if you want attendees to respond directly from the page.
8. In Design, optionally upload a hero image.
9. Use Save draft to keep the page as a draft, or continue to Track and finish with Save and publish.

Event page titles are capped at 60 characters. Descriptions are capped at 160 characters, with schedule and location details handled in their own structured fields.

The editor's Design tab includes theme presets and styling controls, and a live preview panel uses the same render path as the public event page.

---

Drafts, publishing, and sharing

• Draft lets you build the page before promoting it publicly.
• Published makes the page available from the page's short link and QR code, then shows a share modal with copy, QR download, and QR customization actions.
• Updating event details after publishing keeps the same short link and QR code active, so printed flyers and posters stay valid.

After publishing, use Share page from the Pages list or editor to reopen the sharing summary, share the short URL to common apps, and download the QR. Use Customize QR when you want to jump straight into QR styling.

This makes event pages useful for real-world promotions where venue details, RSVP settings, or timing might change after you first publish the QR.

---

Hero image uploads

Event pages currently support hero image uploads in:

• PNG
• JPEG
• WebP
• Up to 2 MiB

Hero images are optional. If you do not upload one, the page still publishes normally. When the profile uses the banner layout, the hero image replaces the banner area.

---

RSVP behavior

When RSVP is enabled, the public page collects:

• Name
• Email
• A bounded response state: going, maybe, or not going
• A bounded guest count when the event allows more than one attendee per RSVP

You can optionally set:

• An RSVP close date/time (must be before the event starts)
• A maximum guest count per response (1 to 10)
• A confirmation message shown after submission

If the same attendee submits again with the same email address, Nimriz updates that attendee's current RSVP instead of creating a second visible response row for the page.

---

Public page behavior

The public event page is:

• Standalone: no dashboard navigation or account UI
• Mobile-friendly: optimized for QR scans and short-link visits
• No login required: anyone with the link or QR can view it

When the page includes enough event details, it also provides:

• An Add to calendar action that downloads a calendar file
• An Open map action when location details are available

Pages always show the Nimriz footer in this version.

---

Analytics

Event pages keep Nimriz's two-layer tracking model:

Redirect-layer analytics

When someone clicks the short link or scans the QR, Nimriz records the normal short-link event, including QR scans as qr_scan.

Page engagement analytics

Once the visitor reaches the hosted page, Nimriz records:

• hosted_page_viewed
• map_opened
• calendar_add_clicked
• rsvp_submitted

These events remain tied back to the owning short link. You can review them in the page's Track tab, Analytics›Pages, Realtime, and the owning link's hosted-page summary. IP addresses and full User-Agent strings are handled with Nimriz's privacy-aware analytics posture rather than stored raw.

---

Managing responses

Open Pages, then select the event page you want to review. The page detail view includes:

• Event content editing
• Theme controls
• RSVP settings
• A live preview panel
• A response list showing the latest RSVP per attendee email

Deleting an event page also removes the short link that belongs to that page. Associated RSVP history is removed with the page. If you want to keep the short link, edit the page instead of deleting it.

---

Troubleshooting

I cannot publish the event page

• Confirm the page has a title, schedule, and enough public detail to save cleanly.
• Confirm the workspace has at least one connected domain.
• Remove and re-upload the hero image if the file appears attached but is not rendering in preview.

The calendar or map action is missing or inactive

• Calendar download requires a valid event start time. Without one, the Add to calendar button appears inactive instead of downloading a file.
• Map actions require usable location details or a map URL. Without them, the Open map action is hidden.

An attendee changed their RSVP and I only see one row

This is expected. Event pages keep the latest visible RSVP per attendee email so the dashboard reflects the attendee's current response.

I need lead capture before the event details

Event pages do not use the hosted-page lead gate. For event workflows, use the built-in RSVP flow instead.

---

Related guides

• Custom QR codes
• Custom micro-pages
• Document pages
• Analytics overview