This guide is recommended for Experimentation Hub clients looking to implement our Smartserve script (required to drive basic data collection) and those essential QProtocol events required to drive experiences, segmentation, and analytics.

Don't forget to checkout our Events page for the full QP event specification.

Perform these tasks in the following order:

1. Add the UV API script
2. Add the Smartserve script
3. Emit events

Add on every page:

<script>
!function(){function n(){function n(n){p.level=n}function e(n,e){p.info(n,"event emitted"),e=c(e||{}),e.meta=e.meta||{},e.meta.type=n,u.push(e),r(),v.listeners=f(v.listeners,function(n){return!n.disposed})}function o(n,e,o){function r(){return p.info("Replaying events"),t(function(){s(v.events,function(t){c.disposed||l(n,t.meta.type)&&e.call(o,t)})}),f}function i(){return p.info("Disposing event handler"),c.disposed=!0,f}p.info("Attaching event handler for",n);var c={type:n,callback:e,disposed:!1,context:o||window};v.listeners.push(c);var f={replay:r,dispose:i};return f}function t(n){p.info("Calling event handlers"),a++;try{n()}catch(n){p.error("UV API Error",n.stack)}a--,r()}function r(){if(0===u.length&&p.info("No more events to process"),u.length>0&&a>0&&p.info("Event will be processed later"),u.length>0&&0===a){p.info("Processing event");var n=u.shift();v.events.push(n),t(function(){s(v.listeners,function(e){if(!e.disposed&&l(e.type,n.meta.type))try{e.callback.call(e.context,n)}catch(n){p.error("Error emitting UV event",n.stack)}})})}}function i(n,e,o){var t=v.on(n,function(){e.apply(o||window,arguments),t.dispose()});return t}function s(n,e){for(var o=n.length,t=0;t<o;t++)e(n[t],t)}function c(n){var e={};for(var o in n)n.hasOwnProperty(o)&&(e[o]=n[o]);return e}function l(n,e){return"string"==typeof n?n===e:n.test(e)}function f(n,e){for(var o=n.length,t=[],r=0;r<o;r++)e(n[r])&&t.push(n[r]);return t}var u=[],a=0,p={info:function(){p.level>n.INFO||console&&console.info&&console.info.apply(console,arguments)},error:function(){p.level>n.ERROR||console&&console.error&&console.error.apply(console,arguments)}};n.ALL=0,n.INFO=1,n.ERROR=2,n.OFF=3,n(n.ERROR);var v={on:o,emit:e,once:i,events:[],listeners:[],logLevel:n};return v}"object"==typeof module&&module.exports?module.exports=n:window&&void 0===window.uv&&(window.uv=n())}();
</script>

Add on every page:

<script src='https://static.goqubit.com/smartserve-{your-property-id}.js' ></script>

Events are emitted using the UV API and must conform to a certain schema. Events are emitted using JavaScript, usually on page load or when a new view is rendered on a single page app. An example is shown below:

uv.emit('theEventType', {
  aStringField: 'theValueWhichMustBeTheCorrectType',
  aNumberField: 3,
  aBooleanField: false
})

In the following table, we show an indicative breakdown of a website by page type, alongside the events that could be emitted on each page. This represents a typical set up and there may be exceptions:

In addition to the above events, in the following table we show the events that correspond to common visitor activities, such as registration, login, and search:

Qubit recommends the following events should be emitted:

• trView
• trUser
• trUserLogin
• trUserSignup
• trFormSubmission
• trSearch
• trPackageItem
• trPackageItemCheckout
• trPackageItemTransaction
• trPackageSummary
• trPackageCheckoutSummary
• trPackageTransactionSummary

These events represent the starting point for setting up Qubit on your site. Additional events are required to drive Qubit's programmatic experiences.

For each of the above events, we identify those fields that are required to integrate with Qubit technology. We also detail other fields that we recommend are emitted for data completeness. For both required and recommended fields, we identify those that apply to all sites and those that only apply to journey, accommodation, ancillary, and experience.

Other Qubit products have different event field requirements, which will be discussed during onboarding.

The trView event reports a page view and is a special event because it is required by smartserve.js for data collection and processing. It is therefore essential that every page emits an trView event and that it is emitted before any other event.

DANGER: Any events emitted before the first trView event are considered invalid. Web and mobile applications emit view events whenever a view is rendered.

Emit trView on every page.

• type

• subtypes
• language
• country
• currency

uv.emit('trView', {
  type: 'home',
  subtypes: ['Holidays', 'All Inclusive', 'Luxury'],
  language: 'en-us',
  country: 'US',
  currency: 'USD'
})

• Use only lower-case characters
• Custom names can be used for unique page types that are not covered by our recommended page types such as home, category, product
• It is acceptable to use null in the absence of a page type

• Where possible, the array should be aligned with the same structure used for the page breadcrumb, if available

• These fields are only required if your site has multiple languages, currencies, or shipping countries. If not, they can be safely omitted

The trUser event is emitted once per view and reports visitor metadata. The event should be emitted on every page as long as there is data available for the user.

For many websites, the event will be present and well populated when the visitor logs on. Websites with a newsletter subscription form that the visitor has previously submitted, might be able to populate the name and email address for the visitor using the data collected on form submission.

In short, yes. Both user Id and email can be hashed. However, please be aware that to ingest data for use in the Qubit platform, the user Id and email in the provided dataset must be hashed in the same way.

Alternatively, you may choose to omit user.email. The omission of a required field does not prevent the event itself from being sent to Qubit and being processed by our data pipeline-you will see a validation error in the Validation Dashboard for the event though.

For further information about our role as a data processor and our obligations and commitments under GDPR, please refer to Personal Data and in particular How is customer data treated? For legal clarifications, please contact legal@qubit.com.

Emit trUser events on every page with details of the visitor.

All sites

• user.id
• user.email

All sites

• user.isGuest
• loyalty.tier
• loyalty.tierPoints
• loyalty.membershipType
• loyalty.membershipPoints

uv.emit('trUser', {
  user: {
    id: 'js123xyz',
    email: 'John.Smith@gmail.com',
    isGuest: true,
    loyalty: {
      tier: 'silver',
      tierPoints: 10,
      membershipType: 'Clearsky Rewards',
      membershipPoints: 56
    }
  }
})

• It is acceptable to emit a hashed user Id

• It is acceptable to emit a hashed email

Emitted when a visitor logs in.

INFO: Emit trUserLogin on successful login with details of the logged in user.

All sites

• user.id

uv.emit('trUserLogin',{
  user: {
    id: 'joeBloggs',
  }
})

Emitted when a visitor signs up for a newsletter or event.

INFO: Emit trUserSignup on signup with details of the visitor submitting the signup request.

All sites

• user.id

All sites

• type
• name

uv.emit('trUserSignup',{
  user: {
    id: "2861102bace6e6620948564f0ce0a7cd",
    },
  type: 'newsletter',
  name: 'weekly signup'
})

Examples of a form submission include getting a quote, subscribing to a newsletter, or contacting customer support.

For travel sites that are non-transactional, for example, those sites that provide quotations, this event is very important as it is used to count conversions.

INFO: Emit trFormSubmission on form submission with a unique Id to identity the form submission and an accompanying form name.

All sites

• submissionId
• name

uv.emit('trFormSubmission',{
  submissionId: 'ContactUs-856',
  name: 'ContactUsEnquiry'
})

Emitted when a visitor performs a search on a site. This is a key event because it is usually the first step taken by a visitor when booking a trip and allows you to gather rich information early in the visitor journey, which is very valuable for segmentation.

INFO: Emit trSearch when a visitor performs a search to identify the search parameters.

All sites

• searchType
• numberOfAdults
• numberOfChildren
• numberOfInfants
• numberOfStudents
• numberOfTeenagers
• totalNumber
• startTs
• endTs
• exactDuration
• minDuration
• maxDuration
• exactPrice
• minPrice
• maxPrice
• origin.country
• origin.countryCode
• origin.region
• origin.locality
• origin.name
• origin.code
• destination.country
• destination.countryCode
• destination.region
• destination.locality
• destination.name
• destination.code
• leadTime
• boardBasis
• roomFacilities
• roomTypes
• numberOfRooms
• exactRating
• minRating
• maxRating
• outboundFares
• inboundFares
• flexibleDates
• results.pagination
• results.resultCount
• results.layout
• results.sortBy
• results.sortDirection

