Hi,
First off, I'll let you know that I've tried all of the obvious
things :), and I'm looking for a "better way" to make something like
this happen in a campaign:
To edit your preferences, go to
http://mydomain.com/?e=*|EMAIL|*&id=*|MC:ID|*
The purpose of the ID is to have some measure of security when a user
clicks on a link to go to our custom email preferences page. This way,
someone can't just change the email in the URL and update someone
else's preferences. If I have the email and the ID, I can query the
MailChimp API for the email, and make sure the IDs match.
The problem I have is that I cannot get access to the MailChimp
Subscriber ID for an individual subscriber through Merge Tags. I can
get this value by querying the API and using listMemberInfo, but there
is no way to include that ID in a campaign as a merge tag so that it's
unique per email.
Now... I know that the support documents say to create your own merge
tag to create a unique id for each subscriber (http://
www.mailchimp.com/kb/article/can-i-create-a-different-link-for-each-recipient-using-the-merge-tags),
but this has a few problems. First, it assumes that I'll be manually
creating IDs for every subscriber, or that I'll be adding all
subscribers through the API. It basically assumes that I have 100%
control and knowledge of, every single subscriber that gets into the
list. But what if I put a form on FaceBook, or someone signs up
through the built-in subscription forms directly through MailChimp?
The user has now signed up through a process outside of my control.
I could set up Webhooks, and every time a subscribe happens, 1) have a
post sent to my server, 2) which will then check to see if the user
already has a unique id (because they signed up through a form on our
side using the API), and then if they don't, 3) generate one, and then
4) update the subscriber's ID at MailChimp. The problem is that's 4
steps, all across HTTP, which is prone to problems
Or... the wonderful gurus at MailChimp could add a *|MC:ID*| merge tag
and I could use it in any campaign (generated through the site, or
through the API) and I'd always know that it's right.
I hope I've done a good enough job describing what I'm after, and I
hope you'll consider adding this as a new merge tag in the near
future.
Dan