Skip to content

Commit e5a63f1

Browse files
committed
explain how to create an event
1 parent 70b0b8f commit e5a63f1

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

src/connections/auto-instrumentation/event-builder.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,3 +38,20 @@ Segment separates signal collection from event creation. Signals represent raw u
3838

3939
Signal detection is active for 24 hours after you generate activity. Detected signals are available in the Event Builder for 72 hours.
4040

41+
## Create an event
42+
43+
You can create events by selecting individual signals or combining multiple signals in sequence.
44+
45+
Follow these steps to create an event:
46+
47+
1. Find the signal you want to use and click **Configure event**.
48+
2. Add one or more conditions. The order matters; Segment evaluates them in the order you add them.
49+
- For example, to track a successful login, first select a **button click** signal, then the **network response** signal.
50+
3. Select properties from the signal(s) to include in your event.
51+
4. Map those properties to your targeted Segment event fields.
52+
5. Name your event. This name will appear in the Debugger and downstream tools.
53+
6. Click **Publish event rules** to activate the event in your workspace.
54+
- You must publish each rule before Segment starts collecting data for the event.
55+
56+
For example, suppose a user taps an "Add to Cart" button. You can define an `Add to Cart` event by combining the button click signal with a network response signal that includes product details. You can then map properties like product name, ID, and price directly from the network response to your event.
57+

0 commit comments

Comments
 (0)