@mate-academy/sourcebuster 1.1.3 → 1.1.4

package/README.md

@@ -4,6 +4,9 @@
 
 Read [upgrade guide](UPGRADING.md) for details.
 
+## Source
+This package is a modified clone of [sourcebuster js functionality](https://github.com/alex35mil/sourcebuster-js).
+
 ## About
 * Sourcebuster tracks the sources of your site’s visitors and stores the data in the cookies for further analysis.
 * It handles sources-overriding just like Google Analytics does.
@@ -203,14 +206,14 @@ So by default the cookies are shared. However if you don't want to share them
 
 Let’s take a look at further examples.
 
-**No. 1**  
+**No. 1**
 The first scenario. You have a site: **wow.com**. Also you have a blog on this site: **blog.wow.com**. And you don’t want to separate traffic between them. It means that when the visitor come from **blog.wow.com** to **wow.com**, it won’t be a new visit for **wow.com** (with **blog.wow.com** as Referral source), it will be a common inner click without source change (to sourcebuster.js this scenario will be equal to inner page change: from *wow.com/about* to *wow.com/contacts* for example). To achive this you have to add this line on both sites: **wow.com & blog.wow.com**.
 
 ```javascript
 domain: 'wow.com'
 ```
 
-**No. 2**  
+**No. 2**
 That was simple. Now lets take a look at opposite scenario — you want to separate traffic between your subdomains and consider it as Referral. There is the main site — **wow.com**, and there is a blog on this site — **blog.wow.com**, which also has users subdomains — **alex.blog.wow.com** is one of them. You don’t want to separate traffic between **blog.wow.com** and **alex.blog.wow.com**, but you do want to separate it between all the blogs and the main site. Here’s how we can sort it out:
 
 ```javascript
@@ -220,7 +223,7 @@ domain: {
   isolate: true
 }
 
-// and this on the blogs subdomains (blog.wow.com & alex.blog.wow.com) 
+// and this on the blogs subdomains (blog.wow.com & alex.blog.wow.com)
 domain: 'blog.wow.com'
 ```
 
@@ -521,7 +524,7 @@ All data are stored in cookies. When the script is pushed to production, visitor
 
 #### sbjs_current & sbjs_first
 
-*Format*  
+*Format*
 `typ=organic|||src=google|||mdm=organic|||cmp=(none)|||cnt=(none)|||trm=(none)`
 
 *Examples*
@@ -546,7 +549,7 @@ typ=typein|||src=(direct)|||mdm=(none)|||cmp=(none)|||cnt=(none)|||trm=(none)
 
 #### sbjs_current_add & sbjs_first_add
 
-*Format*  
+*Format*
 `fd=2014-06-11 17:28:26|||ep=http://statica.alexfedoseev.com/sourcebuster-js/|||rf=https://www.google.com`
 
 
@@ -558,7 +561,7 @@ typ=typein|||src=(direct)|||mdm=(none)|||cmp=(none)|||cnt=(none)|||trm=(none)
 
 #### sbjs_udata
 
-*Format*  
+*Format*
 `vst=2|||uip=192.168.1.1|uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36`
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mate-academy/sourcebuster",
-  "version": "1.1.3",
+  "version": "1.1.4",
   "description": "Get sources of your site's visitors (utm / organic / referral / typein).",
   "license": "MIT",
   "keywords": [