Skip to content
This repository was archived by the owner on Feb 6, 2026. It is now read-only.

Commit 051cd23

Browse files
Merge pull request #51 from ShorensteinCenter/devel
[Bugfix, N/A] Fixed relative adjective cases in FAQ and moved link in email report
2 parents d4e48ce + 0759b20 commit 051cd23

2 files changed

Lines changed: 3 additions & 3 deletions

File tree

app/templates/faq.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
<div class="row">
66
<div class="col-12">
77
<h1 class="has-bottom-margin">Frequently Asked Questions</h1>
8-
<h2 class="has-bottom-margin">Who am I being benchmarked against?</h2>
8+
<h2 class="has-bottom-margin">Whom am I being benchmarked against?</h2>
99
<p>The following is a breakdown of organizations in our database. All data is self-reported.
1010
<ul class="has-bottom-margin">
1111
<li>{{ financial_classifications['Non-Profit'] }} of organizations are non-profits, {{ financial_classifications['For-Profit'] }} are for-profits and {{ financial_classifications['B Corp'] }} are B Corps.</li>

app/templates/report-email.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@
5959
<span style="color:#a71930;font-size:22px;line-height:22px;display:inline-block;padding-left:5px;padding-bottom:10px;">Our Tips</span></td>
6060
</tr>
6161
<tr>
62-
<td>We recommend surveying these users. Who are they? What are their habits? What else do they like to read? What do they want out of an email product? What might compel them to support or contribute to your work? Then, develop a few user personas. You should use this data to target your acquisition efforts towards subscribers who are likely to be be highly engaged. Alternatively, try to figure out what separates users in this category from semi-engaged subscribers (those who open ~30-80% of your emails). Might they be better served with a different newsletter or product from your newsroom? To learn more, read the <a href="https://newsletterguide.org/?utm_source=email-benchmarking-tool&utm_medium=email#section-5-email-monetization-conversion" target=-"_blank" rel="noopener">leaky bucket analogy</a>.</td>
62+
<td>We recommend surveying these users. Who are they? What are their habits? What else do they like to read? What do they want out of an email product? What might compel them to support or contribute to your work? Then, develop a few user personas. You should use this data to target your acquisition efforts towards subscribers who are likely to be be highly engaged. Alternatively, try to figure out what separates users in this category from semi-engaged subscribers (those who open ~30-80% of your emails). Might they be better served with a different newsletter or product from your newsroom?</td>
6363
</tr>
6464
</table>
6565
<p style="text-align:center">
@@ -72,7 +72,7 @@
7272
<span style="color:#a71930;font-size:22px;line-height:22px;display:inline-block;padding-left:5px;padding-bottom:10px;">Our Tips</span></td>
7373
</tr>
7474
<tr>
75-
<td>We recommend that newsrooms routinely and manually remove inactive users from their list after sending them a re-engagement campaign. This is also called "cleaning" your list. If you have never cleaned your list, we strongly recommend that you set aside some time to do so. Then, monitor to see if and when the inactive or pending segment grows. We generally recommend a list clean twice a year (around every six months).</td>
75+
<td>We recommend that newsrooms routinely and manually remove inactive users from their list after sending them a re-engagement campaign. This is also called "cleaning" your list. If you have never cleaned your list, we strongly recommend that you set aside some time to do so. Then, monitor to see if and when the inactive or pending segment grows. We generally recommend a list clean twice a year (around every six months). To learn more, read the <a style="text-decoration:underline;color:#a71930;" href="https://newsletterguide.org/?utm_source=email-benchmarking-tool&utm_medium=email#section-5-email-monetization-conversion" target=-"_blank" rel="noopener">leaky bucket analogy</a>.</td>
7676
</tr>
7777
</table>
7878
<p style="font-family:Montserrat,Verdana,sans-serif;font-size:11px;color:#555;margin-left:auto;margin-right:auto;max-width:1200px;">Dataset average represents the mean of all lists in our dataset. &middot; We update cached data at least once every 30 days. &middot; We acknowledge the frequency with which emails are sent can affect metrics, with daily sends having lower engagement than weekly or monthly sends. We do not take this into account at the time of this analysis.<br><br>To learn more about analyzing the health of your email list using data science tools, please see our <a target="_blank" rel="noopener" href="https://shorensteincenter.org/email-analysis-research-guide/?utm_source=email-benchmarking-tool&utm_medium=email" style="text-decoration:underline;color:#a71930;">Research Guide</a> as well as our comprehensive <a target="_blank" rel="noopener" href="https://newsletterguide.org/?utm_source=email-benchmarking-tool&utm_medium=email" style="text-decoration:underline;color:#a71930;">Playbook</a> for email newsletters.<br><br>For more information on how we use and store your data, check out our <a target="_blank" rel="noopener" href="{{ url_for('privacy', _external=True) }}?utm_source=report-email&utm_medium=email" style="text-decoration:underline;color:#a71930;">Privacy Policy</a>.<br><br>If you would no longer like to hear from us, please email us at <a target="_blank" rel="noopener" href="mailto:contact@emailbenchmarking.com" style="text-decoration:underline;color:#a71930">contact@emailbenchmarking.com</a>.

0 commit comments

Comments
 (0)