Update on Debug Mode in Tag v3

We recently made an update regarding warning, log and error messages in Tag v3, the latest version of our generic tag that has been released a few weeks ago.

The majority of the warning, log and error messages that were displayed by default in the console of your browser have been removed to bring back clarity and avoid confusion between AB Tasty logs and your own logs.

However, we know that logs can be useful to understand why a campaign isn’t working so we have created an option to manually activate all AB Tasty logs. They can be enabled by one of the following steps:

  1. Use the cookie abTastyDebug with value true (valid until you remove the cookie or close your browser)
    To do so, copy and paste the following code in the console of your browser: document.cookie="abTastyDebug=true;path=/;domain=mydomain.com;" (you must replace “mydomain.com” with the domain of the website you are working on, i.e: abtasty.com)

  2. Use the global variable window.abTastyDebug with value true
    To do so, copy and paste the following code in the console of your browser: window.abTastyDebug = true; (valid until you reload the page)

  3. Install Requestly and use this specific rule* (valid until you deactivate the rule in the Requestly Chrome Extension)

*To use the Requestly rule, please proceed as follow:

  • install the extension: https://www.requestly.in/

  • import the “AB Tasty Debug (Tag V3)” rule

  • toggle on the "AB Tasty Debug (Tag V3)" rule

  • more information here

Once installed, the Debug mode will show you all the necessary steps to execute the tag and where the error(s) occur(s) if any and what should be done to resolve it.

Screenshot 2020-02-18 at 14.33.00.png

Feel free to contact your CSM if you have further questions.

Google Chrome 80 update

We have an update for you regarding Google Chrome 80 Release and Cross-Domain Tracking.

What happened?

Google’s Chrome release, scheduled for February 2020, will change the default cross-domain (SameSite) behaviour of cookies. The change will enhance security and privacy, but will require websites to explicitly state label the third-party cookies that can be used on other sites.

“Samesite” attribute on a cookie controls its cross-domain behaviour. According to the Chrome Platform Status, “Samesite” is a reasonably robust definition against some classes of cross-site request forgery (CSRF) attacks, but developers currently need to opt-into its protections by specifying a Samesite attribute.”

Chrome 80 release sets cookies as “SameSite=Lax” by default if no “SameSite” attribute is specified. Up until the Chrome 80 release, the default is “SameSite=None”. After the release, developers can choose to opt in to the status quo of unrestricted use by explicitly setting “SameSite=None”; “Secure”.

What does this mean?

Cookies will no longer work for non-secure (HTTP) browser access, including any community, portal or site in your organization. Use HTTPS instead.

In addition, custom integrations that rely on cookies may no longer work within Google Chrome. This change affects, but is not limited to integrations using iframes and cross-domain communication.

What do I need to do?

Nothing! AB Tasty only uses First-Party cookies. Therefore, the Chrome 80 release won’t have any impact, unless you have enabled the Cross-Domain Tracking in your account. The current Cross-Domain Tracking relies on Third-Party cookies.

We’ve created a fix that has been integrated into the latest version of AB Tasty generic script (Tag V3). If not already done, your account will be switched to that latest version in the coming days/weeks. Once the Tag V3 has been enabled on your account, the Cross-Domain Tracking will work the same, but only within one session. Once the session ends, we cannot guarantee that the visitors will be recognized beyond the initial domain.

External Resources

Chrome Platform Status: Cookies default to SameSite=Lax

Chrome Platform Status: Reject insecure SameSite=None cookies

Multi-page Test Integration update

With the new version of our Tag v3, the multi-page test integration with third-party analytics tools have experienced some changes. Now, we send each subtest ID instead of the global master ID. Therefore, tests analyzed during the migration period (November-December) may have been affected.

Feel free to reach out to CSM if you have any questions.

Campaign reporting revamp

The following improvements have been made to campaign reporting:

  • The Summary and Advanced tabs have been renamed Gain probability and Confidence interval.

  • Gain probability is now displayed for all campaign variations to enable better comparison with the original version.

  • The transaction goals have been reorganized and are now displayed as tabs (Transaction rate, Profit, Turnover, Cart).

  • Transaction goals may now be exported in CSV format.

To access the new reporting, go to the dashboard and click ALL_Rapport.png.

Learn more

New NPS© reports

NPS© reports have been redesigned and may now be viewed directly in the reports of the campaign the widget was configured in. NPS© reports show the following information:

  • The total score;

  • The number of detractors, promoters and passives for each variation;

  • The list of comments sent by visitors.

To access NPS© reports, go to the dashboard and click ALL_Rapport.png, then click the NPS tab.

Learn more

Session recording revamp

The following improvements have been made to the Session recording interface:

  • Shortcuts to videos for which the Highest transaction or the Highest level of frustration was identified.
  • Behavioral tags that are automatically applied to videos for which error click, rage click, rage quit and transaction type actions are identified.
  • A brand new design for the bar of applied filters based on browser, device, dates, campaigns and variations.
  • A new video player interface, which enables you to highlight the points at which error click, rage click, rage quit and transaction type actions occur.

New reporting - Adding of a category and filter reorder

The following improvements have been made to the filters of the new reporting:

  • The category Total number of items has been added to the filter Item.

  • The filters have been reordered as follows:

    • Device

    • Browser

    • Loyalty

    • Date

    • Action tracking

    • Custom tracking

    • Page

    • Landing page

    • Geolocalisation

    • Transaction

    • Item

    • Ecommerce variable

The filters are accessed via the new reports. To access them, go to the dashboard and click ALL_Rapport.png.

Learn more

NPS© (Net Promoter Score©) widget

The NPS© module has been improved. You can now customize your satisfaction survey via the NPS© (Net Promoter Score©) widget. Visitor feedback and comments remain available in the Insights section.

It is accessed via the widget library, in the Dynamic content category. To access this widget, please contact your AB Tasty sales manager.

EN_NPS.png

Learn more

New reporting - Improvements

The following improvements have been made to the new reporting:

  • The Ecommerce variable filter has been added. It enables you to filter visitor purchases according to ecommerce variables configured previously in your source code.

EN_ecovar_filter.png

  • Tooltips have been added to provide information on the campaign lifecycle.

EN_report_information.png

Also, from now on, you can no longer delete reporting data once your campaign has registered over 1,000 visitors.

To access the new reporting, go to the test or personalizations dashboard and click ALL_Rapport.png.

Learn more

Indicator reorganization in the target configuration step

On the campaign target configuration screen, the indicators have been reorganized as follows:

  • Action tracking
  • Page tracking
  • Custom tracking
  • Browsing indicators
  • Transaction

Learn more