Integrate with Third-Party Analytics

monetate doesn't report data for product recommendations for email experiences nor full page test experiences to third party platforms depending on your site structure, you may need to use javascript polling to ensure that monetate correctly captures your site's data in addition to experience analytics available in the monetate platform, you can integrate your monetate account with third party platforms to report experience information examples of these platforms include google analytics, ibm digital analytics (formerly coremetrics), and adobe analytics, including adobe marketing cloud how integrations work exporting data to a third party platform may add server calls to your system for traditional monetate tag–based experiences, monetate writes to a client's webpage the integrate with third party analytics javascript variable it contains the experience id, name, and split information for every experience running on that page for the site visitor viewing it by default, experience data is pushed when a site visitor sees an experience and after a 5 minute interval on the next track, be that a new page load or a page retracks if you want a custom interval for reporting label pushes, such as having labels pushed on every page load (every track) or every 30 minutes, then submit a support ticket using the {{monetatesupportcontact}} and provide the name of the report for which you want to customize the interval monetate provides ready made options if you need to integrate your account with contentsquare or google analytics you can use your own javascript or use integration tools provided by other analytics platform vendors if you’ve developed your own analytics tracking tools, you can use them as well see enabling a custom report at the experience level in configure a custom third party analytics report in the monetate knowledge base for more information about sending experience data to your third party analytics platform(s) the campaigns variable the campaigns javascript variable is an array of objects that contains information about the experiences running on a page of your site it sends the experience data to your third party analytics platform(s) the number of indices in campaigns is equal to the number of experiences the site visitor sees on the page monetate writes the campaigns variable on a page of your site, but the variable doesn't provide other functionality by itself submit a support ticket using the {{monetatesupportcontact}} if you have questions each object in the campaigns variable contains the following information id — the unique experience id, which doesn't change (for example, 217022 ) key — the experience name shortened and appended with the experience id (for example, winter sale 217022 ); changes if you change the experience name 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 the following code snippet places the array in a variable available on the front end campaigns variable code example window\ monetate = window\ monetate || {}; window\ monetate campaigns = campaigns; the following screenshot shows how to access the campaigns variable in your console session count discrepancies and data validation checks session counts between monetate and your third party analytics platform will always have discrepancies due to various factors instead of focusing on session matching, monetate strongly encourages you to conduct a purchase audit to match purchases between platforms because consistent collection and alignment of purchase data signifies a healthy monetate implementation session counts between monetate and a third party analytics platform may vary for various reasons differences in session definitions and handling between monetate and the third party analytics platform variances in bot traffic–filtering mechanisms between monetate and the third party analytics platform varied session timeout and activity limits set by different analytics systems inclusion of nonessential analytics cookies that may be blocked by visitors by conducting a purchase audit to align purchase data between monetate and your third party analytics platform, you can ensure data accuracy and obtain more meaningful insights for analysis requesting a purchase audit to initiate a purchase audit, contact your customer success manager, who can guide you through the process and provide you with the necessary details regarding the data you need to provide for the audit you can also find more information in the test an implementation section of test an implementation testing the integration after you create the custom third party analytics reporting integration following the steps in configure a custom third party analytics report , you can ensure it works by adding the javascript console log() method and a message to the code in the editor on the report configuration page in the monetate platform the following example is the code samples for third party analytics integrations with the console log() method added ga4 with google tag with console log() example if (typeof(window\ gtag) === "function") { for (var i = 0; i < campaigns length; i++) { var campaign = campaigns\[i]; window\ gtag('event', campaign key, { 'event category' 'monetate', 'event label' campaign split, 'non interaction' true }); } console log("google analytics 4"); } after you add the console log() method and message to the report code, click the preview icon callout of the preview icon for a for a google analytics 4 report configuration while viewing the new browser tab or window in which your site loaded in preview mode, open your browser's developer tools, switch to its console, and ensure the message that you used with the console log() method in the report code is present callout of the 'google analytics 4' message resulting from the 'console log()' method used in the ga4 report's code when you've confirmed that the integration works, you can enable it for all new web experiences as well as add it to any active web experiences refer to enabling a custom report at the experience level in the monetate knowledge base for the steps