We categorize websites into three different categories.

• Standard systems like native WooCommerce or Adobe Commerce
• Standard systems as above, but with custom plugins installed in key areas
• Custom systems or systems that are unknown to us.

We will be able to natively track all of the pages your visitors visit in all three categories. Events such as adding and removing products from baskets will vary depending on your system.

The guide below is for Standard systems such as native WooCommerce or Adobe Commerce (Magento) 1.9 or 2.0 installations.

By the end of this guide, you will have set up Tracking and synchronization to handle the following
Contact Data

• Flat data such as name, birthday, permission
• Deep transactional data

Events

• Page visited
• Product visited
• Category visited
• Product/category added to cart
• Product/category removed from cart
• Product/category bought

Step 1. Create Product Feed and Sitemap

First off you will have to add your Product Feed and the Sitemap to your webshop. This is a requirement since the very heart of Tracking requires us to know your Products and pages in order to record who has visited what.

In-depth details about setting up Feeds and Sitemaps can be found here (link to setup of Feeds and Sitemaps).

Step 2. Setup Tracking

With the Product Feed and Sitemap added we can now set up the Tracking. In the Tracking, you are able to tell us which element in your Product Feed is the Category, Product ID, Sales Price, etc. This will be used in Segments and bridging the Tracking information with the Order data saved in One-to-Many empowering you to target Contacts who have or have not bought, have visited but not bought, etc. from a specific Product Category, Price range, etc.

We will guide you through the mapping and the system will automatically detect if you are using a known system such as SmartWeb, WooCommerce,  Adobe Commerce, etc. 

Click yes to automatic mapping and you will have the Product Events automatically mapped. If we do not detect your webshop you will have to map this manually.

In order to be empowered with the full potential of the benefits of Tracking it is required to map at least the following:

• Product Events
• Product Link
• Product Category
• Product ID
• Cart Page
• Checkout 
• Thank You Page.

It is advised to map more, but not required.

The visitors’ journey…

..and the congruence between Sitemap, Website, and Product Feed.

For us to combine the knowledge of which products have been browsed and added to the cart there are two important elements in the product feeds that bind the Sitemap and webshop together.

1. Product link. When a customer is visiting a site, we are checking the mapped “Product Link (URL)” and find the product he visited. From that we can see the product id and thereby the category, price etc for the product he visited. It is important that the mapped element for “Product Link (URL)” contains the link in a format shown below

2. Product Unique Identifier (id). When a product is added to the cart it is not visible in the URL alone, and there are many ways for the customer to add an item to the cart without being on the product page itself (search results, main pages with a list of products and an add-to-cart option, etc.).

Most webshops are saying that a specific product id has been added to the basket.  For the standard systems we know what that looks like, so all you need to do is to map the “Product Unique Identifier (id) with what is the product id used on the webshop.

It is important that the product ids are the same on the webshop and in the Product Feed – since when the shop is telling us a customer has added Product id “421” to the cart, we will check for product “421” in the Product Feed. If the ids are not the same – there will be no matches found and we will not know which product he added and have nothing to insert in Campaigns or show in Segments.

Step 3 – Setup Connector

The integration part is a few-click procedure. You can also choose the use the API (link) to transfer Contacts and their purchase data to our platform.

To synchronize Contacts and order data between your webshop and MarketingPlatform you go to the Connector page and select your system.

You are then required to insert a few details such as API key depending on your system.

Once connected you can start choosing which data to synchronize.

You can read our general Connector guides (link).

It is advisable to map at least

Product id (required)

Shipping information 
Sales price
Permission fields

And any information you want to use for segmentation and mail-merge

Step 4 – Setup Intelligence

By doing the above setups you have fulfilled all requirements for using the Intelligence function inside of the platform such as AI and intelligent segmentation. You can go to the Intelligence point in the menu (link text to: https://client3.mailmailmail.net/admin/index.php?Page=Intelligence&Action=mapping) and see if you miss any required mapping.

If you have followed the above steps then it is most likely that all you have to do is to edit the One-to-Many field and add the required mapping.

Here you can map which field in your OrderData is the item id, order id, item price, etc. This will be used to bind your order data with your product feed allowing you to create segments such as “Contacts who have bought from x category” etc as well as using AI for predicting product recommendations which you can read more about here.

The post How to Set Up a Standard System appeared first on MarketingPlatform - Dansk Email Marketing Software.

We categorize websites into three different categories.

• Standard systems like native WooCommerce or Adobe Commerce (Magento)
• Standard systems as above, but with custom plugins installed in key areas
• Custom systems or systems that are unknown to us

We will be able to natively track all of the pages your visitors visit in all three categories. Events such as adding and removing products from baskets will vary depending on your system.

The guide below is for Standard systems such as Adobe Commerce (Magento) 1.9 or 2.0, Prestashop, and other installations where you at some point in the journey of product purchasing have installed a plugin. That could be in the checkout-flow, a third-party option of adding products to the basket, etc.

By the end of this guide, you will have set up Tracking and synchronization to handle the following

Contact Data

• Flat data such as name, birthday, permission
• Deep transactional data

Events

• Page visited
• Product visited
• Category visited
• Product/category added to cart*
• Product/category removed from cart* 
• Product/category bought*

*With or without the use of Google-tag-manager

Step 1. Create Product Feed and Sitemap

First off you will have to add your Product Feed and the Sitemap to your webshop. This is a requirement since the very heart of Tracking requires us to know your Products and pages in order to record who has visited what.

In-depth details about setting up Feeds and Sitemaps can be found here.

Step 2. Setup Tracking

With the Product Feed and Sitemap added we can now set up the Tracking. In the Tracking, you are able to tell us which element in your Product Feed is the Category, Product ID, Sales Price, etc. This will be used in Segments and bridging the Tracking information with the Order data saved in One-to-Many empowering you to target Contacts who have or have not bought, have visited but not bought, etc. from a specific Product Category, Price range, etc.

We will guide you through the mapping and the system will automatically detect if you are using a known system such as SmartWeb, WooCommerce,  Adobe Commerce, etc. 

Click yes to automatic mapping and you will have the Product Events automatically mapped. If we do not detect your webshop you will have to map this manually.

In order to be empowered with the full potential of the benefits of Tracking it is required to map at least the following:

• Product Events
• Product Link
• Product Category
• Product ID
• Cart Page
• Checkout 
• Thank You Page.

It is advised to map more, but not required.

The visitors’ journey and congruence between Sitemap, site, and product feed.

For us to combine the knowledge of which products have been browsed and added to the cart there are two important elements in the product feeds that bind the Sitemap and webshop together.

1. Product link. When a customer is visiting a site, we are checking the mapped “Product Link (URL)” and find the product he visited. From that we can see the product id and thereby the category, price, etc for the product he visited. It is important that the mapped element for “Product Link (URL)” contains the link in a format shown below

2. Product Unique Identifier (id). When a product is added to the cart it is not visible in the URL alone, and there are many ways for the customer to add an item to the cart without being on the product page itself (search results, main pages with a list of products and an add-to-cart option, etc.).

Most webshops are saying that a specific product id has been added to the basket.  For the standard systems we know what that looks like, so all you need to do is to map the “Product Unique Identifier (id) with what is the product id used on the webshop.

It is important that the product ids are the same on the webshop and in the Product Feed – since when the shop is telling us a customer has added Product id “421” to the cart, we will check for product “421” in the Product Feed. If the ids are not the same – there will be no matches found and we will not know which product he added and have nothing to insert in Campaigns or show in Segments.

Google tag-manager

In some cases, you might have installed a plugin or module to your webshop improving or altering the checkout flow or creating additional ways of adding products to the basket.

In this case, it is not sure we are able to detect these events, and it is, therefore, necessary to tell us when these events happen in case you want to make use of these events in places such as Segments and FlowBuilder. It is up to you how you prefer to do this.

These are the data we need for each event

We suggest using Google Tag Manager since most webshops are already using this service. You can simply create a custom event using Google Tag Manager to tell us when things happen depending on the Trigger you choose.

Creating a custom HTML in Google tag-manager

Creating a Custom HTML Tag as above requires two things to send us the data:

1. You need the ProductID as a variable in order to send it to us
2. You need to have your event setup as a Trigger to fire the above Tag

It is not necessary to set up this to track the parts not marked with * at the beginning of the article.

The post How to Set Up a Standard System with Custom Plugins appeared first on MarketingPlatform - Dansk Email Marketing Software.

We categorize websites into three different categories.

• Standard systems like native WooCommerce or Adobe Commerce
• Standard systems as above, but with custom plugins installed in key areas
• Custom systems or systems that are unknown to us.

We will be able to natively track all of the pages your visitors visit in all three categories. Events such as adding and removing products from baskets will vary depending on your system.

The guide below is for custom shop systems and systems that are unknown to us.

By the end of this guide, you will have set up Tracking and synchronization to handle the following

Contact Date

• Flat data such as name, birthday, and permission (with the use of Connector or API)
• Deep transactional data (with the use of Connector or API)

Events

• Page visited
• Product visited
• Category visited
• Product/category added to cart (with the use of Google-tag-manager)
• Product/category removed from the cart (with the use of Google-tag-manager)
• Product/category bought (with or without the use of Google-tag-manager)

Step 1. Create Product Feed and Sitemap

First off you will have to add your Product Feed and the Sitemap to your webshop. This is a requirement since the very heart of Tracking requires us to know your Products and pages in order to record who has visited what.

In-depth details about setting up Feeds and Sitemaps can be found here.

Step 2. Setup Tracking

With the Product Feed and Sitemap added we can now set up the Tracking. In the Tracking, you are able to tell us which element in your Product Feed is the Category, Product ID, Sales Price, etc. This will be used in Segments and bridging the Tracking information with the Order data saved in One-to-Many empowering you to target Contacts who have or have not bought, have visited but not bought, etc. from a specific Product Category, Price range, etc.

If we do not detect your webshop you will have to map this manually.

In order to be empowered with the full potential of the benefits of Tracking it is required to map at least the following:

• Product Events
• Product Link
• Product Category
• Product ID
• Cart Page
• Checkout 
• Thank You Page.

It is advised to map more, but not required.

You have now set up enough for us to track what is highlighted with green at the top of this article:

Events

• Page visited
• Product visited
• Category visited

Contact Data

In order to synchronize Contact Data you can set up a Connector(link to connector wiki) or use our API (link to API documentation). With that, you will have set up the following Contact Data:

Contact Data

• Flat data such as name, birthday, and permission (with the use of Connector or API)
• Deep transactional data (with the use of Connector or API)

Events

In order to synchronize the events highlighted in yellow at the top of this article, you can manually tell us when these events occur. 

• Product/category added to cart (with the use of Google-tag-manager)
• Product/category removed from cart (with the use of Google-tag-manager)
• Product/category bought (with or without the use of Google-tag-manager)

We advise the use of Google Tag-manager since most webshops have installation tutorials for Google Tag-manager and it is widely used by most websites.

These are the data we need for each event

You can simply create a custom event using Google tag-manager to tell us when things happen depending on the Trigger you choose.

Creating a custom HTML in Google tag-manager

Creating a Custom HTML Tag as above requires two things to send us the data:

1. You need the ProductID as a variable in order to send it to us
2. You need to have your event setup as a Trigger to fire the above Tag

The visitors’ journey and congruence between Sitemap, site, and product feed.

For us to combine the knowledge of which products have been browsed and added to cart there are two important elements in the product feeds that bind the Sitemap and webshop together.

1. Product link. When a customer is visiting a site, we are checking the mapped “Product Link (URL)” and find the product he visited. From that we can see the product id and thereby the category, price etc for the product he visited. It is important that the mapped element for “Product Link (URL)” contains the link in a format shown below

2. Product Unique Identifier (id). When a product is added to cart it is not visible in the URL alone, and there are many ways for the customer to add an item to the cart without being on the product page itself (search results, main pages with a list of products, and an add-to-cart option, etc.).

Most webshops are saying that a specific product id has been added to the basket.  For the standard systems we know what that looks like, so all you need to do is to map the “Product Unique Identifier (id) with what is the product id used on the webshop.

It is important that the product ids are the same on the webshop and in the Product Feed – since when the shop is telling us a customer has added Product id “421” to the cart, we will check for product “421” in the Product Feed. If the ids are not the same – there will be no matches found and we will not know which product he added and have nothing to insert in Campaigns or show in Segments.

The post How to Set Up Tracking on a Custom System appeared first on MarketingPlatform - Dansk Email Marketing Software.

Setup requirements

In order to set up tracking in MarketingPlatform, you must upload a sitemap – if you have a shop, you must also upload a product feed.

Your sitemap must be in xml format, i.e., domain.xml

Your sitemap or product feed is uploaded under “integration – feed cache”.

More about feed cache here.

Tracking setup

In the menu on the left, you will find Tracking – create tracking > Name your tracking.

If you wish, you can edit how long your LeadScores should be kept. The period must reflect your purchase process. If you sell pencils, your period must be shorter than if you sell cars.

You can also define the LeadScore of other actions here if our default does not make sense in your case. Press next when you are done with your settings.

On the next page, connect your sitemap and product feed and generate the script to be used on your website.

Choose which list you want the tracking to be set up with. Select the product feed – if you do not have one, use the little toggle and deselect the feed to be used.

Enter your website URL and select your sitemap. You can click on test sitemap and see if it reads correctly. If you have a webshop, this is where you can manually add your purchase pages to the setup. These are usually not to be found in your sitemap.

Press next, when you are ready for the next step.

On the last page of the setup, you need to map the different pages in your sitemap and any product feed.

Product link (URL), product category (primary) and product unique identifier (ID) are required to map if you have a webshop. Map as much as possible and press save when you are done. You can always come back and map more.

You now need to take the tracking script and implement it on your website. You might also need to implement custom events like “add to cart, remove from cart etc.” manually in your webshop.

Custom events:

Add To Cart

var data = {}; 
data['empattr_id'] = %%PRODUCT ID%%; 
data['empattr_qty'] = %%PRODUCT QUANTITY%%; 
data['leadscore'] = %%LEADSCORE VALUE%%; 
_empTrack.action('addtocart',0,data);


Remove From Cart

var data = {}; 
data['empattr_id'] = %%PRODUCT ID%%; 
data['empattr_qty'] = 0; 
data['leadscore'] = %%LEADSCORE VALUE%%; 
_empTrack.action('rmfromcart',0,data);


Empty Cart

var ts = Math.round((new Date()).getTime() / 1000);"; 
var data = {}; 
data['empattr_actiontime'] = ts; 
_empTrack.action('updatecartstart',0,data);


Update Cart Items

var ts = Math.round((new Date()).getTime() / 1000);"; 
var data = {}; 
data['empattr_actiontime'] = ts; 
_empTrack.action('updatecartstart',0,data); 


--------ITERATE THIS CALL FOR EACH ITEM THAT NEED TO BE UPDATED IN CART-------- 
var data = {}; 
data['empattr_id'] = %%PRODUCT ID%%; 
data['empattr_qty'] = %%PRODUCT QUANTITY%%; 
data['empattr_actiontime'] = ts; 
_empTrack.action('updatecart',0,data); 
-------------------------------------------------------------------------------

Custom Event

var data = {}; 
_empTrack.action('%%CUSTOM EVENT NAME%%',1,data

The post Setting up Tracking appeared first on MarketingPlatform - Dansk Email Marketing Software.