Emarsys

Tick this to use the test mode when implementing and testing your environment before releasing.

This setting affects all events and tags in stage and production use if activated and published! Make sure to never use this setting on production.

It disables logging for all commands contained in the current window.ScarabQueue global object. In effect, this will prevent data-collection events from being recorded. It also prevents the Live Events tool from working. The Inspector tool will still work, you can use it for checking your JavaScript integration. Use testMode command on your staging or test site to avoid test traffic from interfering with your live website data-collection. For example to prevent purchases on the test site from showing up in Site Traffic statistics.

The purchase event tag provides functionality to collect transaction data in your web store with Emarsys. It must be called whenever a purchase event appears, passing the order identifier, the list of purchased items, the quantities and prices of each order event to Emarsys.

This tag will create the following data storages (cookies, local or session client side browser storages):

• no data is explicitly stored or read on a users device (client side) specifically with this tag with JENTIS
• this tag will interact with global JavaScript objects and activate tracking with a third party service that might access cookies or stream data to a third party

The following default _jts push track calls are required for the default JENTIS Emarsys implementation to work out of the box:

_jts.push track:

• pageview
• product
  • id
  • quantity
  • price
• order
  • id
• submit

Code example (do not execute or copy paste; for reference only).

function pageview() {
    _jts.push({
       "track" : "pageview"
    });
    _jts.push({
        "track"     :   "product",
        "type"      :   "order",
        "id"        :   "1111111",
        "brutto"    :   100.00,
        "quantity"  :   3
    });
    _jts.push({
        "track"     :   "order",
        "orderid"   :   "abcdef123456""
    });
    _jts.push({
        "track" : "submit"
    });
}

With the category you can track which product categories your visitors viewed in your web store. This tag must be called on the category page your visitors open and should pass the categoryPath parameter to Emarsys.

This tag will create the following data storages (cookies, local or session client side browser storages):

• no data is explicitly stored or read on a users device (client side) specifically with this tag with JENTIS
• this tag will interact with global JavaScript objects and activate tracking with a third party service that might access cookies or stream data to a third party

The following default _jts push track calls are required for the default JENTIS Emarsys implementation to work out of the box:

_jts.push track:

• pageview
• productlist
  • categorypath
• submit 

Code example (do not execute or copy paste; for reference only).

function pageview() {
    _jts.push({
       "track" : "pageview"
    });
    _jts.push({
       "track" : "productlist",
       "categorypath": ["category1","category2",...]
    });
    _jts.push({
        "track" : "submit"
    });
}

The view command makes it possible to track which products your visitors view in your web store. Accordingly this tag must be called on the product pages your visitors open and should pass the item identifier of the displayed products to Emarsys.

This tag will create the following data storages (cookies, local or session client side browser storages):

• no data is explicitly stored or read on a users device (client side) specifically with this tag with JENTIS
• this tag will interact with global JavaScript objects and activate tracking with a third party service that might access cookies or stream data to a third party

The following default _jts push track calls are required for the default JENTIS Emarsys implementation to work out of the box:

_jts.push track:

• pageview
• productlist
  • categorypath
• submit 

Code example (do not execute or copy paste; for reference only).

function pageview() {
    _jts.push({
       "track" : "pageview"
    });
    _jts.push({
       "track" : "productlist",
       "categorypath": ["category1","category2",...]
    });
    _jts.push({
        "track" : "submit"
    });
}

Tracks an add-to-cart event. It is mandatory to trigger this tag in order to send the correct current cart data on every page view and other events. Make sure to implement all cart-events (addition and removal of products) to have consistent data, as it is persisted as the current cart and must represent it correctly for correct operation of Emarsys.

This tag will create the following data storages (cookies, local or session client side browser storages):

• local storage (Client Devices Browser): jentis.connector.emarsys.cart - this holds information on the cart of the current checkout process
• this tag will interact with global JavaScript objects and activate tracking with a third party service that might access cookies or stream data to a third party

