EE A/B Test Goals Do Not Fire For The Variant If The Goal Is Specifc To The A/B Test Rule (Doc ID 2188670.1)

Last updated on MARCH 02, 2017

Applies to:

Oracle Live Help On Demand - Version N/A to N/A [Release ATG v1]
Information in this document applies to any platform.

Symptoms

On : NA version, Rules Engine

ACTUAL BEHAVIOR
---------------
EE A/B Test Goals Do Not Fire For The Variant If The Goal Is Specifc To The A/B Test Rule

When an A/B test is a variant version of an existing rule created - these two rules have different rule IDs.
When adding goals to an A/B test the goal can be set to 'any rule' or restricted to a specific rule.

EXPECTED BEHAVIOR
-----------------------
Goals restricted to the rule being A/B tested should be logged for both the control and variants of the rule.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. create a control rule "My A/B test rule" to use for the AB test - this should contain a transaction complete action and a runJavaScript action console.log('Control version of the rule')
2. create an AB test using the rule from step 1 with
  a. The variant rule should have a runJavaScript action of: console.log('Variant version of the rule')
  b. The goal should be transactionComplete for rule "my AB test rule"
3. run the A/B test
4. go to a URL where the A/B test is running
5. confirm that event=transactionComplete is logged
6. check that the abGoal is logged for both control and variant

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, goals restricted to the rule being A/B tested are only logged for the control rule.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms