How TrackIt Works

Create interactive, mobile-first content. Link it to NFC tags or QR codes. Track engagement in real time.

1) Build Interactive Content
1) Build Interactive Content
2) Link to NFC or QR
2) Link to NFC or QR
3) Users Engage
3) Users Engage
4) Measure with Analytics
4) Measure with Analytics

1) Build Interactive Content

Use the block-based builder to craft engaging, mobile-first experiences that open from an NFC tap or QR scan. Combine content, media, interactions, and rewards in minutes.

Core Blocks

  • Text, Image, Gallery
  • Button / CTA
  • Theme & Layout controls

Media & Streaming

  • Native Video block
  • YouTube embed with detailed tracking
  • Twitch Live/VOD integration

Interactive

  • Polls and Quizzes
  • Points & Rewards
  • Gamified blocks (e.g., Slot Machine)

Automations & AI

  • Twilio SMS hooks
  • AI-assisted content generation
  • Optional scraping & data utilities

3) Users Engage

When users open your link, they see an interactive TrackIt page powered by your blocks. All key interactions can be tracked.

  • Video playback (native and YouTube)
  • Twitch livestream/VOD actions
  • Poll, quiz, and CTA interactions

Example Viewer

The dynamic viewing route pages/view/[id].js renders your blocks and sends analytics to /api/track.

YouTube tracking captures play/pause/seek/ended events with watch-time and seek distances. Native video emits similar events.

4) Measure with Analytics

TrackIt records structured events server-side in analytics-data.json via pages/api/track.js.

Core Events

  • content_view
  • cta_click
  • poll_submit
  • quiz_complete

YouTube Video

  • youtube_play, youtube_pause
  • youtube_seek (with previousTimenewTime)
  • youtube_ended

Native Video

  • video_play, video_pause
  • video_seek (with previousTimenewTime)
  • video_ended

Twitch

  • twitch_play, twitch_pause
  • twitch_seek
  • twitch_ended (when detected)
  • twitch_event (raw events payload)

Common Payload Fields

  • event, linkId, userAgent
  • Video fields: video, previousTime, newTime
  • CTA fields: url, cta

Server captures IP (from headers) and timestamp for each request. SMS via Twilio is currently disabled by default.

Best Practices

  • Keep content concise and focused on a single action.
  • Use contrasting colors and clear CTAs.
  • Preview on multiple devices before publishing.

Theme & Branding

  • Apply themes (Light, Dark, Midnight, etc.).
  • Use consistent fonts and spacing.
  • Favor readable typography for long text.

Next Steps

  • Set up campaigns and rewards.
  • Monitor analytics, then iterate on your content.
  • Automate follow-ups (e.g., SMS) if desired.