Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Campaign analytics data is cutoff, but no possible explanation why. #1795

Open
dev-cb opened this issue Mar 25, 2024 · 1 comment
Open

Campaign analytics data is cutoff, but no possible explanation why. #1795

dev-cb opened this issue Mar 25, 2024 · 1 comment
Assignees
Labels
needs-investigation Potential bug. Needs investigation

Comments

@dev-cb
Copy link

dev-cb commented Mar 25, 2024

Version

  • listmonk: [eg: v3.0.0]
  • OS: [e.g. Ubuntu]

Description of the bug and steps to reproduce
Noticed that the analytics data seems incorrect:
A campaign was started and finished on the same day (March 11). Correctly stated in the campaign overview, as well as in the campaigns table in the database. But looking at the analytics (/admin/campaigns/analytics?id=15) the data starts from March 18. Changing the date range also doesn’t make a difference.

Several scheduled campaigns where running in parallel. All the same template though, but different contact lists.

Screenshots

Bildschirmfoto 2024-03-25 um 11 39 43 Bildschirmfoto 2024-03-25 um 11 35 48 Bildschirmfoto 2024-03-25 um 11 36 50
@dev-cb
Copy link
Author

dev-cb commented Mar 25, 2024

Also in the database I checked in the data tables link_clicks and campaign_views for this specifics campaign_id, and there is data (using SELECT * FROM campaign_views WHERE campaign_id = 15;):
Bildschirmfoto 2024-03-25 um 12 02 13
Bildschirmfoto 2024-03-25 um 12 03 31

@knadh knadh added the needs-investigation Potential bug. Needs investigation label Apr 1, 2024
@knadh knadh self-assigned this Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-investigation Potential bug. Needs investigation
Projects
None yet
Development

No branches or pull requests

2 participants