uv.emit('trSearch',{
  searchType: 'One-way Flight',
  numberOfAdults: 2,
  numberOfChildren: 5,
  numberOfInfants: 2,
  numberOfStudents: 2,
  numberOfTeenagers: 2,
  totalNumber: 9,
  startTs: 1454585576191,
  endTs: 1455926400000,
  exactDuration: 16,
  minDuration: 1,
  maxDuration: 6,
  exactPrice: {
    value: 9.99,
    currency: 'USD'
  },
  minPrice: {
    value: 9.99,
    currency: 'USD'
  },
  maxPrice: {
    value: 9.99,
    currency: 'USD'
  },
  origin: {
    country: 'Austria',
    countryCode: 'AT',
    region: 'Carinthia',
    locality: 'Villefranche sur saone',
    name: 'Ouagadougou Airport',
    code: 'LYS'
  },
  destination: {
    country: 'Austria',
    countryCode: 'AT',
    region: 'Carinthia',
    locality: 'Villefranche sur saone',
    name: 'Ouagadougou Airport',
    code: 'LYS'
  },
  leadTime: 42,
  boardBasis: [
    'All Inclusive',
    'Room Only'
  ],
  roomFacilities: [
    'A/C',
    'Wifi',
    'Jacuzzi'
  ],
  roomTypes: [
    'Royal Suite',
    'Single Room'
  ],
  numberOfRooms: 3,
  exactRating: 3.5,
  minRating: 3,
  maxRating: 4.5,
  outboundFares: [
    'Flexible First Class'
  ],
  inboundFares: [
    'Cheap Cheap Economy'
  ],
  flexibleDates: true,
  results: {
    pagination: 10,
    resultCount: 15,
    layout: 'grid',
    sortBy: 'price',
    sortDirection: 'ascending'
  }
})

This event is emitted on products pages, which are considered to be outside of the booking/checkout funnel.

Each trPackageItem event will contain a packageItemType, which describes either a journey, accommodation, ancillary, or experience.

For packaged holidays, the event will contain a packageItemType for each part of the package: flight, accommodation, ancillary(ies), experience.

A booking that only includes flights, would typically contain 1 packageItemType, with the value journey for the outbound flight and another packageItemType for the inbound flight, as shown in the following example:

uv.emit('trPackageItem',{
  package: {
    id: 'TRP201214'
  },
  eventType: 'detail',
  packageItem: {
    id: 'TRP201215',
    packageItemType: 'journey',
    journey: {
      journeyType: 'outbound'
   }
 }
})

Refer to the following table for a few example scenarios showing how to emit this event:

See Explanation of Package Types for more information.

Emit trPackageItem events on product detail pages for each package item shown.

All sites

• trPackageItem.packageItem.packageItemType

Ancillary

• trPackageItem.packageItem.ancillary.ancillaryType

All sites

• trPackageItem.package.id
• trPackageItem.eventType
• trPackageItem.packageItem.id

Journey

• trPackageItem.journey.id
• trPackageItem.packageItem.journey.journeyType
• trPackageItem.packageItem.journey.originName
• trPackageItem.packageItem.journey.originCode
• trPackageItem.packageItem.journey.destinationName
• trPackageItem.packageItem.journey.destinationCode
• trPackageItem.packageItem.journey.departureTs
• trPackageItem.packageItem.journey.arrivalTs
• trPackageItem.packageItem.journey.fare
• trPackageItem.packageItem.journey.originCountry
• trPackageItem.packageItem.journey.destinationCountry

Accommodation

• trPackageItem.accommodation.id
• trPackageItem.packageItem.accommodation.rating
• trPackageItem.packageItem.accommodation.normalizedRating
• trPackageItem.packageItem.accommodation.stars
• trPackageItem.packageItem.accommodation.boardBasis
• trPackageItem.packageItem.accommodation.travelLocation.country
• trPackageItem.packageItem.accommodation.travelLocation.locality
• trPackageItem.packageItem.accommodation.travelLocation.name
• trPackageItem.packageItem.accommodation.travelLocation.code

Ancillary

• trPackageItem.ancillary.id

Experience

• trPackageItem.packageItem.experience.id
• trPackageItem.packageItem.experience.name
• trPackageItem.packageItem.experience.location.country
• trPackageItem.packageItem.experience.location.locality
• trPackageItem.packageItem.experience.location.name
• trPackageItem.packageItem.experience.location.code
• trPackageItem.packageItem.experience.startTs
• trPackageItem.packageItem.experience.endTs

In the following example, we detail the schema structure of the trPackageItem event. This schema will be extended with the fields that correspond to the packageItemType implemented:

In the following example, we show an example of the trPackageItem event:

uv.emit('trPackageItem',{
  package: {
    id: 'TRP201214'
  },
  eventType: 'detail',
  packageItem: {
    id: 'TRP201218',
    packageItemType: 'journey'/'accommodation'/'ancillary'/'experience' // each packageType will have a set of fields for that specific type
  }
})

uv.emit('trPackageItem',{
  package: {
    id: 'TRP201214'
  },
  eventType: 'detail',
  packageItem: {
    id: 'TRP201215',
    packageItemType: 'journey',
    journey: {
      id: 'FL0989',
      journeyType: 'outbound',
      originName: 'John F Kennedy International',
      originCode: 'JFK',
      destinationName: 'Los Angeles International',
      destinationCode: 'LAX',
      departureTs: 1454585859331,
      arrivalTs: 1454595869331,
      price: {
        value: 299.99,
        currency: 'USD'
      },
      fare: 'Premium Cabin',
      originCountry: 'United States of America',
      destinationCountry: 'United States of America'
   }
 }
})

uv.emit('trPackageItem',{
  package: {
    id: 'TRP201214'
  },
  eventType: 'detail',
  packageItem: {
    id: 'TRP201215',
    packageItemType: 'accommodation',
    accommodation: {
      id: 'AC221144',
      rating:6,
      normalizedRating: 0.4,
      stars: 4,
      boardBasis: 'All inclusive',
      travelLocation: {
        country: 'United States',
        region: 'New York',
        locality: 'Manhatten',
        code: 'NYCMAN'
      }
    }
  }
})

In the following example schema, we present details of a few of the possible types of ancillaries.

Typically, for all ancillary types, you would emit an id and type.

uv.emit('trPackageItem',{
  package: {
    id: 'TRP201214'
  },
  eventType: 'detail',
  packageItem: {
    id: 'TRP201215',
    packageItemType: 'ancillary',
    ancillary: {
      ancillaryType: 'insurance',
      insurance: {
        id: 'INS1234',
        type: 'Travel Insurance',
        coverage: 2
      }
    }
  }
})

uv.emit('trPackageItem',{
  package: {
    id: 'TRP201214'
  },
  eventType: 'detail',
  packageItem: {
    id: 'TRP201215',
    packageItemType: 'ancillary',
    ancillary: {
      ancillaryType: 'luggage',
      luggage: {
        id: 'LUG123',
        type: 'Carry on',
        weight: 32
      }
    }
  }
})

uv.emit('trPackageItem',{
  package: {
    id: 'TRP201214'
  },
  eventType: 'detail',
  packageItem: {
    id: 'TRP201215',
    packageItemType: 'ancillary',
    ancillary: {
      ancillaryType: 'seats',
      seats: {
        id: 'SEAT123',
        type: 'Free upgrade',
        tier: 'Economy Plus',
        seatNumber: [
          '1A',
          '35D',
          '35E'
        ]
      }
    }
  }
})

uv.emit('trPackageItem',{
  package: {
    id: 'TRP201214'
  },
  eventType: 'detail',
  packageItem: {
    id: 'TRP201215',
    packageItemType: 'ancillary',
    ancillary: {
      ancillaryType: 'priority',
      priority: {
        id: 'PRIO123',
        type: 'Priority Boarding'
      }
    }
  }
})

uv.emit('trPackageItem',{
  package: {
    id: 'TRP201214'
  },
  eventType: 'detail',
  packageItem: {
    id: 'TRP201215',
    packageItemType: 'ancillary',
    ancillary: {
      ancillaryType: 'vehicleRental',
      vehicleRental: {
        id: 'VEHIO123',
        type: 'Standard Vehicle Rental',
        vendor: 'Excellent Rental Company'
      }
    }
  }
})

uv.emit('trPackageItem',{
  package: {
    id: 'TRP201220'
  },
  eventType: 'detail',
  packageItem: {
    id: 'TRP201221',
    packageItemType: 'experience',
    experience: {
      id: 'TRP201228',
      name: 'An amazing winter experience',
      location:{
        country: 'Finland',
        locality: 'Helsinki',
        name: 'Helsinki City',
        code: 'HelCC',
      },
      startTs: 1454585859331,
      endTs: 1454595869331
    }
  }
})

This event is similar to trPackageItem but is emitted on the checkout page and therefore inside the booking/checkout funnel.

Emit trPackageItemCheckout events on checkout pages for each package item the visitor has in their package.

All sites

• trPackageItemCheckout.packageItem.packageItemType

Ancillary

