For the complete documentation index, see llms.txt. This page is also available as Markdown.

Health Check

Use the Health Check to verify that everything is ready to start an A/B Test, or that the test is running correctly.

1

User Identifier Delivery

Checks whether the User Identifier selected as the distribution basis for the A/B Test is being sent to Hackle correctly.

2

Event Delivery

Checks whether the events used when registering goals, retention, and funnels in the A/B Test are being sent correctly.

3

A/B Test Exposure

Checks whether at least one user has been exposed to the A/B Test and distributed to a test group. You can verify whether users have actually participated in the A/B Test in the production environment. This can be checked 1 hour after the A/B Test starts.

  1. Check that both the User Identifier delivery and Event delivery items are normal.

  2. Verify that at least 1% of traffic has been allocated. If the test has started but traffic is still at 0%, users will not be exposed to the A/B Test.

  3. Check that the A/B Test Targeting is working correctly. Property information used in targeting conditions must be collected. Refer to the Set Targeting document.

4

Data Calculation

Checks the calculation results of the registered goals, retention, and funnels. For any item whose result is 0, go through the checks below in order.

  1. Verify that the A/B Test integration, event delivery, and A/B Test exposure are all normal.

  2. For items with a filter applied, check the event property used in the filter. Open the relevant event in Event Management and check its Event Property.

Last updated