@frontity/comscore-analytics
Comscore Analytics package for Frontity
Install
npm i @frontity/comscore-analytics
Settings
The namespace for this package is comscoreAnalytics
Every Comscore account has a Tracking ID.
To connect the package with a specific account (or accounts) we can set the following properties in the frontity.settings.js
:
state.comscoreAnalytics.trackingId
: to specify just one tracking IDstate.comscoreAnalytics.trackingIds
: to specify a list of tracking ID's
export default {
packages: [
{
name: "@frontity/comscore-analytics",
state: {
comscoreAnalytics: {
trackingId: "34567890",
},
},
},
],
};
export default {
packages: [
{
name: "@frontity/google-tag-manager-analytics",
state: {
comscoreAnalytics: {
trackingIds: ["34567890", "56789012"],
},
},
},
],
};
Usage
This @frontity/comscore-analytics
package can co-exist with some other analytics
packages. Once we have properly installed and configured these analytics
packages, their actions will be centralized by the analytics
namespace
actions.analytics.pageview
will take into account settings in state.analytics.pageviews
actions.analytics.event
will take into account settings in state.analytics.events
Read More info about how to use Analytic packages in the docs
actions.analytics.pageview
If @frontity/comscore-analytics
is configured and enabled for pageviews, every time a link changes (or every time action.router.set(link)
is launched) a tracking for that page will be sent to Google Analytics
actions.analytics.event
This package doesn't actually track events for Comscore so any call of the method actions.analytics.event()
will have no effect for this service
Feature Discussions
Feature Discussions about Frontity are public. You can join the discussions, vote for those you're interested in or create new ones.
These are the ones related to this package: https://community.frontity.org/tags/c/feature-discussions/33/comscore-analytics
Changelog
Have a look at the latest updates of this package in the CHANGELOG
» Frontity Resources 🌎
We have a number of different channels at your disposal where you can find out more information about the project, join in discussions about it, and also get involved:
- 📖 Docs: our primary documentation resource - this is the place to learn how to build amazing sites with Frontity.
- 👨👩👧👦 Community forum: join our forum and ask questions, share your knowledge, give us feedback and tell us how we're doing, and meet other cool Frontity people. We'd also love to know about what you're building with Frontity, so please do swing by the forum and tell us about your projects.
- 🐞 Contribute: we use GitHub for bugs and pull requests. See our Contributing section to find out how you can help develop Frontity, or improve this documentation.
- 🗣 Social media: interact with other Frontity users. Reach out to us on Twitter. Mention us in your tweets about Frontity and what you're building by using
@frontity
. - 💌 Newsletter: do you want to receive the latest news about Frontity and find out as soon as there's an update to the framework? Subscribe to our newsletter.
» Get involved 🤗
Got questions or feedback about Frontity? We'd love to hear from you in our community forum.
Frontity also welcomes contributions. There are many ways to support the project! If you don't know where to start then this guide might help: How to contribute?.
If you would like to start contributing to the code please open a pull request to address one of our good first issues.