Gdddk

If the heap is initialized for security, then why is the stack uninitialized?

Example of a Mathematician/Physicist whose Other Publications during their PhD eclipsed their PhD Thesis

How do we know the LHC results are robust?

How to solve a differential equation with a term to a power?

How do I avoid eval and parse?

How did people program for Consoles with multiple CPUs?

Can you replace a racial trait cantrip when leveling up?

Indicator light circuit

How to count occurrences of text in a file?

Would a completely good Muggle be able to use a wand?

Is it possible to search for a directory/file combination?

Does it take more energy to get to Venus or to Mars?

Inappropriate reference requests from Journal reviewers

Why do we use the plural of movies in this phrase "We went to the movies last night."?

How to safely derail a train during transit?

Why do airplanes bank sharply to the right after air-to-air refueling?

If/When UK leaves the EU, can a future goverment conduct a referendum to join the EU?

Is it ever safe to open a suspicious html file (e.g. email attachment)?

Should I tutor a student who I know has cheated on their homework?

What is "(CFMCC)" on an ILS approach chart?

Do I need to enable Dev Hub in my PROD Org?

Why didn't Khan get resurrected in the Genesis Explosion?

What is the result of assigning to std::vector<T>::begin()?

Anatomically Correct Strange Women In Ponds Distributing Swords

Email Frequency Capping in Marketing Cloud Connect

2

I want to do the Frequency Capping to those Emails which are sent/triggered from the Marketing Cloud Connect.

I know that we can add the exclusion Script to the Journey Emails, Content Builder Emails, Automation Studio Emails and Triggered Emails to applied the Frequency Capping at the send time.

Similarly, is there any good way to add the Frequency Capping while sending emails from the Marketing Cloud Connect?

marketing-cloud email ampscript marketing-cloud-connect exclusion-script

share|improve this question

edited 17 hours ago

Dhananjay Patil

32

asked 18 hours ago

Rushikesh PanditRushikesh Pandit

1558

add a comment | 

2

I want to do the Frequency Capping to those Emails which are sent/triggered from the Marketing Cloud Connect.

I know that we can add the exclusion Script to the Journey Emails, Content Builder Emails, Automation Studio Emails and Triggered Emails to applied the Frequency Capping at the send time.

Similarly, is there any good way to add the Frequency Capping while sending emails from the Marketing Cloud Connect?

marketing-cloud email ampscript marketing-cloud-connect exclusion-script

share|improve this question

edited 17 hours ago

Dhananjay Patil

32

asked 18 hours ago

Rushikesh PanditRushikesh Pandit

1558

add a comment | 

I want to do the Frequency Capping to those Emails which are sent/triggered from the Marketing Cloud Connect.

I know that we can add the exclusion Script to the Journey Emails, Content Builder Emails, Automation Studio Emails and Triggered Emails to applied the Frequency Capping at the send time.

Similarly, is there any good way to add the Frequency Capping while sending emails from the Marketing Cloud Connect?

marketing-cloud email ampscript marketing-cloud-connect exclusion-script

share|improve this question

edited 17 hours ago

Dhananjay Patil

32

asked 18 hours ago

Rushikesh PanditRushikesh Pandit

1558

share|improve this question

edited 17 hours ago

Dhananjay Patil

32

asked 18 hours ago

Rushikesh PanditRushikesh Pandit

1558

share|improve this question

edited 17 hours ago

Dhananjay Patil

32

asked 18 hours ago

Rushikesh PanditRushikesh Pandit

1558

edited 17 hours ago

Dhananjay Patil

32

edited 17 hours ago

Dhananjay Patil

32

asked 18 hours ago

Rushikesh PanditRushikesh Pandit

1558

asked 18 hours ago

Rushikesh PanditRushikesh Pandit

1558

2 Answers
2

active

oldest

votes

3