The following default _jts push track calls are required for the default JENTIS Emarsys implementation to work out of the box:

_jts.push track:

• pageview
• product
  • id
  • price
  • quantity
• addtocart
• submit 

Code example (do not execute or copy paste; for reference only).

function pageview() {
    _jts.push({
       "track" : "pageview"
    });
    _jts.push({
        "track"     :   "product",
        "type"      :   "addtocart",
        "id"        :   "1111111",
        "brutto"    :   100.00,
        "quantity"  :   3
    });
    _jts.push({
        "track"     :   "addtocart"
    });
    _jts.push({
        "track" : "submit"
    });
}

Tracks a remove-from-cart event. It is mandatory to trigger this tag in order to send the correct current cart data on every page view and other events. Make sure to implement all cart-events (addition and removal of products) to have consistent data, as it is persisted as the current cart and must represent it correctly for correct operation of Emarsys.

This tag will create the following data storages (cookies, local or session client side browser storages):

• local storage (Client Devices Browser): jentis.connector.emarsys.cart - this holds information on the cart of the current checkout process
• this tag will interact with global JavaScript objects and activate tracking with a third party service that might access cookies or stream data to a third party

The following default _jts push track calls are required for the default JENTIS Emarsys implementation to work out of the box:

_jts.push track:

• pageview
• product
  • id
  • price
  • quantity
• removefromcart
• submit 

Code example (do not execute or copy paste; for reference only).

function pageview() {
    _jts.push({
       "track" : "pageview"
    });
    _jts.push({
        "track"     :   "product",
        "type"      :   "removefromcart",
        "id"        :   "1111111",
        "brutto"    :   100.00,
        "quantity"  :   3
    });
    _jts.push({
        "track"     :   "removefromcart"
    });
    _jts.push({
        "track" : "submit"
    });
}

Tracks a checkout event with Emarsys. With this event the current cart information is set to all products pushed with this event - any product added or removed previously will be overridden with the latest information as of this event.

This tag will create the following data storages (cookies, local or session client side browser storages):

• local storage (Client Devices Browser): jentis.connector.emarsys.cart - this holds information on the cart of the current checkout process
• this tag will interact with global JavaScript objects and activate tracking with a third party service that might access cookies or stream data to a third party

The following default _jts push track calls are required for the default JENTIS Emarsys implementation to work out of the box:

_jts.push track:

• pageview
• product
  • id
  • price
  • quantity
• checkout
• submit 

Code example (do not execute or copy paste; for reference only).

function pageview() {
    _jts.push({
       "track" : "pageview"
    });
    _jts.push({
        "track"     :   "product",
        "type"      :   "checkout",
        "id"        :   "1111111",
        "brutto"    :   100.00,
        "quantity"  :   3
    });
    _jts.push({
        "track"     :   "checkout"
    });
    _jts.push({
        "track" : "submit"
    });
}

This tag passes all product data to Emarsys as it is currently represented in the current cart (based on previous events, such as checkout, add to cart or remove from cart). Emarsys suggests that this tag is executed on every page of your web store, passing the item identifier, the quantity and price of each product found in the cart. This is handled by JENTIS natively and requires the according events (checkout, add to cart and remove from cart) to be implemented correctly.

This tag will create the following data storages (cookies, local or session client side browser storages):

• local storage (Client Devices Browser): jentis.connector.emarsys.cart - this holds information on the cart of the current checkout process
• this tag will interact with global JavaScript objects and activate tracking with a third party service that might access cookies or stream data to a third party

The following default _jts push track calls are required for the default JENTIS Emarsys implementation to work out of the box:

_jts.push track:

• pageview
• submit

Code example (do not execute or copy paste; for reference only).

function pageview() {
    _jts.push({
       "track" : "pageview"
    });
    _jts.push({
        "track" : "submit"
    });
}