Sales owners approving/Suppressing their contacts before email send | Community
Skip to main content
D
Dhanush_Ganesh1
New Participant
May 17, 2022
Question

Sales owners approving/Suppressing their contacts before email send

  • May 17, 2022
  • 1 reply
  • 1820 views

Hi all,

we currently have a process in place which is bit manual. 

 

We have sales owners who have multiple contacts under each of them. We email the sales owners 3 days prior to the original campaign launch to ask them "do they want to suppress their contacts for that particular campaign launch?." If they wish to suppress ( based on CTA click activity ), we add them to a separate list. After that we add the salesowner's email address manually into the Campaign's smart list as suppression.

 

We want the manual part ( adding sales owner's email addressess in smart campaign ) to be automated. Please share your suggestions.

 

Thanks in advance!

 

 

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

1 reply

Darshil_Shah1
Darshil_Shah1
Community Manager
May 18, 2022
If they wish to suppress ( based on CTA click activity ), we add them to a separate list. After that we add the salesowner's email address manually into the Campaign's smart list as suppression.

 

Apologies if I'm missing anything here but instead of referencing Sales Owners in the SLs, can you not reference the list to which you add people to based on Sales Owners' inputs for suppressing people in the campaign directly?

 

Also, if I'm not wrong, you say the Sales owners decide if the contacts need to suppressed or not based on the CTA activity, can you not build a flow based on the CTA, campaign, and other contact attributes (if required) to decide if the people need to be suppressed from the campaign or not directly, instead of asking sales owners? You may build a flow/method that can apply to most of the contacts, and for the outliers you can still go back to the Sales to inquire if those contacts need to be suppressed or not.

 

D
Dhanush_Ganesh1Author
New Participant
May 18, 2022

Hi @darshil_shah1 Thanks for the feedback.

Let me explain it clearly.

 

1. We email Sales Owner's to see if they want to suppress their contacts

2. In the email, we have a CTA " Do you want to Suppress?". If the sales owner's click the CTA, we add them to a separate list.

3. During the launch, we have a target audiences who will be under different Sales owners.

4.  From step 2, Sales owner's who wished to suppress their contacts will be manaully added into the smart list like this

 

 

here in the smart list, the first criteria is target audience and the second criteria is Sales owner's email address. So people in the first criteria (AND) people under the sales owners we input in the second criteria would give us the suppression that we need.

 

We want this second criteria to be automated rather than going in and updating the sales owners email addresses manually.

 

We want all of these to handled in Marketo. Any ideas would be of great help.

 

Thanks

Darshil_Shah1
Darshil_Shah1
Community Manager
May 19, 2022

Thanks for the detailed explanation! This is a little tricky as you cannot reference any tokens in the smart list and hence there isn't a way for us to reference the data stored in a pre-defined custom token/attribute that could be added in the SL instead of manually plugging in the values. An alternate work-around to automate this (off the top of my head) is - maybe you could use Marketo APIs to get the people who need to be suppressed based on the input from the sales owners, and add them to a suppression static list which can be added as a filter in the campaign to filter out people in the static list from flowing through the campaign. You can build the API pipeline that can be run to perform these operations before you launch the campaign. One downside of this approach is that it isn't very scalable as the max # of people that you can add to a static list in one call is capped at 300.

 

Terms & ConditionsAccessibility statement

Loading footer...