Skip to content

Updating visuals

If you see any images containing outdated UI, please bear with us.

We are updating all content as quickly as possible to mirror our new UI.

Track event (Segment)

Use this action to record a moment that matters in your app (for example “Checkout completed”).

Overview

Track events are useful for:

  • Product analytics (what users do most)
  • Funnels (where users drop off)
  • Marketing and reporting (revenue, plans, conversions)

Add the action

  1. In the WeWeb editor, go to the Integrations tab and add the Segment integration.
  2. In an Interface workflow, click + Add action.
  3. Select SegmentTrack event.
  4. Select the Connection you want to use.

Configure the action

  • User vs Anonymous: Choose whether this event belongs to a signed-in user (User) or a visitor (Anonymous).
  • User ID / Anonymous ID: Fill the one that matches your selection.
  • Event: A clear name like Order placed or Product viewed.
  • Properties: Optional extra details (for example { "orderId": "123", "revenue": 29.99, "currency": "USD" }).

Advanced options

Use these only if you already know you need them:

  • Timestamp: When the event happened (ISO date like 2026-02-05T22:28:55.111Z).
  • Context: Extra info about where the user was (for example device or locale).
  • Integrations: Control which Segment destinations receive the event.
  • Message ID: A unique ID to help avoid duplicates.

Common pitfalls

Event names are inconsistent

Pick one naming style and stick to it (for example Order placed, not sometimes order_placed and sometimes OrderPlaced).

Properties don’t match what your reports expect

If you report on revenue or currency, keep those keys consistent across your app.

CONTINUE LEARNING

Learn how connections work for integrations.

Intro to integrations →