Skip to main content
K
karanhari-1
Level 7
December 14, 2018
Question

The "Email CC" option is finally here!

  • December 14, 2018
  • 2 replies
  • 11163 views

I just noticed that the option to CC in an email is finally available! Marketo recently launched this feature. Here is the URL to the product docs for Email CC​ . Just putting this information out so that its accessible to anyone who might be searching for it!

Best Always,

Karan Hari

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    December 14, 2018

    Now that you've "stickied" the feature we're going to have to actually discuss it.

    We're advising our clients not to use this feature because it's clearly destructive to analytics and subscription management . 

    It's the last nail in the coffin of click tracking, for example: now not only do you have to to consider the original recipient's mail scanner, you have to consider the CC recipient's mail scanner and the human CC recipient themselves clicking the link, which will be attributed to the original recipient.

    It also disrupts proper unsubscribes.  If the CC recipient follows an unsubscribe link and doesn't click Not You? (if that option is even available on your unsubscribe page), they will unsubscribe the original recipient.

    This doesn't mean the feature was poorly implemented, though. It's actually a perfect implementation of CC as the entire SMTP body is copied verbatim to additional envelope recipients. It's just that people probably shouldn't have been asking for "CC" because they didn't think about the consequences.

      Dan_Stevens_
      Dan_Stevens_
      Level 10
      December 17, 2018

      I found this to be a more preferred way of how this feature should work (I think you actually included the link in one of your prior posts, Sandy): https://customer.io/docs/documentation/fake-bcc.html

        Alex_Baumgarten
        Alex_Baumgarten
        Level 2
        January 2, 2019

        Could this new feature be a way to ensure an inbox or email address received at least 1 copy of every particular email?

        I asked this question in the community a few months ago at the link below, and it seemed like at the time that the BCC function was the best fit for the task. However, this resulted in of every email being sent to the inbox BCC'ed, rather than just one copy of the email.

        Would the Email CC feature be a better solution to this problem? If an email used dynamic content or tokens, will the recipient be CC'ed on each individual version or send?

        Link: How to ensure every email sent is delivered to a single email address

        SanfordWhiteman
        SanfordWhiteman
        Level 10
        January 2, 2019

        [I]t seemed like at the time that the BCC function was the best fit for [ensuring a mailbox was copied on every email].

        Would the Email CC feature be a better solution to this problem?

        No, it wouldn't.

        The only way to use CC to accomplish this would be to ensure that one (and only one) person who qualified for every send had a certain secondary email field filled in. All others in every send would have to have that field empty. Obviously, this isn't any easier to manage than the old "make sure your CC mailbox qualifies for every send" method!

        The CC feature is for a much narrower use case: to create, in essence, a group message wherein all links are owned by a single recipient. For example, sending to an executive, their assistant, and their sales owner and keeping all in the loop during a subsequent Reply-All thread. I'm not too taken with the idea because of link tracking, as you can see above.

          Alex_Baumgarten
          Alex_Baumgarten
          Level 2
          January 2, 2019

          This is how I thought the new Email CC feature worked, but I was hopeful that maybe this would help me with this request. Thank you for the clarification.

          Terms & ConditionsAccessibility statement

          Loading footer...