You can create an initial Auto Suppression data extension and then use the API to add a query that targets it. (You have to use the API to create the query since you can't select the Auto Suppression data extension as the target through the interface.)

The query (or queries) could include criteria based on aggregated sends counts by subscriber as @Lukas suggested.

Automating the query his works well for account-wide frequency suppression.

share|improve this answer

edited 15 hours ago

answered 15 hours ago

Adam SpriggsAdam Spriggs

17.7k42147

add a comment | 

0

You will need to build a custom solution, where a Data Extension built on querying your _sent data view will keep track on how many emails a consumer has received over the last X days, and you then use AmpScript in your email to validate against that Data Extension whether this recipient indeed is allowed to be emailed or not. In the case where the email should not be sent, you can use RaiseError function to stop the email, but continue the job for the next subscriber.

This approach is indeed universal, and as it is not linked to a specific method, it can be utilised in triggered sends, guided sends, journeys etc.

share|improve this answer

answered 17 hours ago

Lukas LunowLukas Lunow

3,2331421

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  I would not recommend this approach as RaiseError() count as a send and should only be used for exclusion. The exclusion should be done before the send.
  
  – Jeremy Garcia
  15 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Valid point, @JeremyGarcia - thanks for bringing it up! I guess the quality of my answers is proportional to the number of days left till weekend.
  
  – Lukas Lunow
  11 hours ago
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "459"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f255821%2femail-frequency-capping-in-marketing-cloud-connect%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

3

You can create an initial Auto Suppression data extension and then use the API to add a query that targets it. (You have to use the API to create the query since you can't select the Auto Suppression data extension as the target through the interface.)

The query (or queries) could include criteria based on aggregated sends counts by subscriber as @Lukas suggested.

Automating the query his works well for account-wide frequency suppression.

share|improve this answer

edited 15 hours ago

answered 15 hours ago

Adam SpriggsAdam Spriggs

17.7k42147

add a comment | 

3

You can create an initial Auto Suppression data extension and then use the API to add a query that targets it. (You have to use the API to create the query since you can't select the Auto Suppression data extension as the target through the interface.)

The query (or queries) could include criteria based on aggregated sends counts by subscriber as @Lukas suggested.

Automating the query his works well for account-wide frequency suppression.

share|improve this answer

edited 15 hours ago

answered 15 hours ago

Adam SpriggsAdam Spriggs

17.7k42147

add a comment | 

You can create an initial Auto Suppression data extension and then use the API to add a query that targets it. (You have to use the API to create the query since you can't select the Auto Suppression data extension as the target through the interface.)

The query (or queries) could include criteria based on aggregated sends counts by subscriber as @Lukas suggested.

Automating the query his works well for account-wide frequency suppression.

share|improve this answer

edited 15 hours ago

answered 15 hours ago

Adam SpriggsAdam Spriggs

17.7k42147

share|improve this answer

edited 15 hours ago

answered 15 hours ago

Adam SpriggsAdam Spriggs

17.7k42147

answered 15 hours ago

Adam SpriggsAdam Spriggs

17.7k42147

answered 15 hours ago

Adam SpriggsAdam Spriggs

17.7k42147

0

You will need to build a custom solution, where a Data Extension built on querying your _sent data view will keep track on how many emails a consumer has received over the last X days, and you then use AmpScript in your email to validate against that Data Extension whether this recipient indeed is allowed to be emailed or not. In the case where the email should not be sent, you can use RaiseError function to stop the email, but continue the job for the next subscriber.

This approach is indeed universal, and as it is not linked to a specific method, it can be utilised in triggered sends, guided sends, journeys etc.

share|improve this answer

answered 17 hours ago

Lukas LunowLukas Lunow

3,2331421

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  I would not recommend this approach as RaiseError() count as a send and should only be used for exclusion. The exclusion should be done before the send.
  
  – Jeremy Garcia
  15 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Valid point, @JeremyGarcia - thanks for bringing it up! I guess the quality of my answers is proportional to the number of days left till weekend.
  
  – Lukas Lunow
  11 hours ago
  

  
  
  
  

add a comment | 

0

You will need to build a custom solution, where a Data Extension built on querying your _sent data view will keep track on how many emails a consumer has received over the last X days, and you then use AmpScript in your email to validate against that Data Extension whether this recipient indeed is allowed to be emailed or not. In the case where the email should not be sent, you can use RaiseError function to stop the email, but continue the job for the next subscriber.

This approach is indeed universal, and as it is not linked to a specific method, it can be utilised in triggered sends, guided sends, journeys etc.

share|improve this answer

answered 17 hours ago

Lukas LunowLukas Lunow

3,2331421

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  I would not recommend this approach as RaiseError() count as a send and should only be used for exclusion. The exclusion should be done before the send.
  
  – Jeremy Garcia
  15 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Valid point, @JeremyGarcia - thanks for bringing it up! I guess the quality of my answers is proportional to the number of days left till weekend.
  
  – Lukas Lunow
  11 hours ago
  

  
  
  
  

add a comment | 

You will need to build a custom solution, where a Data Extension built on querying your _sent data view will keep track on how many emails a consumer has received over the last X days, and you then use AmpScript in your email to validate against that Data Extension whether this recipient indeed is allowed to be emailed or not. In the case where the email should not be sent, you can use RaiseError function to stop the email, but continue the job for the next subscriber.

This approach is indeed universal, and as it is not linked to a specific method, it can be utilised in triggered sends, guided sends, journeys etc.

share|improve this answer

answered 17 hours ago

Lukas LunowLukas Lunow

3,2331421

share|improve this answer

answered 17 hours ago

Lukas LunowLukas Lunow

3,2331421

answered 17 hours ago

Lukas LunowLukas Lunow

3,2331421

answered 17 hours ago

Lukas LunowLukas Lunow

3,2331421