@@ -6,8 +6,11 @@ Analyze metrics
6
6
7
7
In order to properly understand the success or failure of an email marketing campaign, it is
8
8
necessary to monitor several key metrics. The insights gained from these metrics can then be used to
9
- optimize future campaigns. Odoo's *Email Marketing * application tracks several :ref: `key metrics
10
- <email-marketing/key-metrics>`, that can be interpreted to improve future campaigns.
9
+ optimize future campaigns. Odoo's **Email Marketing ** application tracks several :ref: `key metrics
10
+ <email-marketing/view-metrics>`, that can be interpreted through :ref: `reports
11
+ <email_marketing/create_reports>` to improve future campaigns.
12
+
13
+ .. _email-marketing/view-metrics :
11
14
12
15
View metrics
13
16
============
@@ -17,84 +20,182 @@ locations.
17
20
18
21
To access the metrics for an individual mailing, navigate to :menuselection: `Email Marketing app
19
22
--> Mailings `. Locate the specific mailing in the list view, and use the column headings to view the
20
- results for that mailing. Click on one of the mailings in the list to open the record. At the top of
21
- the record, detailed metrics are displayed as smart buttons.
23
+ results for that mailing. Click on one of the mailings in the list to open the record.
24
+
25
+ At the top of the record, detailed metrics are displayed as smart buttons.
22
26
23
27
.. image :: analyze_metrics/metric-smart-buttons.png
24
28
:align: center
25
29
:alt: The smart buttons on a mass mailing, displaying the results of the message.
26
30
27
- .. tip ::
28
- Click on the smart buttons to see the recipient records for each metric.
29
-
30
- .. _email-marketing/key-metrics :
31
-
32
31
Opened rate
33
32
-----------
34
33
35
- The *Opened * rate measures the percentage of emails opened by recipients against the total number of
36
- sent emails.
34
+ The percentage of emails opened by recipients, against the total number of sent emails.
37
35
38
- A high open rate may indicate that the subject line was timely, compelling, and successfully
39
- prompted the recipients to view the message.
36
+ In cases where a reply is expected, such as cold outreach emails, high open rate may indicate the
37
+ subject line was timely, compelling, and successfully prompted the recipients to view the message.
40
38
41
- A low open rate may indicate the subject line failed to capture the recipients' interest. It could
42
- also indicate the email ended up in a spam or junk folder due to having a poor sender reputation or
43
- failing to :doc: `configure the proper DNS records <../../general/email_communication/email_domain >`.
39
+ In cases where a reply is not expected, such as promotional emails, it may indicate an issue with
40
+ the email, such as incorrect product links or coupon codes.
41
+
42
+ In cases where a reply is expected, a low open rate may indicate the subject
43
+ line failed to capture the recipients' interest or the message ended up in a spam or junk folder. It
44
+ could also indicate the email ended up in a spam or junk folder.
45
+
46
+ .. note ::
47
+ Emails that consistently land in recipient spam folders could be due to having a poor sender
48
+ reputation (i.e. high unsubscribe rate, high percentage of past emails marked as spam, etc.),
49
+ or failing to :doc: `configure the proper DNS records
50
+ <../../general/email_communication/email_domain>`.
44
51
45
52
Replied rate
46
53
------------
47
54
48
- The *Replied * rate measures the percentage of recipients who responded to the email directly against
49
- the total number of sent emails.
55
+ The percentage of recipients who responded to the email, against the total number of sent emails.
50
56
51
- A high replied rate may indicate the email resonated with recipients, prompting them to take action
52
- or provide feedback.
57
+ A high replied rate may indicate the email resonated with recipients, prompting them to take
58
+ action or provide feedback.
53
59
54
- A low replied rate may suggest that the message lacked relevance or did not contain a clear call to
55
- action.
60
+ A low replied rate may suggest the message lacked relevance or did not contain a clear
61
+ call-to- action.
56
62
57
63
Clicked rate
58
64
------------
59
65
60
- The *Clicked * through rate (CTR), measures the percentage of recipients who clicked on a link within
61
- the email against the total number of sent emails.
66
+ This represents the *Clicked through rate (CTR) *, which measures the
67
+ percentage of recipients who clicked on a link within the email, against the total number of sent
68
+ emails.
62
69
63
- A high |CTR | may indicate the email content was relevant and appropriately targeted. Recipients were
64
- motivated to click the links provided, and likely found the content engaging.
70
+ A high |CTR | may indicate the email content was relevant and appropriately targeted. Recipients
71
+ were motivated to click the links provided, and likely found the content engaging.
65
72
66
73
A low |CTR | may indicate issues with either the targeting, or the content itself. Recipients may
67
- have been unmotivated by the calls to action, if there were any, or the message itself may have been
68
- directed toward the wrong audience.
74
+ have been unmotivated by the calls-to- action, if there were any, or the message itself may have
75
+ been directed toward the wrong audience.
69
76
70
77
Received rate
71
78
-------------
72
79
73
- The * Received * rate measures the percentage of emails that were successfully delivered against the
74
- total number of sent emails.
80
+ This rate measures the percentage of emails that were ** successfully ** delivered, against the total
81
+ number of sent emails.
75
82
76
- A high received rate can indicate that the mailing list used is up to date and the sender
77
- authentication is trusted by email providers.
83
+ A high received rate can indicate the mailing list used is up-to- date, and the sender authentication
84
+ is trusted by email providers.
78
85
79
- A low received rate may indicate issues either with the mailing list used for the mailing or with
86
+ A low received rate may indicate issues, either with the mailing list used for the mailing, or with
80
87
the sender authentication. View the :ref: `email-marketing/deliverability-issues ` section for more
81
88
information.
82
89
83
90
Bounced rate
84
91
------------
85
92
86
- The * Bounced * rate measures the percentage of emails that were unsuccessfully delivered, against the
87
- total number of sent emails.
93
+ This rate measures the percentage of emails that were ** unsuccessfully ** delivered, and did not
94
+ enter a recipient's inbox, against the total number of sent emails.
88
95
89
- A high bounce rate could indicate issues either with the mailing list used for the mailing or with
96
+ A high bounce rate could indicate issues, either with the mailing list used for the mailing, or with
90
97
the sender authentication.
91
98
92
- A low bounce rate may indicate that the mailing list used is up to date and the sender
99
+ A low bounce rate may indicate that the mailing list used is up-to- date, and the sender
93
100
authentication is trusted by email providers. View the :ref: `email-marketing/deliverability-issues `
94
101
section for more information.
95
102
103
+ .. tip ::
104
+ Click on the respective smart buttons to see all the corresponding recipient records that are
105
+ attributed to each metric. When these filtered records are in view, multiple types of reports can
106
+ be run for further analysis.
107
+
108
+ .. _email_marketing/create_reports :
109
+
110
+ Create metrics reports
111
+ ======================
112
+
113
+ Individual metrics can be analyzed by creating a report. To begin, click on the smart button of the
114
+ desired metric.
115
+
116
+ Next, click the :icon: `fa-caret-down ` :guilabel: `(down arrow) ` to the right of the search bar to see
117
+ a drop-down menu of filtering and grouping parameters.
118
+
119
+ :guilabel: `Filters `, located in the left column of the search options, can be used to keep only the
120
+ results that fit the filter. For example, selecting the *Bounced * filter only shows emails
121
+ that could not be delivered.
122
+
123
+ :guilabel: `Group By `, found in the middle column, is used to organize the results into groups, and
124
+ can be used with or without filters.
125
+
126
+ .. note ::
127
+ Setting multiple :guilabel: `Group By ` options creates nested groups, according to which option
128
+ is selected first. For example, selecting :guilabel: `Sent Period `, followed by
129
+ :guilabel: `Add Custom Group --> Responsible `, in the :guilabel: `Group By ` column, sorts all
130
+ results *first * by the sent period, *then * by the team member responsible. This is a useful
131
+ metric for analyzing who on the team is sending in volume or quantity over a set time period.
132
+
133
+ This can be verified by looking at the direction, and order, of the selections in the group tile
134
+ that appears in the search bar after the selections are made.
135
+
136
+ .. example ::
137
+ A monthly newsletter has been sent out, and 6.9% of the sent emails were bounced.
138
+
139
+ .. image :: analyze_metrics/newsletter-metrics.png
140
+ :align: center
141
+ :alt: The metrics smart buttons of the newsletter.
142
+
143
+ To see what these bounced recipients have in common, the records are grouped using a custom group
144
+ targeting :guilabel: `Mailing Lists `, which groups all records by the mailing lists they are on.
145
+ The records are then filtered using a custom filter with the rule `Created on >= 07/01/2024
146
+ 00:00:00 `, to filter by when the mailing list was last checked. This filter only includes
147
+ recipients that have been created on, or after, July 1st, 2024, in the report.
148
+
149
+ .. image :: analyze_metrics/metrics-filter.png
150
+ :align: center
151
+ :alt: The custom filter creation form.
152
+
153
+ Using these configurations, it is evident that all the recipients with bounced emails were added
154
+ after the list was last checked. Looking closer at the domains, it is evident that each
155
+ recipient has a malformed email domain (i.e: @yaoo.com instead of @yahoo.com), likely due to a
156
+ manual entry error while updating the database.
157
+
158
+ .. image :: analyze_metrics/malformed-addresses.png
159
+ :align: center
160
+ :alt: A list of bounced email addresses with malformed email domains.
161
+
162
+ .. seealso ::
163
+ View :doc: `../../essentials/search ` for more information about making custom groups and
164
+ filters.
165
+
96
166
.. _email-marketing/deliverability-issues :
97
167
168
+ Mass mailing analysis
169
+ =====================
170
+
171
+ It is also possible to analyze the success between mailing campaigns by creating a *Mass Mailing
172
+ Analysis * report. To begin, navigate to :menuselection: `Email Marketing app --> Reporting --> Mass
173
+ Mailing Analysis `.
174
+
175
+ A dashboard appears displaying a bar chart containing each mailing campaign. By default,
176
+ :guilabel: `Sent ` is selected, displaying the number of sent records on the y-axis. To change the
177
+ measure, click the :guilabel: `Measures ` button, and select the desired measure from the drop-down
178
+ menu.
179
+
180
+ .. example ::
181
+ The following chart displays the number of opened emails from two different mass mailings.
182
+
183
+ In this view, it can be seen that the first mass mailing led to a higher opened rate than the
184
+ second. Because a lower opened rate can sometimes be attributed to a subject line that failed to
185
+ capture readers' attention, the subject line of each mass mailing can be a good place to begin
186
+ looking.
187
+
188
+ .. image :: analyze_metrics/mma-opened.png
189
+ :align: center
190
+ :alt: A bar chart displaying the different opened rate between two mass mailing campaigns.
191
+
192
+ Comparing the two subject lines, it is clear the newsletter's subject line was less engaging,
193
+ which may have led to the lower opened rate, when compared to the other mass mailing.
194
+
195
+ .. image :: analyze_metrics/mailing-comparison.png
196
+ :align: center
197
+ :alt: alt text
198
+
98
199
Deliverability issues
99
200
=====================
100
201
0 commit comments