Integrations

Spar can run with no integrations connected, but each one you add makes the audit and the test workflow more powerful.

Google Analytics 4

Pulls real funnel data, traffic sources, and page-level metrics. Unlocks the Metrics page, behavioral observations on Data, and impact scoring on opportunities.

Connect by signing in with the Google account that owns the GA4 property, then picking the property to link.

Microsoft Clarity

Brings in heatmap and session-replay signal. Used to confirm friction points on specific pages and to enrich behavioral observations.

Shopify

For Shopify stores. Reads the live theme, products, and checkout flow so crawl results are accurate. Also enables Shopify-native test deployment via the Spar theme app extension.

GrowthBook

If your team runs experiments in GrowthBook, connect it to:

• Surface existing GrowthBook experiments as "orphan suggestions" on the Tests page.
• Deploy new Spar tests directly to GrowthBook.

Intelligems

For teams using Intelligems for price testing. Same idea as GrowthBook — existing experiments surface in Tests, and new tests can be deployed there.

Convert

For teams running A/B tests in Convert.com. Same idea as GrowthBook and Intelligems — existing experiments surface in Tests, and new tests can be deployed there as draft experiences.

Connect by pasting your API key and API key secret (found in your Convert account under Project Settings → API keys), then selecting the account and project to target.

Convert supports two experiment types from Spar:

• Visual editor — A/B, A/A, MVT, multipage, and deploy experiences.
• URL redirect — split-URL tests where each variant is a different URL.

Jira

Connects your Atlassian Jira workspace so prioritized fixes show up in your engineering backlog automatically.

Connect by signing in with the Atlassian account that has access to the project you want to use, then pick the Jira project and the initial status new issues should land in.

Once connected, dragging a fix card into the Prioritized lane on the Fixes board creates a Jira issue with the fix title as the summary, the description as the body, and a link back to the fix in Spar. The issue key shows up on the fix card with a link to Jira.

If Jira is disconnected or the API call fails, the fix still moves to Prioritized and the card shows a Create in Jira button. Clicking it retries the issue creation; the original error appears as a toast if it fails again.

The integration is one-way for now — Spar creates the issue, but changes you make in Jira don't sync back to the fix card.

Asana

Connects your Asana workspace so prioritized fixes are automatically created as tasks in the project and section you choose.

Connect by authorizing Spar with your Asana account, then pick the workspace, project, and section where new tasks should land.

Once connected, dragging a fix card into the Prioritized lane on the Fixes board creates an Asana task with the fix title as the task name, the description as the notes body, and a link back to the fix in Spar. The task URL appears on the fix card so engineers can pick it up without re-keying the work.

If Asana is disconnected or the API call fails, the fix still moves to Prioritized and the card shows a Create in Asana button. Clicking it retries the task creation; the original error appears as a toast if it fails again.

The integration is one-way for now — Spar creates the task, but changes you make in Asana don't sync back to the fix card.

When to connect what