Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: initialize server side google analytics with multiple options #64

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

asastre
Copy link

@asastre asastre commented Jun 23, 2020

Update for Google Analytics plugin

When tracking from server side sometimes is needed to share the clientId created in the browser so the tracking on both sides (browser and server) represents the flow done by the same user.

Now, the Google Analytics can be initialized on the server side only with the trackingId, not being able to specify a clientId, but the universal-analytics library accepts more options on its initialization, including the clientId, userId, etc.

This PR enables the possibility of initializing the Google Analytics on the server side with all the possible options that universal-analytics accepts and also mantaining the actual configuration.

@asastre asastre changed the title feat: initialize server side analytics with multiple options feat: initialize server side google analytics with multiple options Jun 23, 2020
* @param {string} pluginConfig.trackingId - Google Analytics site tracking Id. Same as tid (se below), only one needed
* @param {string} pluginConfig.tid - Google Analytics site tracking Id. Same as trackingId (se above), only one needed
* @param {string} [pluginConfig.cid] - Google Analytics client Id. It generates a random UUID if none is set
* @param {boolean} [pluginConfig.strictCidFormat] - Set it to false to set a custom client Id (not UUID). Only used if cid is set
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't look like strictCidFormat is used. Do we need that?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, you need to set strictCidFormat to false if you want to use a non UUID clientId. It's explained in the readme file and also you can see here how it's used.

@@ -7,12 +7,24 @@ if (!process.browser) {
/**
* Serverside Google Analytics plugin
* @param {object} pluginConfig - Plugin settings
* @param {string} pluginConfig.trackingId - Google Analytics site tracking Id
* @param {string} pluginConfig.trackingId - Google Analytics site tracking Id. Same as tid (se below), only one needed
* @param {string} pluginConfig.tid - Google Analytics site tracking Id. Same as trackingId (se above), only one needed
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tid property looks like a repeat of trackingId do we need that or can we just use the trackingId field?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it is indeed.
I added this 4 new docummented attributes of pluginConfig but there are more that can be used in universal-analytics initialization.
I keeped the trackingId attribute in order to keep compatibility with the actual implementation and also allow to define all the attributes accepted in universal-analytics initialization.
Maybe it would be better to keep the actual jsDoc and add only a reference to all the possible attributes that can be used in pluginConfig and explaining that the trackingId attribute can be declared also as tid.

@DavidWells
Copy link
Owner

Thanks for the PR! ❤️

Added a couple of notes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants