Please note: no personal information is stored in cookies and they cannot contain viruses.

Full text

(1)

Tracking Script

The Mojn tracking script is used to track your visitor behaviour. When the script is implemented on your site, a cookie is saved to your visitors’ browser when they visit your site. After a user has been tagged, Mojn is able to track her behaviour and recognise her on websites she visits.

Please note: no personal information is stored in cookies and they cannot contain viruses.

Based on the data collected in the tracking process, Mojn is able to deliver recommendation images that are personalised for the users' behaviour. In addition, the tracked data is used to place all your visitors into segments, based on their browsing behaviour on your website.

The tracking script is a small piece of javascript that looks like the script below:

The script should be inserted on all of your pages. It is not page specific, so you can safely place it in your template that is included site-wide. We recommend that it is placed in the header just before the closing head tag </ head>. That said, you are free to place it wherever you want.

The script is loaded asynchronously and does not block loading of any other content on the page. Please note that the script is unique for each Mojn customer, so your script will contain a

unique ‘customer code’ instead of [CUSTOMER_CODE].

WHAT IS THE TRACKING SCRIPT USED FOR?

<!-- Mojn tracker begin --> <script type="text/javascript"> var _mojnTrack = _mojnTrack || []; _mojnTrack.push({ cid:"OF8YO" }); (function(d) { try {

var scr = d.getElementsByTagName("script")[0], f = d.createElement('iframe');

f.src = "javascript:''"; f.style.display = "none"; scr.parentNode.insertBefore(f, scr); f.contentWindow.name = "mjn:scrf";

var d2 = f.contentWindow.document,fn='write';

d2.open()[fn]("<body onload=\"var d=document,s=d.createElement('script');s.src='// track.idtargeting.com/[CUSTOMER_CODE]/track.js';d.body.appendChild(s);\">");

d2.close();

}catch(e){}})(document); </script>

<!-- Mojn tracker end -->

(2)

Tracking Script

If you want to track custom on click events (e.g. launching a modal or similar) or ajax events, you can call the method below:

An example would then look like this:

Please note: the call method takes an [URL] as an argument. The [URL] has to be unique, and since it’s not tracking a real URL it has to be a fictive/pseudo URL representing the specific “event”.

(OPTIONAL) HOW TO TRACK ADDITIONAL CLICK EVENTS?

_mojnTrack.push({ u:"[URL]" });

(3)

Email Open Tracking Pixel

The email open tracking pixel is a small invisible image file that you need to insert into you email template. When an email subscriber opens one of your emails and downloads the invisible image, a request is sent to Mojn’s servers. In this request, the email subscribers unique ID should be present. Mojn is then able to associate the subscriber’s unique email ID to a tracker cookie we already have on our servers. This enables Mojn to later generate customized recommmendation images for your various customers.

<img width="1" height="1"

src="https://matcher.idtargeting.com/email.gif?cid=[CUSTOMER_CODE]&_mjnctid=[UNIQUE_ID]">

WHAT IS THE EMAIL OPEN TRACKING PIXEL?

HOW TO IMPLEMENT THE EMAIL OPEN TRACKING PIXEL?

The email open tracking pixel is an image tag that needs to be inserted in your email template. To enable us to integrate the feed, it should look like the following:

2 variables above need to be replaced: 1) the [CUSTOMER CODE] and 2) the [UNIQUE ID].

The Customer Code - [CUSTOMER CODE]

The customer code is provided by Mojn and should never be changed. The customer code is a 5 character long unique identifier containing both numbers and capital letters.

The Unique ID - [UNIQUE ID]

The unique ID is to be inserted into image tag by you. Depending on the email system you use, you should insert a command that would make your email system insert a unique ID per email subscriber into this place. It’s really easy.

For example, in Mailchimp this command (or tag as they call it) is *|EMAIL|* for a user’s email address. Note that these commands vary for different email newsletter providers. Feel free to contact us in case you need assistance.

A correctly implemented tag for a client with the customer code VIP33 using Mailchimp would look like this:

We only have one important requirement for the unique ID that you use: it must be unique for each newsletter subscriber. You can use an email addres, an internal ID or even a customer ID.

<img width="1" height="1"

(4)

Sales Conversion Pixel

A campaign’s performance is measured by how many derivative sales the campaign entails and how much these sales generate in revenue. In order for Mojn to measure these parameters and associ-ate them with a campaign, you have to insert the sales conversion pixel, which sends the necessary information back to us. The necessary parameters are the currency used in a transaction and the total value of the transaction. Mojn sales conversion pixel enables you to later follow the results of your campaign within our web application.

The sales conversion pixel code is as following:

The pixel must be implemented on your purchase confirmation page – i.e. the page after the cus-tomer has completed the entire purchase process (completed payment and confirmed the pur-chase). In addition, the pixel must be inserted after Mojn Tracking Script. The variables [CURRENCY], [AMOUNT] and [ORDER_ID] must be filled in dynamically with the corresponding values for a specif-ic order.

A few examples of correct currency and amount values transmitted to Mojn: USD123.34 = 123 Dollars and 34 cents.

EUR2,000.00 = 2,000 Euros and 0v cents. DKK200.00 = 200 Danish kroner

Please note the following: The decimal separator of the value needs to be “." and thousands separa-tor is optional. The currency code should be in ISO 4217 format (read more here: http://en.wikipidia. org/wiki/ISO_4217). The customer code is provided by Mojn. This is your unique identifer and may not be changed. The order ID is optional and is mostly used to prevent fraud.

A correctly implemented tag for a standard DanDomain webshop should look like the tag below (for the client with the customer code WIN99):

The commands that fetch the values from the order vary for each e-commerce system. If you do not know the correct commands for your e-commerce system please feel free to contact us or alterna-tively use your existing e-commerce system’s support line.

<img src="//matcher.idtargeting.com/cnv/[CUSTOMER_CODE]?amt=[CURRENCY][AMOUNT]&oid=[ORDER_ID]" height="0" width="0">

WHAT IS THE SALES CONVERSION PIXEL USED FOR?

HOW TO IMPLEMENT THE SALES CONVERSION PIXEL?

<img src="//matcher.idtargeting.com/cnv/WIN99?amt=DKK[[SubTotalInclVATUSNoCur]]&oid=[[OrderID]]" height="0" width="0">

(5)

Sales Conversion Pixel

Sales Tracking Pixel also support an optional oid parameter (for Order ID). E.g. set oid=00000123 if you want to parse the Order ID along to Mojn.

As an alternative to the “Sales Conversion Pixel" you can use Mojn’s simpler JavaScript API. The correct syntax can be seen below:

An example would then look like this:

Please note: the Javascript conversion API call does not support oid (Order ID) yet.

<script type="text/javascript">

var _mojnTrack = _mojnTrack || [];

_mojnTrack.push({ cid:"[CUSTOMER_CODE]"}); _mojnTrack.push({ conv:"[CURRENCY][AMOUNT]" }); </script>

(OPTIONAL) ORDER PARAMETER FOR THE SALES PIXEL

(ALTERNATIVE) JAVASCRIPT SNIPPET INSTEAD OF THE SALES PIXEL

<script type="text/javascript">

var _mojnTrack = _mojnTrack || []; _mojnTrack.push({ cid:"WIN99"}); _mojnTrack.push({ conv:"USD2,000.00" });

(6)

Product Feed

In order to create personalised retargeting images, Mojn “scrapes” your website for all product names, product prices and product images. In some cases though, it might be necessary for us to get a “product feed” from you instead. This makes sense especially for:

• websites with more than 2.000 products

• websites that add new products on a daily basis Before we can import the feed, there are a few requirements:

• It is important that the product URL provided in the feed is 100% compatible with the product URL that users come in and look at on the website.

• Import lever must be able to identify what constitutes photo references – e.g. images have a reference <productImg>.

WHAT IS THE PRODUCT FEED?

<items> <item> <url>http://somesite/redshoe.html</url> <name>Red shoe</name > <price>199.95</price> <productImg>http://somesite/redshoe.gif</productImg> </item> <item> <url>http://somesite/blueshoe.html</url> <name>Blue shoe</name > <price>449.95</price> <productImg>http://somesite/blueshoe.gif</productImg> </item> … </items>

WHAT’S THE PREFERRED STRUCTURE OF THE PRODUCT FEED?

To enable us to integrate the feed, it should look like the following:

The tags that define an element <url>, <name>, <price> & <productImg> are those that will be export-ed and shown within the recommendation image. E.g. if we define <name>Rexport-ed shoe</name > in the feed, the text “Red shoe” will be shown in the image etc.

Please note: the elements shown in the feed example above are standard elements for our standard

Figure

Updating...

References

Updating...

Related subjects :