Connected Data Sources Across the Suite

One measurement layer for the whole suite

The reason StretchAnalytics works with almost no setup is that it doesn't rely on a separate data pipeline. It reads live activity from the same platform the rest of StretchSuite writes to. When something happens in another app, it's available to StretchAnalytics — no export, no sync, no snippet. This article explains what each connected source contributes so you know where every number comes from.

What each app contributes

• StretchAnalytics (traffic) — the raw event stream itself: page views, CTA clicks, form submissions, and messenger events, powering the Platform total events KPI and all of Explore, Funnels, and Retention.
• StretchForms (intake) — form definitions and submissions, powering the Form submissions KPI and the intake view of your funnels.
• StretchCRM (crm) — contacts and deals, surfaced as the CRM contacts and CRM deals KPIs.
• StretchSupport (support) — tickets, surfaced as Open support tickets, plus knowledge-base pages as Support KB pages.
• StretchFiles (files) — stored assets, surfaced as the File assets KPI.
• StretchLearn (learning) — courses, surfaced as Learn courses.
• StretchBooks (finance) — invoices, surfaced as Books invoices.
• StretchSearch (search) — search projects, surfaced as Search projects.

Each KPI in the catalog names its source app, so you always know the system of record behind a number.

How the data is scoped

Every read is hard-scoped to your organization. Your organization is resolved from your authenticated session and matched against the organization stamped on each record — it's never taken from a URL or a parameter. That means the same StretchAnalytics app shows each customer only their own contacts, deals, tickets, invoices, and events.

Step-by-step: trace a KPI to its source

1. Open the KPI catalog on the overview.
2. Find the metric you're checking (for example CRM deals).
3. Note its source app (StretchCRM).
4. Open that app to see the underlying records.
5. The KPI reflects what that app has recorded for your organization — the two should agree.

Example

An operator sees Open support tickets jump on the overview. Because the KPI names StretchSupport as its source, she opens StretchSupport, filters to open tickets, and finds a batch created by one customer overnight. StretchAnalytics pointed her to the exact system of record in seconds — the analytics layer summarized, the source app held the detail.

Tips

• Treat StretchAnalytics as the summary layer and each source app as the detail layer — start broad here, drill down there.
• A KPI reading zero usually means the source app has no matching activity yet for your org, not that anything is broken.
• Because all apps share one platform, cross-app views (traffic → form → CRM → invoice) line up naturally.
• New activity in any connected app shows up in StretchAnalytics automatically — no import step.

FAQ

Do I have to connect these apps manually? No. They already share the StretchSuite platform, so their activity is available to StretchAnalytics automatically.

Why does a KPI differ slightly from the source app? Check that you're comparing the same time window and the same status filters (for example, Open support tickets excludes archived ones). The definitions are auditable and consistent.

Can I add a data source that isn't a StretchSuite app? StretchAnalytics reads from the suite platform. For external data, export events to CSV and combine them in your own tooling.