I've created a program that is triggered based on an email click, however, the link I want to track is not static. It is a dynamic field pulled from the database called "URL".
From the dropdown criteria, I see an option for "{{lead.URL:default=edit me}}", however, that didn't seem to work.
Any idea what I'm doing wrong?
Solved! Go to Solution.
This is easy. Doesn't matter if the {{Lead.URL Field}} value can be wildly different URLs, you don't need to reference the token value in the trigger. Constrain the Clicks Link in Email trigger by Link ID. Then just give the link an ID, like <A id="lead-url" href=...>.
Ah, good point. So technically you can't use the dynamic URL as a trigger directly but that's a nice workaround!
which you could also tokenize...
Sure, though it might be easier to use the name of the token as the id, like id="URL-Field".
Are you filtering for this email click within the smart list of a smart campaign? If so, you cannot use tokens in the smart lists of smart campaigns. Although I would love for this capability some day.
First, +1 on Dan Stevens the {{lead.URL field}} token is just what you'd drop in the Email copy or link value before it runs.
What does the actual URL and field URL look like here?
For example, is the base URL structure enough to trigger on?
Clicks Link In Email CONTAINS info.firm.com/XYZ.html or something? If anyone who clicks the link should go through the next campaign? Is there a routing rule based on a code?
Is the Unique URL Field contain special code that would determine routing?
Hi Gregoire,
Ok, I've changed the url in my database to not include the "http://" part, however, I still can't seem to get it to work.
My trigger is based on "Clicks Link in Email" > "Link contains" = {{lead.URL:default=edit me}}
It was working perfectly before when I was testing the trigger with static URLs (link contains = http://test.com), so I know it's not the trigger overall. It must be the criteria.
How do I specific the dynamic URL criteria in the trigger?
That's unfortunate, but thanks!
Fortunately, we do have a common element in the URL so it should work
Did you not see my answer? Much easier than having to know the URL.