@meniga/analytics
Advanced tools
Comparing version 4.0.4-alpha.229 to 4.1.0
@@ -7,3 +7,3 @@ { | ||
}, | ||
"version": "4.0.4-alpha.229+642c0c1", | ||
"version": "4.1.0", | ||
"description": "A library to track events and send them to analytics services, like meniga, google, avo or segment", | ||
@@ -30,3 +30,3 @@ "main": "lib/index.js", | ||
}, | ||
"gitHead": "642c0c1b62bff095878a67745d8bebd9ec2ce584" | ||
"gitHead": "a757d6e9446ce407c9c6302c6ad892e4a0d2121a" | ||
} |
@@ -6,3 +6,5 @@ # @meniga/analytics | ||
## Getting started | ||
--- | ||
Create a config file called tracking.js in your container app that specifies which tracking services should be enabled. | ||
@@ -41,3 +43,5 @@ | ||
## Tracking an event | ||
--- | ||
To track an event you need to import the analytics actions to your component, like this: | ||
@@ -103,3 +107,5 @@ | ||
## Adding new services | ||
--- | ||
Right now we have a built in support for google analytics, segment.com and the meniga /eventtracking api service. In order to add support for a new service, you need to add code to the *identifyUser* and *trackEvent* functions in *api.js* that deals with calling that service. Then you also might have to add code to the *initialize.js* file to initialize the connection to the service. | ||
@@ -106,0 +112,0 @@ |
Manifest confusion
Supply chain riskThis package has inconsistent metadata. This could be malicious or caused by an error when publishing the package.
Found 1 instance in 1 package
No v1
QualityPackage is not semver >=1. This means it is not stable and does not support ^ ranges.
Found 1 instance in 1 package
1
166
0
21626