After you have successfully signed up for and signed into Google
Analytics, you need to click on the Admin navigation menu item near
the top of the screen.
screen_shot_1
Then you need to create a new 'account' from the Account drop down
which will take you to a new page where you will need to fill out
information about the account.
screen_shot_2
Make sure to select 'Website' for what you would like to track and the
'Universal Analytics Beta' radio button for the tracking method.
screen_shot_3
Create an account name (can be what every you would like as long as it
is unique for your list of created accounts).
screen_shot_4
You also need to setup an initial property to be associated with this
account. A property is your NTER website. You can have multiple
properties associated to this account you are creating but you will
need to add the other properties after you have finished creating this
initial account.
Enter a website name (this will be your property name and can be what
ever you would like as long as it is unique for all properties
associated to this account that you are creating).
screen_shot_5
Enter the website URL (make sure to select the appropriate HTTP or
HTTPS for your property and the rest of the URL to get to your property).
screen_shot_7
Pick the appropriate Industry Category and Reporting Time Zone for
your business.
screen_shot_6
Leave all the Data Sharing Setting checked (by default) unless you
have a specific reason to not check one and then click the Get
Tracking ID button.
screen_shot_8
Accept the Terms of Service dialog.
screen_shot_9
This will create the new account and the initial property associated
to that account and generate a Google Analytics ID for you and display
a page with your tracking ID and a section of JavaScript code that you
will need in a minute.
Copy the JavaScript code someplace (like Notepad or TextEdit) so you
can easily get to it in steps below when setting up Google Analytics
on your Liferay and Illias services.
Setup Liferay
Now you are ready to add Google Analytics to your NTER node. First we
will setup Google Analytics on your Liferay side. You will need to
login to your NTER Liferay portal using an account with Admin rights.
If you logged in successfully with an account that has admin rights,
you should see a menu bar at the top of the page that looks like the
following:
screen_shot_10
Select the Go to > Control Panel menu item which will take you to
another page with a list of control panel options on the left hand
side of the page.
screen_shot_11
Select from the drop down on the left either your entire NTER node or
the specific NTER node name.
screen_shot_12
Then select 'Site Settings' on the left and 'Analytics' on the right
under Advanced. Enter the Google Analytics ID in the text edit box in
the center of the screen and then click the Save button on the right
under Advanced.
screen_shot_13
screen_shot_14
That will behind the scenes add Google Analytics to every page on your
node.
You have to embed the Google Analytics stuff in a web page. The web
pages in Ilias/NWTP are generated from PHP code.
So you have to modify the PHP code or some of the base HTML that PHP
uses. The easiest way to do that is modify the page headers.
The page headers are set up in the skin, so creating a new skin is a
rather quick and painless way to this.
It also lets you set up different analytic accounts that you can change
to by just selecting a new skin in NWTP.
Rick
On 3/17/2014 12:01 AM, Michael Steele wrote:
Why is it necessary to create a new skin? Obviously we'd want to
backup the old version before modding it. But couldn't we just edit
the existing skin files to add the Analytics snippet?
Also, were you able to validate that all of the pages leverage these
skins? Specifically when the content plays? After all, that's really
the only place the learners touch the LMS. My guess is that the tpl...
pages would cover this, but just wondered if you verified.
Did you test passing any additional LMS metadata back to Google
Analytics? Like course number/name or even user demographic info? I
know Google supports generic metadata tracking, but also some specific
information (related to ecommerce) that we could leverage if it's easy
to pull out of the NTERLMS database.
You have to embed the Google Analytics stuff in a web page. The web
pages in Ilias/NWTP are generated from PHP code.
So you have to modify the PHP code or some of the base HTML that PHP
uses. The easiest way to do that is modify the page headers.
The page headers are set up in the skin, so creating a new skin is a
rather quick and painless way to this.
It also lets you set up different analytic accounts that you can
change to by just selecting a new skin in NWTP.
Rick
On 3/17/2014 12:01 AM, Michael Steele wrote:
Why is it necessary to create a new skin? Obviously we'd want to
backup the old version before modding it. But couldn't we just edit
the existing skin files to add the Analytics snippet?
Also, were you able to validate that all of the pages leverage these
skins? Specifically when the content plays? After all, that's really
the only place the learners touch the LMS. My guess is that the
tpl... pages would cover this, but just wondered if you verified.
Did you test passing any additional LMS metadata back to Google
Analytics? Like course number/name or even user demographic info? I
know Google supports generic metadata tracking, but also some
specific information (related to ecommerce) that we could leverage if
it's easy to pull out of the NTERLMS database.
Thanks Hap! Great instructions!
Glad you got that working.
Rick
On 3/13/2014 12:25 PM, Hap Pearman wrote:
You have to embed the Google Analytics stuff in a web page. The web
pages in Ilias/NWTP are generated from PHP code.
So you have to modify the PHP code or some of the base HTML that PHP
uses. The easiest way to do that is modify the page headers.
The page headers are set up in the skin, so creating a new skin is a
rather quick and painless way to this.
It also lets you set up different analytic accounts that you can change
to by just selecting a new skin in NWTP.
Rick
On 3/17/2014 12:01 AM, Michael Steele wrote:
On 3/17/2014 12:28 PM, Rick Fincher wrote: