Skip to content
English
More support
Log into SimpleEvents Dashboard
  • There are no suggestions because the search field is empty.

What template tokens are available

In this article we explain all the different token and how you can use them in your landing page and email templates


Enterprise plan is required for these features. Upgrade today.

Enterprise plan users can personalize Landing Pages and Email campaigns by embedding event tokens—placeholders that are dynamically replaced with event-specific data at runtime. This guide describes each available [event:*] token, explains what value it injects, and provides examples of how to use them in your content.

How It Works

  1. Define Your Content
    In your Landing Page HTML or Email body, include tokens like [event:title], [event:date], or [event:url] wherever you want the corresponding event data to appear.

  2. Publish or Send
    When your page is rendered or your email is delivered, the system automatically replaces each token with the actual value for the given event.

  3. Result
    Recipients see a fully populated page or email—for example, the real event title, date, registration link, and more.

Available tokens

Token Injected Value Example Output
[event:id] The event’s unique internal identifier (integer). 12345
[event:hash] A secure hash for the event, used for tracking or action URLs (string). a1b2c3d4e5f6...
[event:title] The event’s name or title (string). Quarterly Town Hall
[event:url] The public registration link for the event (URL string). If not set, returns an empty string. https://example.com/register?event=12345
[event:formId] The HubSpot Form ID associated with the event (string). If not set, returns an empty string. abcd1234-efgh-5678-ijkl-9012mnopqrst
[event:dateSpan] A formatted date range for multi-day events, adjusted to your account’s time zone (string). July 20 – July 22, 2025
[event:timeSpan] A formatted time range (start–end) for the event, in your account’s time zone (string). 9:00 AM – 5:00 PM
[event:date] The event’s start date, formatted as F j, Y (e.g., July 20, 2025) in UTC. Returns an empty string if unset. July 20, 2025
[event:time] The event’s start time, formatted as g:i A (e.g., 2:30 PM) in UTC. Returns an empty string if unset. 2:30 PM
[event:location] The event’s physical or virtual location (string). If not set, returns an empty string.

Conference Room A / Zoom or the Address
[event:surveyURL] The post-event survey link (URL string). If not set, returns an empty string. https://example.com/survey?event=12345
[event:description] The full HTML description or summary of the event (HTML string). <p>Join us for a deep dive into Q3 initiatives…</p>
[event:actionURL] A URL generated for call-to-action buttons or QR codes, based on the event hash (e.g., for check-ins or special landing pages). https://example.com/action/a1b2c3d4e5f6


Detailed Token Descriptions

[event:id]

  • What it is: The system’s internal numeric ID for your event.

  • Use case: Tracking or conditional logic in advanced templates.

[event:hash]

  • What it is: A secure, unique hash string identifying the event.

  • Use case: Append to custom URLs for one-time links, QR codes, or additional tracking.

[event:title]

  • What it is: The official title of the event as set in the event editor.

  • Use case: Display prominently in email subjects, headers, or page titles.

[event:url]

  • What it is: The attendee-facing registration link.

  • Use case: Use in “Register Now” buttons or plain-text hyperlinks.

[event:formId]

  • What it is: The ID of the HubSpot form embedded on your Landing Page.

  • Use case: Dynamically load the correct form for each event without manual HTML updates.

[event:dateSpan] & [event:timeSpan]

  • What they are: Human-friendly range displays for multi-day events and schedule windows.

  • Use case: Ideal for banners or summary sections showing “July 20–22, 2025” and “9 AM–5 PM.”

[event:date] & [event:time]

  • What they are: The start date and time in UTC, formatted for clarity.

  • Use case: Great for email reminders: “Your session starts on July 20, 2025 at 2:30 PM UTC.”

[event:location]

  • What it is: Venue name, address, or virtual link.

  • Use case: Embed in confirmation emails or “Find us at” sections on your Landing Page.

[event:surveyURL]

  • What it is: Link to post-event survey to collect feedback.

  • Use case: Include in “Thank you for attending” emails or on post-event pages.

[event:description]

  • What it is: Rich-text (HTML) event summary, including images, links, and formatting.

  • Use case: Populate detailed event overviews without maintaining duplicate copies of the description.

[event:actionURL]

  • What it is: A generated URL based on the event hash, suitable for action buttons or QR code encoding.

  • Use case:

    • Button:

      <a href="[event:actionURL]" class="btn btn-primary">Access Your Event</a>

Usage Examples

Email Template Snippet

<p>Hello [contact:firstName],</p>
<h2>Reminder: [event:title]</h2>
<p>
  📅 Date: [event:date] at [event:time] UTC<br>
  📍 Location: [event:location]
</p>
<p>To register or view details, click below:</p>
<p>
  <a href="[event:url]" style="background-color:#007bff;color:#fff;padding:10px 20px;text-decoration:none;">
    Register Now
  </a>
</p>
<p>Can’t make it? Fill out our survey: <a href="[event:surveyURL]">Event Survey</a></p>

Best Practices

  • Test Before Sending: Always send a test email or preview your Landing Page to verify tokens resolve correctly.

  • Fallbacks: If a token might be empty (e.g., no surveyURL set), include conditional copy or default messaging.

  • Time Zones: Date/time tokens use UTC by default. If you need a different time zone, adjust using your account settings or the event editor.

  • HTML Safety: When using [event:description], ensure your template allows raw HTML to render.

By leveraging these [event:*] tokens, you can maintain a single template for all events, reduce manual updates, and deliver a personalized experience to every recipient. If you have questions or need assistance enabling tokens in your workspace, contact Support → Enterprise Plan.