Overview

The Web SDK Test page opens your website in a new browser tab with a dedicated test session. Every Web SDK activity in that tab, including page loads, events, and identity calls, streams live into the test page, where you can inspect each event and its properties. This lets you verify your implementation in minutes, without waiting for data to appear in reports.

Use it to check that:

• The Web SDK loads on the intended pages.
• Your events fire with the correct name, revenue, and properties.
• The customer user ID (CUID) is set after login or signup.

Run a test whenever you first integrate the SDK or change your event setup.

Prerequisites

Before you run a test, make sure you have:

• A web app in AppsFlyer. For more information, see Create a web app in AppsFlyer in Onboard Web Performance Measurement.
• The AppsFlyer Web SDK is deployed on the pages you want to test. For more information, see the Integrate AppsFlyer Web SDK section.

Run a test

Once your prerequisites are in place, run a test as follows:

1. In AppsFlyer, from the side menu, go to Settings > SDK Integration Tests.
2. Select Web SDK Test.
3. In the Test your Web SDK dialog:
   • Select your web app.
   • The URL field is pre-filled with the app's configured website URL. The test runs on this URL by default. Change it to test a specific page.
4. Click Start test. Your website opens in a new browser tab with a dedicated test session. You don't need to do anything there.
5. Return to the Web SDK Test page. Events from the test tab appear automatically in the Live events table as you browse and interact with your website.

View the Live events table

Each row in the Live events table shows the event timestamp, type, name, and validation status.

The Live events table also supports:

• Event details: Click a row to open the Event details panel, to view every property the event includes, for example, revenue and event values.
• Search: Use the search box to find a specific event.
• Export: Click Export CSV to download the results.

Restart or clear a test

Use one of these options to restart or clear a test:

• Restart test: Clears the event list and opens a new browser tab with a new test session. You can use this to start a clean run.
• Restart with new app / URL: Reopens the setup dialog to test a different web app or page.
• Clear logs: Clears only the event list. The current test session and browser tab stay active, so new events keep streaming in.

Common testing scenarios

You can just run a test after every change to your Web SDK setup or events. It's the fastest way to catch issues before they affect your data. Common scenarios include:

• First Web SDK integration: Browse the pages where you installed the SDK and verify that a pageLoad event appears for each one.
• Adding or changing an event: Trigger the event on your website, for example, complete a purchase. Then verify that an EVENT row appears with the correct event name, revenue, and properties in the event details.
• Implementing customer user ID: Sign up or log in on your website and verify that a setCustomerUserId event appears. Setting the CUID improves attribution accuracy and unifies user journeys across platforms.