Third-Party Analytics Reports

Third-party analytics reports allow you to send experience data to any platform that can collect data from a page. Monetate writes a JavaScript variable, campaigns, that contains the experience ID, name, and split information for any experience running on that page for that particular user.

Refer to your analytics platform's labeling guidelines for information about any restrictions or guidelines it may have.

You can send this data to analytics and data platforms such as SiteCatalyst, Mixpanel, Coremetrics, or any internal tools that your company has developed to track analytics.

Monetate pushes experience data to third-party analytics platforms when a site visitor sees an experience, which occurs on the next page load, after 5 minutes, or with a retrack after 5 minutes. The 5-minute interval is unique to when the visitor first qualifies for the experience.

Follow these steps to create a new custom third-party analytics report.

Configuring the code for a custom report requires some knowledge of JavaScript. If you are unfamiliar with JavaScript, check with your IT department for support, or refer to the requirements provided by your third-party analytics platform.

  1. Click the settings icon in the top navigation bar and then select Integration.
  2. On the Third-Party Analytics tab, take one of the following actions:
    • If the account doesn't have any third-party analytics custom reports, then click SELECT for Custom Reporting.

      Callout of the SELECT button for the Custom Reporting option

    • If the account already has a third-party analytics report, then click ADD REPORT and then, if necessary, select Custom.

      Callout of the 'Custom' option in the ADD REPORT button menu

  3. Type the custom report's name into Title, and then input the platform-specific JavaScript into the console.

    Callout of the Title field and the JavaScript code editor

  4. Optionally, set Enable by default for all new experiences to YES if you want Monetate to push experience data for all new experiences to the third-party platform associated with the new report.

    Callout of the 'Enable by default for all new experiences' toggle

  5. Click CREATE.

    Callout of the CREATE button

The campaigns Variable

The JavaScript variable campaigns is an array of objects that contains information about the experiences running on that page. This variable allows you to send Monetate data to your analytics or data platform. The number of indices in campaigns is equal to the number of experiences.

The campaigns variable is only available within the Custom Report JavaScript console. Submit a support ticket using the Kibo Technical Support portal ( if you have any questions.

Each index in the campaigns variable contains the following information:

  • id — The unique ID of the experience (for example, 217022)
  • key — A shortened version of the experience name appended with the experience ID (for example, A/B-Test_217022)
  • split — The split name (for example, Experiment or A-control)

Here is an example of the data present in the campaigns variable for a visitor who was exposed to three different experiences on the page.

Code sample of data from multiple experiences captured in campaigns variables

Testing and Previewing the Report

The easiest way to test and preview the new custom report is to add a console log to see the experience object and use the preview option. You can also add a console log to a test experience targeted to your IP and then verify the accuracy of the integration.

Once you add a custom report to an experience and activate it, you can't edit it or delete it from the platform. Therefore, ensure that you verify the accuracy of the report before adding it to all experiences.

Custom Report Example

This screenshot shows an example of a typical method for sending experience information to Mixpanel.

View of a custom report configuration for Mixpanel

The campaigns variable is an array of experiences active on the page. The following code snippet places that array in a variable available on the front end:

window.monetate = window.monetate || {};
window.monetate.campaigns = campaigns;

The following screenshot shows how to access the campaigns variable in your console.

View of a JavaScript console that shows the campaigns variable

Enabling Third-Party Analytics for Standard Experiences

You can control whether Monetate pushes data to your third-party platform for standard experiences. This option can be useful if you don't want to report particular experiences to your third-party platform.

To enable or disable third-party reporting for individual experiences, click the additional options menu (...) on the Experience Editor page, and then click Third-Party Analytics.

Callout of the 'Third-Party Analytics' option in the menu of additional options on the Experience Editor page

The text in Report Label auto-populates with the name of the experience and its ID. Monetate reports this string to your third-party platform. If you want to see a specific string in your third-party platform for this specific experience, you can enter it into Report Label.

Monetate automatically creates labels for holdout variants based on your specified variant labels. For each variant included in the holdout, Monetate appends the label with - Holdout.

The 'Third-Party Analytics' modal

Click SAVE to close the modal.