@@ -118,7 +118,7 @@ <h4>1-line setup</h4>
118
118
< div class ="container ">
119
119
< section id ="getting-started " analytics-on ="scrollby " analytics-category ="Scrolling " scrollby-offset ="20% ">
120
120
< div class ="page-header "> < h3 > Getting started</ h3 > </ div >
121
- < section >
121
+ < section id =" installation " >
122
122
< h4 > Installation</ h4 >
123
123
< p > Download Angulartics and the Angulartics plugin for your vendor. Note: All plugins list Angulartics as a dependency, so they will be downloaded together.</ p >
124
124
< pre > < code > $ bower install < strong class ="highlighted "> angulartics-google-analytics</ strong > --save</ code > </ pre >
@@ -162,7 +162,7 @@ <h4>Declarative event tracking</h4>
162
162
</ section >
163
163
< br >
164
164
165
- < section >
165
+ < section id =" inferred-values " >
166
166
< h4 > Inferred values</ h4 >
167
167
< p > < code > analytics-on</ code > always needs to be present, because it is the attribute that enables
168
168
event tracking for the element. All other attributes will be inferred if omitted.</ p >
@@ -177,7 +177,7 @@ <h4>Inferred values</h4>
177
177
</ section >
178
178
< br >
179
179
180
- < section >
180
+ < section id =" additional-parameters " >
181
181
< h4 > Additional parameters</ h4 >
182
182
< p > Each vendor has its own set of tracking properties. For example, < strong > Google Analytics</ strong > have
183
183
< i > category</ i > and < i > label</ i > .
@@ -202,7 +202,7 @@ <h4>Scroll tracking</h4>
202
202
</ section >
203
203
< br >
204
204
205
- < section >
205
+ < section id =" using-the-api " >
206
206
< h4 > Using the API</ h4 >
207
207
< p > In order to track pageviews and events from within your application logic,
208
208
inject < code > $analytics</ code > and invoke either the < code > pageTrack()</ code >
0 commit comments