Skip to main content
justin_lautenschlager
justin_lautenschlager
Contributor ⭐️⭐️
December 2, 2015
Solved

Copilot Metrics

  • December 2, 2015
  • 29 replies
  • 346 views
When I view some of the outreaches we've put together in Copilot, it seems as though we're only able to track the number of opens, clicks, bounces, etc. The way we currently track our email outreaches is by the % of unique opens, clicks, and bounces. While I could see the benefit of tracking the pure number of opens and clicks, is there no way to also track the percent of unique opens and clicks as well?
    Best answer by ben
    Hey Kelly,

    I think what you are looking for is "Opened" vs. "Opened Count". "Opened Count" in the Email Logs table is the RAW number of times the contact opened the email. This could be 0 to infinity. Meanwhile "Opened" is a numeric field that is a 0 if they have never opened the email, and a 1 if they have opened it at least once. 

    With this in mind, you can do aggregations across various groupings and use "Opened" as your unique field. You can calculate Open Rate by taking "Opened" / "Sent" for a given aggregate field.

    Hope this helps!

    29 replies

    Show previous replies
    sundar
    sundar
    Expert ⭐️
    July 29, 2016
    We are targeting this for Oct / Nov release timeframe. In the recent development of support for Relationship level outreaches we moved this further out.
    lauren_mintz
    lauren_mintz
    Helper ⭐️⭐️
    July 29, 2016
    Thank you Sundar.
    kelly
    kelly
    Helper ⭐️⭐️⭐️
    August 1, 2018
    Hi - I'm still not seeing unique metrics in the email logs reporting. Has this fallen off? Unique is a much different - and important - metric than total which can be quite skewed. 
    ben
    benAnswer
    Helper ⭐️⭐️⭐️
    August 1, 2018
    Hey Kelly,

    I think what you are looking for is "Opened" vs. "Opened Count". "Opened Count" in the Email Logs table is the RAW number of times the contact opened the email. This could be 0 to infinity. Meanwhile "Opened" is a numeric field that is a 0 if they have never opened the email, and a 1 if they have opened it at least once. 

    With this in mind, you can do aggregations across various groupings and use "Opened" as your unique field. You can calculate Open Rate by taking "Opened" / "Sent" for a given aggregate field.

    Hope this helps!
    -Ben
      kelly
      kelly
      Helper ⭐️⭐️⭐️
      August 1, 2018
      Thanks Ben, that helps
      kelly
      kelly
      Helper ⭐️⭐️⭐️
      October 21, 2018
      Another question - if I use an email in more than one Program, can I still use Email Logs to generate this reporting BY Program? I'm not seeing anything in the filtering that allows me to view these metrics by program.

      I don't use the Program Analytics because it aggregates the reporting for all emails, so I use the Email Logs. Now we are launching additional Programs to different audiences that use the same email but I want to report on them separately. How else can I get the unique open/click data for Email A in Program A and in Program B as two different reports? It's frustrating that it's this difficult to get basic email reporting honestly
      ben
      ben
      Helper ⭐️⭐️⭐️
      October 21, 2018
      Would batch name or batch ID work?
      -Ben
        kelly
        kelly
        Helper ⭐️⭐️⭐️
        October 21, 2018
        Oh batch name might do it (it's a bit confusing that batch name appears to be the same as program name but the fields aren't consistent across sources). Batch (to me) usually means group of sends, as in Monday's send would be batch 1, Tuesday's batch 2, so on and so on. The glossary definition was not the most helpful in this instance, haha.



        Thank you!
        ben
        ben
        Helper ⭐️⭐️⭐️
        October 22, 2018
        Hey Kelly. Valid points, it's not super clear. Batch name is a bit of a legacy naming convention from the old CoPilot functionality (i.e. Outreaches pre-Journey Orchestrator). 

        Hope that worked!
        -Ben
        Terms & ConditionsAccessibility statement