mika
August 15, 2024, 1:27pm
1
My idea is:
I think these groups of people would benefit from this idea:
Why I think they would benefit from this idea:
Are you willing to work on this idea?:
What skills and resources do you need to explore this further?@andersoneccel . Your improvements are great.
1 Like
Hi there!
In 5.0 we did introduce some more stats into the report:
mautic:5.x ← patrykgruszka:DPMMA-1436_ctor-email-report
opened 07:56AM - 12 Sep 23 UTC
<!-- ## Which branch should I use for my PR?
Assuming that:
a = current ma… jor release
b = current minor release
c = future major release
* a.x for any features and enhancements (e.g. 5.x)
* a.b for any bug fixes (e.g. 4.4, 5.1)
* c.x for any features, enhancements or bug fixes with backward compatibility breaking changes (e.g. 5.x) -->
| Q | A
| -------------------------------------- | ---
| Bug fix? (use the a.b branch) | [ N ]
| New feature/enhancement? (use the a.x branch) | [ Y ]
| Deprecations? | [ N ]
| BC breaks? (use the c.x branch) | [ N ]
| Automated tests included? | [ Y ]
| Related user documentation PR URL | mautic/mautic-documentation#...
| Related developer documentation PR URL | mautic/developer-documentation#...
| Issue(s) addressed | Fixes #...
<!--
Additionally (see https://contribute.mautic.org/contributing-to-mautic/developer/code/pull-requests#work-on-your-pull-request):
- Always add tests and ensure they pass.
- Bug fixes must be submitted against the lowest maintained branch where they apply
(lowest branches are regularly merged to upper ones so they get the fixes too.)
- Features and deprecations must be submitted against the "4.x" branch.
-->
#### Description:
This PR adds new columns to Emails reports:
- Click-through count
- Click-through rate (CTR)
- Click-to-open rate (CTOR)
<!--
Please write a short README for your feature/bugfix. This will help people understand your PR and what it aims to do. If you are fixing a bug and if there is no linked issue already, please provide steps to reproduce the issue here.
-->
#### Steps to test this PR:
<!--
This part is really important. If you want your PR to be merged, take the time to write very clear, annotated and step by step test instructions. Do not assume any previous knowledge - testers may not be developers.
-->
1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs [here](https://contribute.mautic.org/contributing-to-mautic/tester))
2. Create a new email with links and send to any segment with contacts
3. Generate some clicks (read and click links as contact)
4. Create a report with datasource **Emails** and add columns: Click-through count, Click-through rate, Click-to-open rate
5. Save & close and check if values are correct
<!--
If you have any deprecations, list them here along with the new alternative.
If you have any backwards compatibility breaks, list them here.
-->
and also on the contact profile:
mautic:5.x ← patrykgruszka:gh-lead-email-stats
opened 07:57AM - 19 Aug 22 UTC
<!-- ## Which branch should I use for my PR?
Assuming that:
a = current ma… jor release
b = current minor release
c = future major release
* a.x for any features and enhancements (e.g. 5.x)
* a.b for any bug fixes (e.g. 4.4, 5.1)
* c.x for any features, enhancements or bug fixes with backward compatibility breaking changes (e.g. 5.x) -->
| Q | A
| -------------------------------------- | ---
| Bug fix? (use the a.b branch) | [ N ]
| New feature/enhancement? (use the a.x branch) | [ N ]
| Deprecations? | [ N ]
| BC breaks? (use the c.x branch) | [ N ]
| Automated tests included? | [ Y ]
| Related user documentation PR URL | mautic/mautic-documentation#...
| Related developer documentation PR URL | mautic/developer-documentation#...
| Issue(s) addressed | Fixes #...
<!--
Additionally (see https://contribute.mautic.org/contributing-to-mautic/developer/code/pull-requests#work-on-your-pull-request):
- Always add tests and ensure they pass.
- Bug fixes must be submitted against the lowest maintained branch where they apply
(lowest branches are regularly merged to upper ones so they get the fixes too.)
- Features and deprecations must be submitted against the "4.x" branch.
-->
#### Description:
This PR adds few email channel statistics info in contact view:
- Total sent
- Open rate (OR)
- Click-through rate (CTR)
- Click-to-open rate (CTOR)
<!--
Please write a short README for your feature/bugfix. This will help people understand your PR and what it aims to do. If you are fixing a bug and if there is no linked issue already, please provide steps to reproduce the issue here.
-->
#### Steps to test this PR:
<!--
This part is really important. If you want your PR to be merged, take the time to write very clear, annotated and step by step test instructions. Do not assume any previous knowledge - testers may not be developers.
-->
1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs [here](https://contribute.mautic.org/contributing-to-mautic/tester))
2. Add new contact and send few emails to generate statistics
3. Open contact view page, statistics should be available as a new tab
<!--
If you have any deprecations, list them here along with the new alternative.
If you have any backwards compatibility breaks, list them here.
-->
<a href="https://gitpod.io/#https://github.com/mautic/mautic/pull/11406"><img src="https://gitpod.io/button/open-in-gitpod.svg"/></a>
so I think it should not be too difficult to add this in the email stats.
Here’s a few PRs you can help with testing in the meantime if you want to see more reporting/stats:
mautic:5.x ← AlanWierzchonCA:DPMMA-1444_emails_barchart_5.x
opened 11:20AM - 01 Aug 24 UTC
<!-- ## Which branch should I use for my PR?
Assuming that:
a = current ma… jor release
b = current minor release
c = future major release
* a.x for any features and enhancements (e.g. 5.x)
* a.b for any bug fixes (e.g. 4.4, 5.1)
* c.x for any features, enhancements or bug fixes with backward compatibility breaking changes (e.g. 5.x) -->
| Q | A
| -------------------------------------- | ---
| Bug fix? (use the a.b branch) | 🔴
| New feature/enhancement? (use the a.x branch) | 🟢
| Deprecations? | 🔴
| BC breaks? (use the c.x branch) | 🔴
| Automated tests included? | 🔴
| Related user documentation PR URL | mautic/user-documentation#...
| Related developer documentation PR URL | mautic/developer-documentation-new#...
| Issue(s) addressed | Fixes #...
<!--
Additionally (see https://contribute.mautic.org/contributing-to-mautic/developer/code/pull-requests#work-on-your-pull-request):
- Always add tests and ensure they pass.
- Bug fixes must be submitted against the lowest maintained branch where they apply
(lowest branches are regularly merged to upper ones so they get the fixes too.)
- Features and deprecations must be submitted against the "4.x" branch.
-->
## Description
Adding a bar chart to the raport with e-mail data: sent, read, bounced, unsubscribed.
<!--
Please write a short README for your feature/bugfix. This will help people understand your PR and what it aims to do. If you are fixing a bug and if there is no linked issue already, please provide steps to reproduce the issue here.
-->
<!--
| Before | After
| -------------------------------------- | ---
| |
-->
---
### 📋 Steps to test this PR:
<!--
This part is crucial. Take the time to write very clear, annotated and step by step test instructions, because testers may not be developers.
-->
1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs [here](https://contribute.mautic.org/contributing-to-mautic/tester))
2. Create and send several emails
3. Open and Read sent emails
4. Create a report with data source emails, and Graph Read / Ignored / Unsubscribed / Bounced (Bar chart)
5. Check the results
<!--
If you have any deprecations and backwards compatibility breaks, list them here along with the new alternative.
-->
mautic:5.x ← annamunk:DPMMA-1660_lead_email_best_hours
opened 09:32AM - 01 Aug 23 UTC
<!-- ## Which branch should I use for my PR?
Assuming that:
a = current ma… jor release
b = current minor release
c = future major release
* a.x for any features and enhancements (e.g. 5.x)
* a.b for any bug fixes (e.g. 4.4, 5.1)
* c.x for any features, enhancements or bug fixes with backward compatibility breaking changes (e.g. 5.x) -->
| Q | A
| -------------------------------------- | ---
| Bug fix? (use the a.b branch) | [❌]
| New feature/enhancement? (use the a.x branch) | [✅]
| Deprecations? | [❌]
| BC breaks? (use the c.x branch) | [❌]
| Automated tests included? | [✅]
| Related user documentation PR URL | mautic/mautic-documentation#...
| Related developer documentation PR URL | mautic/developer-documentation#...
| Issue(s) addressed | Fixes #...
<!--
Additionally (see https://contribute.mautic.org/contributing-to-mautic/developer/code/pull-requests#work-on-your-pull-request):
- Always add tests and ensure they pass.
- Bug fixes must be submitted against the lowest maintained branch where they apply
(lowest branches are regularly merged to upper ones so they get the fixes too.)
- Features and deprecations must be submitted against the "4.x" branch.
-->
#### Description:
Charts with email activity in contact view (s/contacts/view/{id})
The charts show the contact's reading and clicking time preferences
#### Steps to test this PR:
<!--
This part is really important. If you want your PR to be merged, take the time to write very clear, annotated and step by step test instructions. Do not assume any previous knowledge - testers may not be developers.
-->
1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs [here](https://contribute.mautic.org/contributing-to-mautic/tester))
2. Create one or more emails and send them to a contact.
3. Generate email opens and clicks from one contact, preferably at different times of the day and on different days.
4. Open contact view and check that the charts in "Best email time" tab show the correct data.
<!--
If you have any deprecations, list them here along with the new alternative.
If you have any backwards compatibility breaks, list them here.
-->
mautic:5.x ← annamunk:DPMMA-2341_country_stats_table
opened 06:12PM - 27 Dec 23 UTC
<!-- ## Which branch should I use for my PR?
Assuming that:
a = current ma… jor release
b = current minor release
c = future major release
* a.x for any features and enhancements (e.g. 5.x)
* a.b for any bug fixes (e.g. 4.4, 5.1)
* c.x for any features, enhancements or bug fixes with backward compatibility breaking changes (e.g. 5.x) -->
| Q | A
| -------------------------------------- | ---
| Bug fix? (use the a.b branch) | [❌]
| New feature/enhancement? (use the a.x branch) | [✅]
| Deprecations? | [❌]
| BC breaks? (use the c.x branch) | [❌]
| Automated tests included? | [✅]
| Related user documentation PR URL | mautic/mautic-documentation#...
| Related developer documentation PR URL | mautic/developer-documentation#...
| Issue(s) addressed | Fixes #...
<!--
Additionally (see https://contribute.mautic.org/contributing-to-mautic/developer/code/pull-requests#work-on-your-pull-request):
- Always add tests and ensure they pass.
- Bug fixes must be submitted against the lowest maintained branch where they apply
(lowest branches are regularly merged to upper ones so they get the fixes too.)
- Features and deprecations must be submitted against the "4.x" branch.
-->
#### Description:
<!--
Please write a short README for your feature/bugfix. This will help people understand your PR and what it aims to do. If you are fixing a bug and if there is no linked issue already, please provide steps to reproduce the issue here.
-->
This PR adds email/contacts stats to tables in email and campaign views and allows data export. It aligns with the values shown on the map in https://github.com/mautic/mautic/pull/12570
Email campaign (/s/campaigns/view/{campaign_id})
Campaign without sending emails (/s/campaigns/view/{campaign_id})
Email (s/emails/view/{email_id})
#### Steps to test this PR:
<!--
This part is really important. If you want your PR to be merged, take the time to write very clear, annotated and step by step test instructions. Do not assume any previous knowledge - testers may not be developers.
-->
1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs [here](https://contribute.mautic.org/contributing-to-mautic/tester))
2. Create at least one email. Send it to several contacts (preferably with a non-empty country field), then open and click on the link of at least one of messages.
3. Email statistics should be correctly displayed in the e-mail view (s/emails/view/{email_id}) "Countries" tab.
4. Create and run a test campaign with at least one "email.send" event.
5. Simulate reads and clicks on messages sent from the campaign.
6. Statistics from all emails sent from the campaign should be displayed in campaign preview (/s/campaigns/view/{campaign_id}) in "Countries" tab.
<!--
If you have any deprecations, list them here along with the new alternative.
If you have any backwards compatibility breaks, list them here.
-->
There’s instructions for testing at https://mau.tc/tester
1 Like
