Microsoft Dynamics 365 Commerce

AB Tasty & Microsoft Dynamics 365 Commerce


Integrating Microsoft Dynamics 365 Commerce with AB Tasty brings the power of AB Tasty's Experience Optimization Platform to Microsoft Dynamics 365 Commerce. Through the integration, you will be able you run A/B, Multipage or Multivariate tests. You will also benefit from AB Tasty's automation, including dynamic allocation, and the ability to personalize right on your store to increase conversions and transactions.




This article assumes you already have your store on Microsoft Dynamics 365 Commerce and want to create and run Experimentation or Personalization for your online store using AB Tasty.


Installing the AB Tasty Javascript Tag


Beware: There are two kinds of AB Tasty tags: the generic tag will allow you to apply the JavaScript layer for your page modifications, and the transaction tag will send transaction data to your reports. Only the Generic tag can be implemented with Microsoft Dynamics 365 Commerce.


  1. Get the ABT Tasty Generic tag code snippet. For this,
    • Log in to your AB Tasty Account
    • Access Settings > Tags implementation > Generic Tag. Here you will find AB Tasty's Javascript code snippet to copy.
    • Copy the code snippet
  2. Log in to your Microsoft Dynamics Commerce account.
  3. Follow the steps for creating an External script module from this Microsoft Help article.


Good to know 💡

This external script module enables you to include JavaScript from external sources by providing an URL that points to a valid JavaScript file. After the module is added using the Commerce site builder, the script URL can be added to the Script source property.


The external script module includes the “Executed Script Asynchronously” and the “Defer Script Execution” configuration properties:

  • The “Executed Script Asynchronously” property specifies whether the script should be run in an asynchronous mode.
  • The “Defer Script Execution” property specifies whether the script should be run when the page has finished parsing configuration properties.

The following illustration shows an external script injector module that is configured on a page template. The Script source property box is where you add the URL that points to the script source code that will be injected into the HTML for the rendered page.



How to QA the Tag:


Check From the Network Tab

The easiest way to QA your implementation is to have a look at the network tab of your browser. By filtering on the domain, you should see our tag being downloaded.


By opening its preview tab, you will see its last update time and its version.


Check for the JS Object

Our tag creates an ABTasty JS object with useful variables and methods when correctly executed.




Check for the Browser Storage

If no storage restriction is set (consent management), the tag will automatically create cookies and entries in the local storage and session storage.

Was this article helpful?