• trPackageItemCheckout.packageItem.ancillary.ancillaryType

All sites

• trPackageItemCheckout.eventType
• trPackageItemCheckout.package.id
• trPackageItemTransaction.packageItem.id

Journey

• trPackageItemCheckout.packageItem.journey.id
• trPackageItemCheckout.packageItem.journey.journeyType
• trPackageItemCheckout.packageItem.journey.originName
• trPackageItemCheckout.packageItem.journey.originCode
• trPackageItemCheckout.packageItem.journey.destinationName
• trPackageItemCheckout.packageItem.journey.destinationCode
• trPackageItemCheckout.packageItem.journey.departureTs
• trPackageItemCheckout.packageItem.journey.arrivalTs
• trPackageItemCheckout.packageItem.journey.fare
• trPackageItemCheckout.packageItem.journey.originCountry
• trPackageItemCheckout.packageItem.journey.destinationCountry

Accommodation

• trPackageItemCheckout.packageItem.accommodation.id
• trPackageItemCheckout.packageItem.accommodation.rating
• trPackageItemCheckout.packageItem.accommodation.normalizedRating
• trPackageItemCheckout.packageItem.accommodation.stars
• trPackageItemCheckout.packageItem.accommodation.boardBasis
• trPackageItemCheckout.packageItem.accommodation.travelLocation.country
• trPackageItemCheckout.packageItem.accommodation.travelLocation.locality
• trPackageItemCheckout.packageItem.accommodation.travelLocation.name
• trPackageItemCheckout.packageItem.accommodation.travelLocation.code

Experience

• trPackageItemCheckout.packageItem.packageItem.experience.id
• trPackageItemCheckout.packageItem.packageItem.experience.name
• trPackageItemCheckout.packageItem.packageItem.experience.location.country
• trPackageItemCheckout.packageItem.packageItem.experience.location.locality
• trPackageItemCheckout.packageItem.packageItem.experience.location.name
• trPackageItemCheckout.packageItem.packageItem.experience.location.code
• trPackageItemCheckout.packageItem.packageItem.experience.startTs
• trPackageItemCheckout.packageItem.packageItem.experience.endTs

uv.emit('trPackageItemCheckout',{
  package: {
    id: 'TRP201214'
  },
  eventType: 'detail',
  packageItem: {
    id: 'TRP201216',
    packageItemType: 'journey'/'accommodation'/'ancillary' // each packageItemType will have a set of fields for that specific type
  }
})

This event is similar to trPackageItem but is emitted on the confirmation page and contains additional fields for transaction data.

Transaction events are very important because they report revenue for your website.

This event collects granular information about individual items contained within a transaction. It enables segmentation based on preferences, including destinations, journey type, etc.

Emit trPackageItemCheckout events for each package item the visitor has purchased.

All sites

• trPackageItemTransaction.packageItem.packageItemType
• trPackageItemTransaction.transaction.id

Ancillary

• trPackageItemTransaction.packageItem.ancillary.ancillaryType

• trPackageItemTransaction.eventType
• trPackageItemTransaction.package.id
• trPackageItemTransaction.packageItem.id

Journey

• trPackageItemTransaction.packageItem.journey.id
• trPackageItemTransaction.packageItem.journey.journeyType
• trPackageItemTransaction.packageItem.journey.originName
• trPackageItemTransaction.packageItem.journey.originCode
• trPackageItemTransaction.packageItem.journey.destinationName
• trPackageItemTransaction.packageItem.journey.destinationCode
• trPackageItemTransaction.packageItem.journey.departureTs
• trPackageItemTransaction.packageItem.journey.arrivalTs
• trPackageItemTransaction.packageItem.journey.fare
• trPackageItemTransaction.packageItem.journey.originCountry

Accommodation

• trPackageItemTransaction.packageItem.accommodation.id
• trPackageItemTransaction.packageItem.accommodation.stars
• trPackageItemTransaction.packageItem.accommodation.travelLocation.country
• trPackageItemTransaction.packageItem.accommodation.travelLocation.locality
• trPackageItemTransaction.packageItem.accommodation.travelLocation.name
• trPackageItemTransaction.packageItem.accommodation.travelLocation.code

Experience

• trPackageItemTransaction.packageItem.experience.id
• trPackageItemTransaction.packageItem.experience.name
• trPackageItemTransaction.packageItem.experience.location.country
• trPackageItemTransaction.packageItem.experience.location.locality
• trPackageItemTransaction.packageItem.experience.location.name
• trPackageItemTransaction.packageItem.experience.location.code
• trPackageItemTransaction.packageItem.experience.startTs
• trPackageItemTransaction.packageItem.experience.endTs

