search
Ctrlk
HomepageBlogContact Sales

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.

hashtag
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.

  1. If the alert is red: 1-a. Refer to the User Identifier document to send User Identifier information. 1-b. Use the button below to check the Real-time Exposure Status to verify that the User Identifier selected as the distribution basis exists.

  1. If the alert is yellow: 2-a. Use the button below to check Real-time Exposure Status for users exposed within the last 1 hour. If no users have been exposed, check again after a user has been exposed. 2-b. If users have been exposed but the alert persists, a code change may have caused the User Identifier selected as the distribution basis to fail. Refer to the User Identifier document to send the User Identifier.

hashtag
2. Event Delivery

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

  1. If the alert is red: 1-a. Send the events listed in the box below to Hackle. Click on each event item to check its real-time status. 1-b. If the events have been sent but still appear in the box, the User Identifier information selected as the distribution basis may be missing from the event delivery. Refer to the User Identifier document to send events including the User Identifier information.

  1. If the alert is yellow: 2-a. Click on each event item to check whether that event has been sent within the last 1 hour. 2-b. If events have been sent within the last 1 hour but the item still appears, the User Identifier information selected as the distribution basis may be missing. Refer to the User Identifier document and verify that the events are being sent with the User Identifier information.

hashtag
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.

hashtag
4. Data Calculation

Checks whether any of the goals, retention, or funnels registered for the A/B Test have a calculation result of 0. This can be checked 1 hour after the A/B Test starts.

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

  2. If a filter has been applied to the items shown in the box below, check that the event property information used for the filter is being collected correctly. Go to Event Management > the relevant event detail page > Event Property to verify the information exists.

PreviousA/B Test StatusNextVariation Distribution

Last updated