Email Frequency Capping in Marketing Cloud Connect
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
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
edited Mar 29 at 10:54
Dhananjay Patil
32
asked Mar 29 at 10:25
Rushikesh PanditRushikesh Pandit
1729
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
edited Mar 29 at 10:54
Dhananjay Patil
32
asked Mar 29 at 10:25
Rushikesh PanditRushikesh Pandit
1729
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
edited Mar 29 at 10:54
Dhananjay Patil
32
asked Mar 29 at 10:25
Rushikesh PanditRushikesh Pandit
1729
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
marketing-cloud email ampscript marketing-cloud-connect exclusion-script
edited Mar 29 at 10:54
Dhananjay Patil
32
asked Mar 29 at 10:25
Rushikesh PanditRushikesh Pandit
1729
edited Mar 29 at 10:54
Dhananjay Patil
32
asked Mar 29 at 10:25
Rushikesh PanditRushikesh Pandit
1729
edited Mar 29 at 10:54
Dhananjay Patil
32
edited Mar 29 at 10:54
Dhananjay Patil
32
edited Mar 29 at 10:54
Dhananjay Patil
32
32
asked Mar 29 at 10:25
Rushikesh PanditRushikesh Pandit
1729
asked Mar 29 at 10:25
Rushikesh PanditRushikesh Pandit
1729
asked Mar 29 at 10:25
Rushikesh PanditRushikesh Pandit
1729
1729
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
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.
answered Mar 29 at 13:33
Adam SpriggsAdam Spriggs
17.8k42147
Hey, @Adam thanks for your time and response, okay I'll check using the API.
– Rushikesh Pandit
Apr 1 at 6:25
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.
answered Mar 29 at 11:34
Lukas LunowLukas Lunow
3,4082421
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
Mar 29 at 12:51
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
Mar 29 at 17:00
Thank you @Lukas for your time and response.
– Rushikesh Pandit
Apr 1 at 6:22
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
});
}
});
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
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
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
answered Mar 29 at 13:33
Adam SpriggsAdam Spriggs
17.8k42147
Hey, @Adam thanks for your time and response, okay I'll check using the API.
– Rushikesh Pandit
Apr 1 at 6:25
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.
answered Mar 29 at 13:33
Adam SpriggsAdam Spriggs
17.8k42147
Hey, @Adam thanks for your time and response, okay I'll check using the API.
– Rushikesh Pandit
Apr 1 at 6:25
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.
answered Mar 29 at 13:33
Adam SpriggsAdam Spriggs
17.8k42147
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.
answered Mar 29 at 13:33
Adam SpriggsAdam Spriggs
17.8k42147
edited Mar 29 at 13:39
answered Mar 29 at 13:33
Adam SpriggsAdam Spriggs
17.8k42147
answered Mar 29 at 13:33
Adam SpriggsAdam Spriggs
17.8k42147
answered Mar 29 at 13:33
Adam SpriggsAdam Spriggs
17.8k42147
17.8k42147
Hey, @Adam thanks for your time and response, okay I'll check using the API.
– Rushikesh Pandit
Apr 1 at 6:25
add a comment |
Hey, @Adam thanks for your time and response, okay I'll check using the API.
– Rushikesh Pandit
Apr 1 at 6:25
Hey, @Adam thanks for your time and response, okay I'll check using the API.
– Rushikesh Pandit
Apr 1 at 6:25
Hey, @Adam thanks for your time and response, okay I'll check using the API.
– Rushikesh Pandit
Apr 1 at 6:25
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.
answered Mar 29 at 11:34
Lukas LunowLukas Lunow
3,4082421
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
Mar 29 at 12:51
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
Mar 29 at 17:00
Thank you @Lukas for your time and response.
– Rushikesh Pandit
Apr 1 at 6:22
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.
answered Mar 29 at 11:34
Lukas LunowLukas Lunow
3,4082421
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
Mar 29 at 12:51
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
Mar 29 at 17:00
Thank you @Lukas for your time and response.
– Rushikesh Pandit
Apr 1 at 6:22
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.
answered Mar 29 at 11:34
Lukas LunowLukas Lunow
3,4082421
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.
answered Mar 29 at 11:34
Lukas LunowLukas Lunow
3,4082421
answered Mar 29 at 11:34
Lukas LunowLukas Lunow
3,4082421
answered Mar 29 at 11:34
Lukas LunowLukas Lunow
3,4082421
answered Mar 29 at 11:34
Lukas LunowLukas Lunow
3,4082421
3,4082421
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
Mar 29 at 12:51
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
Mar 29 at 17:00
Thank you @Lukas for your time and response.
– Rushikesh Pandit
Apr 1 at 6:22
add a comment |
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
Mar 29 at 12:51
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
Mar 29 at 17:00
Thank you @Lukas for your time and response.
– Rushikesh Pandit
Apr 1 at 6:22
4
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
Mar 29 at 12:51
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
Mar 29 at 12:51
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
Mar 29 at 17:00
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
Mar 29 at 17:00
Thank you @Lukas for your time and response.
– Rushikesh Pandit
Apr 1 at 6:22
Thank you @Lukas for your time and response.
– Rushikesh Pandit
Apr 1 at 6:22
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
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
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
