This repository was archived by the owner on May 5, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
MV Testing 3f4bb4
Benjamin Diolez edited this page May 5, 2026
·
1 revision
Before starting implementation of the MV Testing plugin, please make sure you have initialised the AT Internet JavaScript Tracker and selected the plugin from within the Tag Composer interface.
The MV Testing JavaScript plugin enables the measurement of different design and content combinations for a single web page.
The Tracker has an mvTesting.set() method allowing you to define the test name, wave ID and creative name:
- test: ID and name of the test, in the format ID[name_test].
- waveId: ID of the wave (group of creatives).
- creation: ID and name of creatives (combination of versions for each variable) in the format ID[name_creation].
The following method is deprecated. It will not feed any analysis on the Analytics Suite 2 and Piano Analytics solutions.
The Tracker has an mvTesting.add() method allowing you to define the variable and version name:
- variable: ID and name of the variable in question, in the format ID[name_variable].
- version: ID and name of the version in question, in the format ID[name_version].
For test and creation:
- if you only enter the ID, a name will be automatically generated,
- if you only enter the name, an ID will be automatically generated,
- if you enter an ID and a name, both will be saved.
var tag = new ATInternet.Tracker.Tag();
tag.page.set({
name: 'pageName',
chapter1: 'chap1',
chapter2: 'chap2',
chapter3: 'chap3',
level2: '123'
});
tag.mvTesting.set({
test: '1[My_first_Test]',
waveId: 1,
creation: '2[Version2_page_subscription]'
});
tag.mvTesting.add({
variable: '1[Header]',
version: '2[Grey]'
});
tag.mvTesting.add({
variable: '2[Sidebar]',
version: '4[Black]'
});
tag.dispatch();Last update: 20/06/2022
-
Data API
- Data flow
- Advice optimizations data flow
- Error codes data flow
- Faq data flow
- General information data flow
- Technical information data flow
- Reporting API v3
- Getting started
- Methods
- Parameters
- Technical information
- REST API
- Campaigns
- Custom variables
- Getting started rest
- Methods rest
- Response structure parameters rest
- Fixed periods
- Parameters compatibility
- Relative periods
- Structure of the response
- “code” parameter
- “columns” parameter
- “evo” parameter
- “filter” parameter
- “include” parameter
- “lng” parameter
- “max-results” parameter
- “page-num” parameter
- “period” parameter
- “period” parameter: “H” v. “He” & “MN” v. “MNe”
- “retention” parameter
- “segmentdesc” parameter
- “segment” parameter
- “sep” parameter
- “sort” parameter
- “space” parameter
- Technical specifications rest
- Data flow
-
Data collection
- Android
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Users
- Apple
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Users
- General
- Cddc renew staging process
- Changelog
- Craft your hit
- Encoded parameters
- Server side cookie management
- Supported taggings
- Tagging deletion
- Utilisation of dispatch sdks
- JavaScript
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Partners javascript
- Users
- Piano Analytics
- Event tagging piano analytics
- Getting started piano analytics
- Piano analytics tagging
- Feeding piano analytics with as2 tagging
- Tagging custom properties sdk
- Android