You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thank you for your awesome software! It's very efficient and lightweight, KISS, love it!
We use it as our main mailing tools and newsletter!
I just have an interrogation about the count of the view and the click. I understand that it's "simply" a pixel inside the mail (with the "id" of the subscriber in the url of the pixel), and if the user load it, he count as one view.
So a if a same user load it several time, it counts as several views.
But following if the Individual subscriber tracking parameters is on or off, the count of views is very different:
(We're using redash for dataviz, and redash is connected to the listmonk database).
So between the newsletter 178 and 180 we change the parameter Individual subscriber tracking to yes (or checked) and we observed a huge peak of the views (column Mails ouverts).
We know that the views are counted everytime a user load the pixel. So we have also the column Reach Users to have the tracking by users (even if a user load several times the pixel, is still count as one).
Today we decide to uncheck the Individual subscriber tracking and we retrieve our precedent view rate.
So we are not really sure about the analytics part of listmonk and we don't know if the tracking is working or not?
Our version of listmonk is 3.0.0.
You can find our request SQL here to:
SELECTcampaigns.id,
TO_CHAR(campaigns.updated_at, 'YYYY-MM-DD') AS"Date d'envoi",
TO_CHAR(campaigns.updated_at, 'Day') AS"Jour d'envoi",
TO_CHAR(campaigns.updated_at AT TIME ZONE 'UTC-1', 'HH24:MI') AS"Heure d'envoi",
CONCAT(
ROUND(
COUNT(DISTINCT views.id) *100.0/campaigns.sent,
2
),
'%'
) AS"Taux d'ouverture",
COUNT(DISTINCT clicks.id) AS"Nombre de clics",
CONCAT(
ROUND(
COUNT(DISTINCT clicks.id) *100.0/campaigns.sent,
2
),
'%'
) AS"Taux de Clic",
COUNT(DISTINCT bounces.id) as"Bounces",
campaigns.subject,
campaigns.sent,
COUNT(DISTINCT views.id) AS opened_count,
COUNT(DISTINCT views.subscriber_id) AS reached_users_count
FROM campaigns
LEFT JOIN campaign_views views ONviews.campaign_id=campaigns.idLEFT JOIN bounces ONbounces.campaign_id=campaigns.idINNER JOIN campaign_lists lists ONlists.campaign_id=campaigns.idLEFT JOIN link_clicks clicks ONcampaigns.id=clicks.campaign_idWHERElists.list_id= {{ newsletter_id }}
ANDcampaigns.updated_at BETWEEN '{{date_range.start}}'AND'{{date_range.end}}'GROUP BYcampaigns.id, campaigns.updated_atORDER BYcampaigns.updated_atDESC;
The text was updated successfully, but these errors were encountered:
Hello Dev Team.
First, thank you for your awesome software! It's very efficient and lightweight, KISS, love it!
We use it as our main mailing tools and newsletter!
I just have an interrogation about the count of the view and the click. I understand that it's "simply" a pixel inside the mail (with the "id" of the subscriber in the url of the pixel), and if the user load it, he count as one view.
So a if a same user load it several time, it counts as several views.
But following if the
Individual subscriber tracking
parameters is on or off, the count of views is very different:(We're using redash for dataviz, and redash is connected to the listmonk database).
So between the newsletter 178 and 180 we change the parameter
Individual subscriber tracking
toyes
(or checked) and we observed a huge peak of the views (columnMails ouverts
).We know that the views are counted everytime a user load the pixel. So we have also the column
Reach Users
to have the tracking by users (even if a user load several times the pixel, is still count as one).Today we decide to uncheck the
Individual subscriber tracking
and we retrieve our precedent view rate.So we are not really sure about the analytics part of listmonk and we don't know if the tracking is working or not?
Our version of listmonk is 3.0.0.
You can find our request SQL here to:
The text was updated successfully, but these errors were encountered: