Before you start
You should already have:- The ShortPen Pixel is installed on the site where the event occurs.
- At least one event created.
Reminder: events are not retroactive. They record from the moment they’re created or enabled.
Quick fixes (do these in order)
1. Confirm the pixel is firing on the destination page
- Open the destination page and run the checks in “How to confirm your ShortPen Pixel is working” (in-app verification and basic network checks).
- Or verify live via event testing panel (you’ll see Pixel detected and incoming test events).
- If missing/blocked, reinstall the pixel.
Expected: pixel detected and incoming hits visible in the event testing panel.
2. Ensure the URL has Event Tracking enabled
- Edit the ShortPen link/QR → Settings → toggle Enable Event Tracking → Save.
3. Validate the event’s trigger and scope
Make sure your test actually meets the event’s conditions:- The event exists, is active, and is tied to the same workspace that owns your URL.
- URL-triggered events. The visitor really reaches a path that matches your rule (e.g., contains
/thank-you). Enter only the path/slug, not the full domain. - Code-triggered events. The JS snippet runs at the right moment (e.g., on button click) and the Pixel loads before it fires.
- Avoid duplicate pixels or duplicated event code which can interfere or double-fire.
If the event comes from an integration, remember it may not appear in your Events list and isn’t editable. Verify via the integration setup and confirm live in the Event Testing Panel.
4. Test with the Event Testing Panel
How to test ShortPen events with the Event Testing Panel
Test your ShortPen events live using the Event Testing Panel to verify pixel activity and event triggers instantly.
Less common causes (quick checks)
- Wrong workspace/domain context. Make sure you’re viewing reports where the link and its event live.
- Conditional redirects block the trigger. Device/geo rules might send you to a page that doesn’t fire the event.
- Duplicate or multiple pixels. Remove extra snippets that can interfere with testing.
- Strict blockers. Ad/tracking blockers can prevent firing during tests. Temporarily disable for your test session.
Related links
- What is the ShortPen Pixel
- How to create your first event in ShortPen
- How to manually install the ShortPen Pixel
- How to install the ShortPen Pixel with the Shopify app
- How to confirm your ShortPen Pixel is working
- How to test ShortPen events with the Event Testing Panel
- How to enable Event Tracking on a ShortPen Link
- How to view conversions for a single ShortPen Link