1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
|
=====================================
Spring Metrics -- conversion tracking
=====================================
`Spring Metrics`_ is a conversions analysis tool. It shows you the top
converting sources, search keywords and landing pages. The real-time
dashboard shows you how customers interact with your website and how
to increase conversion.
.. _`Spring Metrics`: http://www.springmetrics.com/
Installation
============
To start using the Spring Metrics integration, you must have installed
the django-analytical package and have added the ``analytical``
application to :const:`INSTALLED_APPS` in your project
:file:`settings.py` file. See :doc:`../install` for details.
Next you need to add the Spring Metrics template tag to your templates.
This step is only needed if you are not using the generic
:ttag:`analytical.*` tags. If you are, skip to
:ref:`spring-metrics-configuration`.
The Spring Metrics tracking code is inserted into templates using a
template tag. Load the :mod:`spring_metrics` template tag library and
insert the :ttag:`spring_metrics` tag. Because every page that you
want to track must have the tag, it is useful to add it to your base
template. Insert the tag at the bottom of the HTML head::
{% load spring_metrics %}
<html>
<head>
...
{% spring_metrics %}
</head>
...
.. _spring-metrics-configuration:
Configuration
=============
Before you can use the Spring Metrics integration, you must first set
your website Tracking ID and tag a page for conversion. You can also
customize the data that Spring Metrics tracks.
Setting the Tracking ID
-----------------------
Every website you track with Spring Metrics gets its own Tracking ID,
and the :ttag:`spring_metrics` tag will include it in the rendered
Javascript code. You can find the Tracking ID in the `Site Settings`_
of your Spring Metrics account. Set :const:`SPRING_METRICS_TRACKING_ID`
in the project :file:`settings.py` file::
SPRING_METRICS_TRACKING_ID = 'XXXXXXXXXX'
If you do not set a Tracking ID, the tracking code will not be rendered.
.. _`manage page`: https://app.springmetrics.com/manage/
.. _`Convertion Tagging`:
Tagging conversion
------------------
In order to make use of Spring Metrics, you must tell it when visitors
become customers. This is called conversion. Usually, it marked by
the client requesting a specific page, such as the "thank you" page
of a webshop checkout. You tag these pages in the `Site Settings`_
of your Spring Metrics account.
Alternatively, you can mark conversion pages using the
:data:`spring_metrics_convert` template context variable::
context = RequestContext({'spring_metrics_convert': 'mailinglist signup'})
return some_template.render(context)
.. _`Site Settings`: https://app.springmetrics.com/manage
Tracking revenue
----------------
Spring Metrics allows you to track the value of conversions. Using the
:data:`spring_metrics_revenue` template context variable, you can let
the :ttag:`spring_metrics` tag pass earned revenue to Spring Metrics.
You can set the context variable in your view when you render a
template containing the tracking code::
context = RequestContext({
'spring_metrics_convert': 'sale',
'spring_metrics_revenue': '30.53',
})
return some_template.render(context)
(You would not need to use the :data:`spring_metrics_convert` variable
if you already tagged the page in Spring Metrics.)
Custom data
-----------
Spring Metrics can also track other data. Interesting examples could be
transaction IDs or the e-mail addresses from logged in users. By
setting any :data:`spring_metrics_X` template context variable, Spring
Metrics will track a variable named :data:`X`. For example::
context = RequestContext({
'spring_metrics_revenue': '30.53',
'spring_metrics_order_id': '15445',
})
return some_template.render(context)
Some variables should be passed on every page and can be computed from
the request object. In such cases you will want to set custom
variables in a context processor that you add to the
:data:`TEMPLATE_CONTEXT_PROCESSORS` list in :file:`settings.py`::
def spring_metrics_global_variables(request):
try:
profile = request.user.get_profile()
return {'spring_metrics_city': profile.address.city}
except (AttributeError, ObjectDoesNotExist):
return {}
Just remember that if you set the same context variable in the
:class:`~django.template.context.RequestContext` constructor and in a
context processor, the latter clobbers the former.
Identifying authenticated users
-------------------------------
If you have not set the :data:`spring_metrics_email` property
explicitly, the e-mail address of an authenticated user is passed to
Spring Metrics automatically. See :ref:`identifying-visitors`.
Internal IP addresses
---------------------
Usually you do not want to track clicks from your development or
internal IP addresses. By default, if the tags detect that the client
comes from any address in the :const:`SPRING_METRICS_INTERNAL_IPS`
setting, the tracking code is commented out. It takes the value of
:const:`ANALYTICAL_INTERNAL_IPS` by default (which in turn is
:const:`INTERNAL_IPS` by default). See :ref:`identifying-visitors` for
important information about detecting the visitor IP address.
----
Thanks go to Spring Metrics for their support with the development of
this application.
|
