Event Tracking & KPI Setup

Discover FlowSync example at the end of the article.

Event tracking and KPI (Key Performance Indicator) setup are essential steps to measure the impact of your experiments and feature rollouts. By defining and tracking the right KPIs, you can objectively determine which variations or features drive better outcomes for your business and users.

Prerequisites

Before you start, ensure you have:

• Access to the AB Tasty FE&R platform and the necessary permissions to edit campaigns.

• Installed the FE&R SDK or implemented the Decision API in your application or website. This is required to send event data and track KPIs. See the SDK/API setup documentation (recommended for developers).

Main Steps to Follow

1

Identify KPI to track

• Collaborate with product managers or stakeholders to decide which KPIs are most relevant for your experiment (e.g., conversions, clicks, page views, transactions).

• KPIs should align with your business goals and user stories.

2

Implement Event Tracking

Use the SDK/API to send event data (hits) corresponding to the KPIs you want to track. This step is crucial for collecting data that will populate your reports.

3

Configure KPIs in the plateform

• In your campaign setup (Your campaigns > campaign name > Goals), select or create KPIs to follow. You can choose from four types: Transaction, Event, Pageview, or Screenview.

• For each KPI, ensure the event name in your code matches the KPI name in the platform.

• Set a primary KPI (main goal) and, if needed, secondary KPIs (additional metrics to monitor

Example: How Ren and Jess Set Up KPI Tracking for Their First Experiment

Once we had the onboarding experiment ready, Ren and I had to make sure we were actually measuring the right things

1. Identifying the KPIs Ren started by sharing the business goal: increase onboarding completion among new users. Together, they defined:

• Primary KPI: onboarding_completion (Event)

• Secondary KPI: step_2_dropoff (Pageview/Event)

Ren added both KPIs inside the FE&R campaign, making sure the names matched exactly what Jess would implement.

2. Implementing Event Tracking Jess then updated the codebase to send events using the SDK:

• When a user finishes onboarding → send "onboarding_completion"

• When a user exits at step 2 → send "step_2_dropoff"

She made sure these events were triggered consistently across both flag variations, so the reports would be comparable.

The SDK integration made it easy: every time an event fired, I could see it show up immediately in the Live Hits section. That helped me confirm everything was wired correctly before we launched.

3. Configuring KPIs in the Platform Back in the FE&R interface, Ren selected:

• Primary KPI: Onboarding Completion

• Secondary KPI: Step 2 Drop-off

She kept the definitions simple, so the team could focus on understanding user behavior without over-instrumenting their first test.

4. Ready to Measure Impact With KPIs configured and events flowing, Ren launched the experiment.

For me, this was one of the smoothest parts of the setup

I knew exactly what Ren wanted to measure, and she could see the metrics appear in real time. When our roles stay aligned, setting up event tracking becomes almost effortless.