Skip to main content
Solved

Using data tables to calculate email clickthrough rate


Hi, using Data Tables for the first time and would love to get some extra pairs of eyes on my work.

Use case:

  • Every time we send an email, we fire an event called notifications:send with event properties of notificationId and notificationType
  • When a user clicks an email, we fire an event called notifications:clicked with event properties of notificationId and notificationType

I am trying to get email clickthrough rate, defined as “for each email that is sent, is it clicked within 7 days”?

I set up a conversion metric to calculate this.


Does it look like I’ve set this up correctly?

Best answer by Manabu Takeya

Hi Anita,

Thank you for reaching out to Amplitude Support. Happy to help!

Based on your use case, you seem to be on the right track. However, whether to use 'Total' or 'Unique' depends on the specific question you're trying to answer.

If you're interested in the total number of times an email was clicked, regardless of who clicked it, then 'Total' would be the appropriate measure. This counts every event instance, even if the same notification is sent multiple times to the same users or if the same user is clicking the email multiple times.

On the other hand, if you're interested in the number of unique users who clicked the email, then 'Unique' would be the appropriate measure. This counts a user only once, no matter how many times they clicked the email. However, in your case, as the hold property constant option is enabled, the same user may appear multiple times with a different notification ID. (e.g., Sent/Click - User A x notification ID=1, User A x notification ID=2)

In the context of calculating clickthrough rate, you might want to consider using 'Unique' to get a sense of how many individual users are engaging with your emails. However, 'Total' could also provide valuable insights, such as if certain users are clicking your emails multiple times.

I hope this helps! Please let me know if you have any questions.

Best regards,
Manabu


P.S. Checkout upcoming events and user meetups on our events page.
View original
Did this topic help you find an answer to your question?

2 replies

  • Author
  • New Member
  • 1 reply
  • August 8, 2024

Forgot to mention that 1 notification can be sent to many users. 

Not sure whether I should be using Total or Unique


Manabu Takeya
Team Member
Forum|alt.badge.img+1
  • Team Member
  • 3 replies
  • Answer
  • August 12, 2024
Hi Anita,

Thank you for reaching out to Amplitude Support. Happy to help!

Based on your use case, you seem to be on the right track. However, whether to use 'Total' or 'Unique' depends on the specific question you're trying to answer.

If you're interested in the total number of times an email was clicked, regardless of who clicked it, then 'Total' would be the appropriate measure. This counts every event instance, even if the same notification is sent multiple times to the same users or if the same user is clicking the email multiple times.

On the other hand, if you're interested in the number of unique users who clicked the email, then 'Unique' would be the appropriate measure. This counts a user only once, no matter how many times they clicked the email. However, in your case, as the hold property constant option is enabled, the same user may appear multiple times with a different notification ID. (e.g., Sent/Click - User A x notification ID=1, User A x notification ID=2)

In the context of calculating clickthrough rate, you might want to consider using 'Unique' to get a sense of how many individual users are engaging with your emails. However, 'Total' could also provide valuable insights, such as if certain users are clicking your emails multiple times.

I hope this helps! Please let me know if you have any questions.

Best regards,
Manabu


P.S. Checkout upcoming events and user meetups on our events page.

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings