email approval | Community
Skip to main content
Level 2
November 26, 2018
Question

email approval

  • November 26, 2018
  • 1 reply
  • 4539 views

Hi there,

So the company I am working for is slowly switching to Marketo from Whatcounts.  But there is a function in WhatCounts that we really need/want with Marketo. 

The process that we have going with WhatCounts is this:

-Create email assets

-Create send list

-Schedule email

-Upon scheduled send, the COO of the company and will receive a test email from Whatcounts asking him to approve or decline the test emails. Without his approval the email campaign will NOT be sent through WhatCounts.

Is there a way to do this with Marketo? I'm pretty sure there isn't but has anyone built some kind of API or anything to be able to make this work? Or does anyone have a similar process?

Hope that articulated correctly!

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

1 reply

Grace_Brebner3
Level 10
November 26, 2018

Hey Kaitlyn,

You're right that this cannot be done out of the box. While there may be API solutions to mimic this process, it's worth noting that unapproved assets cannot be referenced in smart campaigns. That means that you can't schedule an email in Marketo that isn't approved*, so your flow of schedule > approve > send is not possible in Marketo; it'd have to be approve > schedule > send.

I suspect you'll find that most people handle this with clear processes that are enforced by people and practice, not inherently enforced by the system. Personally, I have a documentation and checklist template that users have to run all programs through before activation. This includes specific sign off requirements. The responsibility lies with the user to ensure that they take accountability on this front - for both successes and failures.

You can restrict user permissions to allow only certain roles to approve/run campaigns, but I don't like that approach (I don't think many on community do) because it's inefficient, restrictive, and takes accountability away from the people who are likely using the system most.

Basically - training, processes, documentation.

*Worth noting; you can schedule an email that has an approved version and a draft version that has not been approved, because that asset is still technically approved.

Level 2
November 26, 2018

Thank you for your insight!