Specify token value on an import?

[Anonymous]

Hoping you folks can steer me in the right direction.  I'm trying to work out the most efficient way to setup and manage a training campaign.  At a high-level we will be taking a large group of contacts and splitting them up into groups, could be as high as 50 groups.  Each of these groups will be assigned to a specific training session. I'd like a single invite campaign with a dynamic registration URL, with the event id as a token value, i.e. http://eventu-rl.com?{{my.event id}}.  So I need a good method to assign this event id to the 50 different groups.  From here I'll send be sending a confirmation email as well with the unique event details.

The goal is to reduce the number of redundant campaigns while reducing the chance for human error, i.e. sending the wrong confirmation email?  How you would or how have you handled this situation?

Thanks!

[Anonymous]

Hi Tim,

How are you going to be defining the different groups? Is there certain criteria or is it random? Are these leads all already in the database?

Kim

[Anonymous]

Hi Kim, essentially random, they are being broken down just to reduce the session size. So there's no value in the db to base it on.  The leads are in the database already.

[SanfordWhiteman]

You seem to be conflating {{lead.tokens}} (fields on the Person record) and {{my.tokens}} (program/folder level variables.

If these values are unique only at the program level, set them there and import the lead into the program. Emails can reference the {{my.token}}, which will be pulled from the closest available value in the program/folder hierarchy.

[Anonymous]

Exactly, ultimately I'm looking for a solution to use a program token like a lead token.  Except that the value is the event id not stored against the lead as it's an ephemeral value.  The "problem" is I'm going to need 50 programs or more likely one program with any top-level tokens, and 50 campaigns with the event detail level tokens.  which is what I'm trying to avoid.  There may be no good way around it, but I figure if anyone knows it...

[SanfordWhiteman]

Velocity can (re)generate values based on lead fields.

But there has to be some way to consistently derive the same event ID based on the lead field(s).  For example, if you sort into one of 50 hash buckets based on a read-only lead field (well, except for merges) like Lead ID or Marketo Unique Code, you'll always be able to put the lead back into the same bucket in the future. So adding a dynamic query parameter using a Velocity script will be consistent over time.