LG-8754 Persist AB testing values in session WIP

[jess-fortier]

LG-8754

🛠 Summary of changes

• Change event on IPP CTA load

  • from Frontend: IdV: IPP CTA Variant A / Frontend: IdV: IPP CTA Variant B / Frontend: IdV: IPP CTA Variant C
  • to IdV: IPP CTA Variant Displayed

• Store variant data in session and surface it in future logged events as:

{
     "name": <event name>
          "properties":{
               ...
               "test_data":{
                    "ipp_cta_variant":<variant bucket name>
               }
               ...
          }
     ...
}

• Update existing analytics tests to accommodate the new session entry @session[test_data]

📜 Testing Plan

LG-8754 Test Plan

[zachmargolis]

I am very skeptical of putting this side effect here. Again, the only purpose of this file is to provide some static definitons we can generate documentation from, I think it would be clearer to move this logic up to the call sites

Take a look at #7685 as an example of removing event-specific side effects.

[jess-fortier]

I was struggling with the best way to persist a value in session from the doc auth React flow. Could I put some time on your calendar to discuss?

[zachmargolis]

Yup! Go for it

[aduth]

Could we assign the A/B test bucket to the session before the page is loaded. And then if we need to add that to events for in-person proofing, we could use the existing Idv::AnalyticsEventsEnhancer class to add the variant in dynamically to every event for the in-person flow, since it was designed to add common details to all IPP events.

[zachmargolis]

Suggested change

	**extra,
	variant: variant,
	**extra,