uv.emit('trPackageItemTransaction',{
  package: {
    id: 'TRP201214'
  },
  eventType: 'detail',
  packageItem: {
    id: 'TRP201216',
    packageItemType: 'journey'/'accommodation'/'ancillary' // each packageItemType will have a set of fields for that specific type
  },
  transaction: {
    id: '83748372'
  }
})

This event contains all of the high-level information about the viewed/selected/purchased package and is the equivalent of a shopping basket summary.

The package Id should capture information for the whole package and not just the package items. Where there is a single package item, the information for the package and package item might be the same.

Emit trPackageSummary events for each package shown on a product detail page and once per pageview/context.

All sites

• trPackageSummary.package.id
• trPackageSummary.package.numberOfAdults
• trPackageSummary.package.numberOfChildren
• trPackageSummary.package.numberOfInfants
• trPackageSummary.package.totalNumber
• trPackageSummary.package.startTs
• trPackageSummary.package.endTs
• trPackageSummary.package.duration
• trPackageSummary.package.name
• trPackageSummary.package.type
• trPackageSummary.package.total

uv.emit('trPackageSummary',{
  package: {
    id: 'TRP201214',
    numberOfAdults: 2,
    numberOfChildren: 2,
    numberOfInfants: 1,
    totalNumber: 5,
    startTs: 1454585576191,
    endTs: 1455926400000,
    duration: 16,
    name: 'Winter wonderland',
    type: 'packaged holiday',
    total: {
      value: 2199.99,
      currency: 'USD'
    }
  }
})

This event is similar to trPackageSummary but is emitted on the checkout page and therefore inside the booking/checkout funnel.

Emit trPackageCheckoutSummary events on checkout pages for the package the visitor has in their basket.

All sites

• trPackageCheckoutSummary.package.id
• trPackageCheckoutSummary.package.numberOfAdults
• trPackageCheckoutSummary.package.numberOfChildren
• trPackageCheckoutSummary.package.numberOfInfants
• trPackageCheckoutSummary.package.totalNumber
• trPackageCheckoutSummary.package.startTs
• trPackageCheckoutSummary.package.endTs
• trPackageCheckoutSummary.package.duration
• trPackageCheckoutSummary.package.name
• trPackageCheckoutSummary.package.type
• trPackageCheckoutSummary.package.total
• trPackageCheckoutSummary.step

uv.emit('trPackageCheckoutSummary',{
  package: {
    id: 'TRP201214',
    numberOfAdults: 2,
    numberOfChildren: 2,
    numberOfInfants: 1,
    totalNumber: 5,
    startTs: 1454585576191,
    endTs: 1455926400000,
    duration: 16,
    name: 'Winter wonderland',
    type: 'Packaged holiday',
    total: {
      value: 2199.99,
      currency: 'USD'
    }
  },
  step: 'Confirmation'
})

This event is similar to trPackageSummary but is emitted on the confirmation page and includes additional fields for transaction data.

Most importantly, this event is used to count conversions and the associated revenue.

Emit trPackageTransactionSummary events on confirmation pages for the purchased package.

All sites

• trPackageTransactionSummary.package.total
• trPackageTransactionSummary.transaction.id

All sites

• trPackageTransactionSummary.package.id
• trPackageTransactionSummary.package.numberOfAdults
• trPackageTransactionSummary.package.numberOfChildren
• trPackageTransactionSummary.package.numberOfInfants
• trPackageTransactionSummary.package.totalNumber
• trPackageTransactionSummary.package.startTs
• trPackageTransactionSummary.package.endTs
• trPackageTransactionSummary.package.duration
• trPackageTransactionSummary.package.name
• trPackageTransactionSummary.package.type
• trPackageTransactionSummary.package.total

uv.emit('trPackageTransactionSummary',{
  package: {
    id: 'TRP201214',
    numberOfAdults: 2,
    numberOfChildren: 2,
    numberOfInfants: 1,
    totalNumber: 5,
    startTs: 1454585576191,
    endTs: 1455926400000,
    duration: 16,
    name: 'Winter wonderland',
    type: 'packaged holiday',
    total: {
      value: 2199.99,
      currency: 'USD'
    }
  },
  transaction: {
    id: '83748372'
  }
})