Create a custom data conversion using the Advanced Editor

A custom data conversion records not only an event that has happened, but also values attached to it. For example – Purchase may be an event, with Revenue and Units as custom data points.
In this document, we’ll briefly explain how to set these up in the Advanced Editor.

1. Automatic Tracking

In some situations, you will already have data fields tracking. You will see these presented as follows:

  1. Go to the conversions section of the workflow
  2. You will see some greyed-out options, which are also marked with AUTO.
  3. Their types are shown to the right.

If the fields you need are already on this list, there is no need to make additional ones.

2. Create your own

In the white fields shown in the above screenshot, you can produce your own fields. Please ensure that your field name is only letters or underscores – no numbers and no spaces.

The field types are as follows:

  • Text – Free text. Field limit of upto 250 characters.
  • Decimal – A decimal type.
  • Integer – A whole number.

Please ensure that if you send numeric types, they’re sent as numbers and not strings. I.e. field_name: 20, not field_name: "20"

Why use numeric types?

Doing this will unlock our non-binomial reporting, allowing you to report on things like Average per tested visitor, Mean, Media, Uplifts, Chance to beat Control and Signficance.

Sending custom data with Javascript

// Without the Optimize Build Framework:{
    testAlias: "ta_something",
    conversionPoint: "response_question1",
    data: {
        field_name: "field_value",
        next_field_name: "next_field_value"
// With the Optimize Build Framework:
Test.conversion("response_thumbsup", {
    data: {
        field_name: "field_value",
        next_field_name: "next_field_value"