> ## Documentation Index
> Fetch the complete documentation index at: https://shortpen.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> Learn how to create your first event in ShortPen. Set up triggers, verify your Pixel, and start tracking real conversions from your links and campaigns in minutes.

# How to create your first event in ShortPen

**Short answer:** An event records an important action on your site, like a signup, purchase, or form submission, and attributes it to your ShortPen links. To get started, you’ll ensure a [Pixel](/key-concepts/pixel-overview) is active on your domain, create an event with a trigger, verify it fires, and (optionally) enable event tracking on the links that drive traffic.

This page gives you the conceptual overview for creating your first event.

<Info>
  **See:** [Understanding events and conversions in ShortPen](/key-concepts/events-and-conversions-overview)
</Info>

## What events are (and why they matter)

Events extend ShortPen beyond clicks by capturing **what happens after a visitor lands on your site**.

Use events to measure outcomes, signup completed, purchase, lead created, and tie them back to campaigns, links, folders, and tags.

> **In short:** clicks show engagement. **Events show outcomes** .

## Prerequisites

* A working [ShortPen Pixel installed](/getting-started/install-shortpen-pixel) on the destination domain(s) where events will occur.
* Access to create events in your workspace.
* A shortlist of actions you want to track (e.g., `signup`, `purchase`, `lead_created`).

<Tip>
  **Tip:** Events are not retroactive. Create and test them **before** launching campaigns so you don’t miss early conversions.
</Tip>

## How to create your first event

All events share the same high-level flow:

<Steps>
  <Step title="Open Events">
    Go to **Events → New Event** in your workspace.

    ***
  </Step>

  <Step title="Name the event">
    Use a clear, consistent naming convention (e.g., `signup_newsletter`, `checkout_purchase`).

    ***
  </Step>

  <Step title="Choose a trigger type">
    <CardGroup cols={2}>
      <Card title="URL-Triggered" icon="globe-pointer" href="/event-tracking/manage-events/url-triggered-events">
        * Fires when a visitor loads a specific path (e.g., `/thank-you`).
      </Card>

      <Card title="Code-Triggered" icon="code" href="/event-tracking/manage-events/code-triggered-events">
        * Fires when your site/app tells ShortPen that an action happened.
      </Card>
    </CardGroup>

    ***
  </Step>

  <Step title="Test the event">
    Use the **Event Testing Panel** to perform the action once and confirm it appears under Events received (test data doesn’t affect analytics).

    <Info>
      **Learn more:** [How to test ShortPen events with the Event Testing Panel](/event-tracking/manage-events/events-testing)
    </Info>

    ***
  </Step>

  <Step title="Enable tracking on links (optional but recommended)">
    In the link editor, toggle [**Enable Event Tracking**](/link-management/links-settings/enabling-event-tracking) for links that will drive traffic to pages where your event can fire. The toggle appears when a Pixel is active for the destination domain.
  </Step>
</Steps>

## Verification and data flow

* **Pixel dependency.** Events require a [verified Pixel](/event-tracking/shortpen-pixel/pixel-verification) on the domain where the action happens. Without it, the event cannot be recorded.
* **Real-time checks.** The Event Testing Panel confirms that your trigger fires correctly before you go live.
* **Attribution.** Once active, events are attributed to the ShortPen links that sent traffic, visible in [**Link Analytics**](/analytics/link-level-analytics/link-conversion-analytics) and [**Workspace Analytics**](/analytics/workspace-level-analytics/workspace-conversion-analytics).

## Best practices

* **Plan a minimal set.** Start with a few meaningful events (e.g., `signup`, `purchase`) and add more later.
* **Name consistently.** Prefer `noun_action` or `context_action` patterns (e.g., `checkout_purchase`, `newsletter_subscribed`).
* **Test on production URLs.** Staging environments may block or cache scripts differently.
* **Avoid duplicates.** Ensure each action fires **one** event; watch out for multiple triggers or repeated JS calls.
* **Mind quotas.** Your plan may include monthly [event limits](/account-billing-security/plans-and-limits/plans-and-limits), enable tracking where it matters most.

## Troubleshooting

<AccordionGroup>
  <Accordion title="No toggle to enable tracking on links">
    The destination domain isn’t in the Pixel’s **Allowed domains** or the Pixel isn’t installed.
  </Accordion>

  <Accordion title="Clicks but zero events">
    Confirm the event exists and is active, the link has **Enable event tracking** toggled on, and the Pixel is firing on the page.
  </Accordion>

  <Accordion title="Event fires twice">
    Look for duplicate JS calls, multiple Pixels, or overlapping triggers.
  </Accordion>
</AccordionGroup>

## FAQ

<AccordionGroup>
  <Accordion title="Do I need the ShortPen Pixel to track events?">
    Yes. Events require an installed and verified Pixel on the destination domain.
  </Accordion>

  <Accordion title="Can I enable event tracking after a link is live?">
    Yes. Toggle **Enable event tracking** in the link editor. Only future actions will be counted.
  </Accordion>
</AccordionGroup>

## Related links

* [How to install the ShortPen pixel](/getting-started/install-shortpen-pixel)
* [Understanding events and conversions in ShortPen](/key-concepts/events-and-conversions-overview)
* [How to enable event tracking on a ShortPen link](/link-management/links-settings/enabling-event-tracking)
* [How to test ShortPen events with the Event Testing Panel](/event-tracking/manage-events/events-testing)