Working with Your Event Stream

Where events come from

Events are the raw material of StretchAnalytics, and the good news is you rarely have to think about creating them. They are captured automatically as people interact with your suite: a visitor views a page (page_view), clicks a call to action (cta_click), submits a form (form_submission), or interacts with a messenger lane. You don't install a snippet or call an API from the workspace — the suite records activity for your organization and StretchAnalytics reads it.

What an event contains

Each event carries a rich set of fields, including:

• event_name — the type of signal (page_view, cta_click, form_submission, messenger…).
• brand / site / page_path / page_url — where it happened.
• referrer — where the visitor came from.
• session_id / visitor_id — who (anonymously) did it and in which session.
• cta_name / form_name / messenger_lane — the specific element involved.
• metadata_json — extra context, such as country.
• created_at — when it happened.

Behind the scenes events also carry campaign and device context (source, medium, campaign, device type, browser, OS, country, region) that powers grouping and rollups.

Step-by-step: browse recent events

1. Open StretchAnalytics.
2. Go to the Events view (or read the Recent events panel on the overview).
3. Scan the list — the most recent events appear first, with name, brand, site, page, and timestamp.
4. Use this as a live tail to confirm tracking is working after you publish a page or launch a campaign.

Step-by-step: analyze events by property

To go beyond the raw list, use Explore:

1. Open Explore.
2. Choose the event you care about.
3. Group by brand, site, page_path, cta_name, or country.
4. Optionally bucket by hour or day and set a date range.
5. Run to see the event broken out the way you need.

Step-by-step: export events

1. Open the Export action.
2. Set a from/to window and optionally a specific event_name.
3. Export. You get a CSV of matching events (up to 5,000 rows) with the key fields for offline analysis.

Example

After launching a new pricing page, a marketer opens Recent events and immediately sees page_view events with the new page_path arriving — tracking confirmed. She switches to Explore, groups cta_click by cta_name, and learns the "Start free trial" button outperforms "Contact sales" three to one. Finally she exports the week's form_submission events to CSV to hand to sales.

Tips

• Use Recent events as a smoke test right after publishing — if the events show up, tracking is working.
• Event names are exact strings. page_view and pageview are different; use the exact name recorded.
• To analyze events, reach for Explore; to read them raw, use the events list; to take them elsewhere, use Export.
• Anonymous visitor and session identifiers power funnels and retention — they don't personally identify anyone.

FAQ

Can I manually add events from the workspace? No — the workspace is a read-and-report surface. Events are recorded automatically as activity happens across the suite.

Why don't I see an event I expected? Confirm the interaction actually occurred for your organization and check the exact event name in Explore. Widen your date range if needed.

How far back does the stream go? The events list shows the most recent activity; for a bounded historical pull, use Export with a from/to window.