CloudPagesURL Personalisation Strings
The CloudPagesURL()
function provides a secure and efficient way to link out to CloudPages from email messages.
<a href="%%=RedirectTo(CloudPagesURL(4132))=%%">Click HERE</a>
It generates a URL link to the landing page with an encrypted query string appended —meaning no subscriber information is passed in clear text.
https://pub.s10.exacttarget.com/1qVt23cf?qs=92fcbe6d03c54df75b03c7d674f2e836
This encrypted query string (?qs=______
) references the email and allows standard system personalisation strings to be used on a landing page.
When using the RedirectTo(CloudPagesURL(1234))
function, I was curious if it was required to use requestParameter
, queryParameter
, or possiblyAttributeValue()
.
In fact, it is A LOT simpler than that. As you would in an email, you can simply use the defined system personalisation strings:
SET @Subkey= _subscriberkey
Then, logically the below also works:
SET @Subkey = AttributeValue(“_subscriberkey”)
Most personalisation string are available in the CloudPages context…
If you are interest in testing this yourself: build an html table in cloudpages, set your ampscript variables, create an email with CloudPagesURL function to your test CloudPage, conduct a test send and see what values populate.
Here’s something to get you started….
%%[
SET @SubKey = _subscriberkey
SET @emailaddr = emailaddr
SET @jobid = jobid
SET @emailid = _emailid
SET @PreHeader = _PreHeader
SET @emailName = emailname_
SET @IsTestSend = _IsTestSend
SET @MID = memberid
SET @msgcontext = _messagecontext
SET @replyname = replyname
SET @replyemail = replyemailaddress
SET @SendDEname = _DataSourceName
]%%<table border=”1" cellspacing=”0" cellpadding=”1" style=”width:50%”>
<tr>
<td>SubKey:</td>
<td>%%=v(@SubKey)=%%</td>
</tr>
<tr>
<td>emailaddr:</td>
<td>%%=v(@emailaddr)=%%</td>
</tr>
<tr>
<td>jobid:</td>
<td>%%=v(@jobid)=%%</td>
</tr> etc..
etc..</table>