Partial Content Tracking for Optimize

When an Optimize experiment spans multiple pages or app screens users may not see all part of the test. In order to track views and partial test completion, we have started collecting data on which parts of a test were viewed. Both the Infinity Tag and Mobile SDKs (iOS 3.2.4+ and Android 3.3.0+) will collect data in this manner.

For a single test on a page the collected data will look similar to the following:

  1. opt.project_type_id:
    AB
  2. opt.project_id:
    1373402
  3. opt.test_id:
    1373419
  4. opt.experiment_id:
    1373422
  5. opt.mode:
    2

For 2 tests on the page:

  1. opt.project_type_id:
    AB,AB
  2. opt.project_id:
    1373402,1234567
  3. opt.test_id:
    1373419,1234567
  4. opt.experiment_id:
    1373422,1234567
  5. opt.mode:
    2,1

Various delimiters are used to separate parameter values:

  • Multiple tests on a page: Comma
  • List of updates within a test: Semicolon
  • Update name within a factor: Colon

The “Test Content Rendered” (opt.tcr)¬†attribute indicates which update(s) from the Action Factor(s) have been applied.

Example:

opt.tcr: Heading:DIVbold; Heading:DIVitalic; Heading:H2copy; Hero:IMGsrc; Hero:IMGwidth; Hero:IMGheight; Footer:DIVhide, ctaF1:INPUTcopy; ctaF1:INPUTstyle; ctaF2:IMGsrc

Expanded out, this would mean:

  • Test 1:
    1. Factor named: Heading
      • Updates:
        • DIVbold
        • DIVitalic
        • H2copy
    2. Factor named: Hero
      • Updates:
        • IMGsrc
        • IMGwidth
        • IMGheight
    3. Factor named: Footer
      • Updates:
        • DIVhide
  • Test 2:
    1. Factor named: ctaF1
      • Updates:
        • INPUTcopy
        • INPUTstyle
    2. Factor named: ctaF2
      • Updates:
        • IMGsrc