Cloud page Issues

Custom Un-Subscription Use Case

The most common use case is to design a html page to capture the subscriber details and honor his/her request to unsubscribe. 


FAQ:

1. How to redirect the subscriber to unsubscribe cloud page from an email link ?


%%[
SET @url=CLOUDPAGESURL(1234,'SUBSCRIBERKEY',@SUBSCRIBERKEY)
SET @type='UNSUBSCRIBE'
]%%
<a href='%%=RedirectTo(@url)=%%'>%%=v(@type)=%%</a>

Most us define personalized string for "SubscriberKey" as %%_subscriberkey%% 


2. Why  "Personalization Strings" in Email not working?

Personalization strings in email don't work because the subscriber is not yet present in All Subscriber.

3. Should we add the subscriber to All Subscriber prior to sending email communications?
It's not a mandate to add subscriber prior to sending emails. Subscribers are added to All subscribers automatically while sending emails.
The only issue is when you are using email personalization heavily in the email to make dynamic content based on subscriber profile.

4. What is the best practice to use personalization emails?
When you want to use personalization, leverage AmpScript LookUp function.

%%[SET @city =Lookup('PostalCode','City','PostalCode',46016)]%%

5. How to fetch the subscriber details in Cloud Page for updating the subscriber in All Subscriber?
Send the subscriberkey from email as a query parameter. Use RequestParameter() function to set the subscriberkey from the query parameter.

6. I was able to pass the subscriberkey to the cloud page, how to unsubscribe from All Subscriber?
<script runat="server">
  Platform.Load("Core","1.1.1");
  try{
    var prox = new Script.Util.WSProxy();
      SET @listid = RequestParameter("1050")
      var myList = List.Init(@listid);
      var subkey = RequestParameter("subkey");
      var props = [
        {
          Name: "SubscriberKey", Value: subkey }
        ,
        {
          Name: "Reason", Value: "WSProxy one click unsubscribe" }
      ];
      var data = prox.execute(props, "LogUnsubEvent");
      Write(Stringify(data));
   
  }
  catch(e){
    Write(Stringify(e));
  }
</script>



Comments

Most Viewed

CLOUD PAGE ENABLEMENT - PART 1

EMAIL NOT SENT IN JOURNEY BUILDER

CONSIDERATIONS FOR JOURNEY BUILDER

Understanding Transactional Messaging

Preference Center Demystified


Knowledge Article

Popular Posts

CLOUD PAGE ENABLEMENT - PART 1

EMAIL NOT SENT IN JOURNEY BUILDER

CONSIDERATIONS FOR JOURNEY BUILDER

Understanding Transactional Messaging

Preference Center Demystified

Journey Builder REST API Documentation

Share with Friends

Disclaimer:

The information provided on this technical blog is for general informational purposes only. As a SFMC (Salesforce Marketing Cloud) Technical Architect, I strive to offer accurate and up-to-date content related to SFMC and its associated technologies. However, please note that technology is constantly evolving, and the information provided may become outdated or inaccurate over time.

The content published on this blog represents my personal views and experiences as a SFMC Technical Architect and does not necessarily reflect the official views or opinions of any organization or employer I may be affiliated with.

While I make every effort to ensure the accuracy and reliability of the information presented, I cannot guarantee its completeness, suitability, or applicability to your specific circumstances. Therefore, it is essential to verify any information provided and make your own independent assessments or seek professional advice if needed.

Furthermore, any actions taken based on the information provided on this blog are at your own risk. I shall not be held liable for any damages, losses, or inconveniences arising from the use of the information presented here.

Please keep in mind that SFMC and its associated technologies are complex and require technical expertise for proper implementation and management. It is recommended to consult with qualified professionals or official SFMC documentation for comprehensive guidance.

Finally, please note that any product or company names mentioned on this blog are trademarks or registered trademarks of their respective owners. The mention of these trademarks or registered trademarks does not imply any endorsement or affiliation with the blog.

By accessing and using this blog, you agree to the terms of this disclaimer. If you do not agree with any part of this disclaimer, please refrain from using this blog.