0

This is a 'best practice' question:

Should we be sending a Salesforce GUID in an email? We have a button in an email to ask them for consent (to a thing). That button links to a VF Page or a Marketing cloud page (we can go either way). In either case the query string will contain the ID of the lead.

My contention is that a user could change the URL and [...klyAAE ] isn't very different to [...klYAAE] and maybe that is a record.

I get some emails from Salesforce / SFMC users and I see urls such as: http://click.e.domainname.com/?qs=07d1f922e432d9f8b76fc2ecd423c011ff2aa49fdc139daa21c87ee360df886e2b3cfc7b62180ba77a05d1afbc9d75512d7a073dfd34a5d1

So - What am I missing?

SeanGorman
  • 1,015
  • 13
  • 32

2 Answers2

2

Best practice if you were to go via the Marketing Cloud Pages track would b

  1. Pass on the subscriberkey or any identifier using the CloudPages Ampscript function
  2. On the cloud page, use the RequestParameter function to parse the identifier

If you have integrated right, then your leadid would also be your subscriber key.

gNerb
  • 9,481
  • 5
  • 25
  • 58
0xsegfault
  • 6,603
  • 2
  • 30
  • 67
  • So - My question is: should we be sending the LEADID as a parameter in the clear? My contention that it isn't good practice. – SeanGorman Jan 03 '19 at 19:39
  • 1
    You would add lead I’d using the cloud pages url function, but when you view it in browser it would be similar to the qs bit in your question – 0xsegfault Jan 03 '19 at 19:45
-1

Adam Spriggs wrote a blog post about the MicrositeURL() function, I'm pretty sure the same idea would work with the CloudPagesURL() function. This has worked great for me multiple times. Here's a link to the post:

https://sprignaturemoves.com/a-case-for-the-micrositeurl-function/

victorcorey
  • 1,808
  • 1
  • 24
  • 50