This module provides interface to add events for tracking in Google Analytics.
Installation
Enable module (it creates field collection 'Google Events').
Add this field collection to every content type that you want.
Note: you need Google Analytics tracking code on your site
Usage
On particular node in 'Google Events' field collection fill all 4 fields:
1. Target Class (item class that you want to track)
2. Event Type (use mousedown or submit)
3. Event Category (event category in GA dashboard. Example, 'test category')
4. Event Label (event label in GA dashboard. Example, 'test label')
Project Page:
https://www.drupal.org/sandbox/oss-usa.com/2313051
GIT:
git clone --branch 7.x-1.x oss-usa.com@git.drupal.org:sandbox/oss-usa.com/2313051.git
Comments
Comment #1
oss-usa.com commentedComment #2
oss-usa.com commentedComment #3
PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxoss-usacom2313051git
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #4
klausihttps://www.drupal.org/project/google_analytics_et
This sounds like a feature that should live in the existing google_analytics_et project. Module duplication and fragmentation is a huge problem on drupal.org and we prefer collaboration over competition. Please open an issue in the google_analytics_et issue queue to discuss what you need. You should also get in contact with the maintainer(s) to offer your help to move the project forward. If you cannot reach the maintainer(s) please follow the abandoned project process.
If that fails for whatever reason please get back to us and set this back to "needs review".
Comment #5
oss-usa.com commentedCode style issues were resolved.
https://www.drupal.org/project/google_analytics_et
You need to know programming to create a module and make different arrays with google_analytics_et module instruction. And if you need to track link from particular node you need to create some condition. And you need to do this for every node, for every link.
Google Analitycs simple event tracking module is pretty simple, you need to enable it and fill the fields in drupal CMS.
Comment #6
oss-usa.com commentedComment #7
oss-usa.com commentedComment #8
pkamerakodi commentedManual review:
1) $current_collection_item = $field_collection[$field_collection_id];. It is better to add a isset and also a if check below to handle cases if current collection item returns empty.
2) The $variables array contains the following arguments: it should $vars.
3) I see a comment hook install but it is not implemented
/**
* Implements hook_install().
*/
Regards,
Prajwal
Comment #9
oss-usa.com commentedpkamerakodi, thank you for review.
I hope that all issues were fixed.
Comment #10
oss-usa.com commentedComment #11
danharper commentedIndividual user account
[No: Does not follow] the guidelines for individual user account.
No user profile details, seems to be company rather than individual
No duplication
[Yes: Does not cause]
Master Branch
[No: Does not follow] the guidelines for master branch.
There is still a master branch, make sure to set the correct default branch: https://www.drupal.org/node/1659588 . Then remove the master branch, see also step 6 and 7 in https://www.drupal.org/node/1127732
Review of the 7.x-1.x branch (commit 4727085):
Licensing
[Yes: Follows] the licensing requirements.
3rd party assets/code
[Yes: Follows] the guidelines for 3rd party assets/code.
README.txt/README.md
[No: Does not follow] the guidelines for in-project documentation and/or the README Template.
git clone on project page should be git clone --branch 7.x-1.x http://git.drupal.org/sandbox/oss-usa.com/2313051.git
Code long/complex enough for review
[Yes: Follows] the guidelines for project length and complexity.
Secure code
[Yes: Meets the security requirements.]
Coding style & Drupal API usage
[List of identified issues in no particular order. Use (*) and (+) to indicate an issue importance. Replace the text below by the issues themselves:
(*)Requires field_list requirement adding to module.
Comment #12
danharper commentedComment #13
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.