HubSpot’s workflow tooling is simple and powerful, but there’s one thing it doesn’t do out of the box.
For every qualifying person, I’ll use a workflow to send a welcome email containing a unique registration URL. I also want to send an automatic reminder after a few days if he/she doesn’t click the link.
Simple, right? Well, no.
- Even though it’s possible to see whether a user has clicked a link in a particular email, it’s not possible to build workflow triggers directly off those clicks.
- I don’t have access to the destination domain, so I can’t track visits.
- I can’t rely on CSS or HTML to identify the link.
To make this possible, I now do the following:
- Create a redirection page and link to that page instead
- Create an event that tracks any user’s visits to that URL pattern
- Create a smart list containing everyone who has experienced that event
- Use that smart list to trigger workflow unenrollment
Here’s an example.
In my new emails, I’ll create a page on my HubSpot domain called “redirect” and link to “http://myhubspotdomain.com/redirect?p1=v1”, track the visit, then redirect to “http://otherdomain.com/page?p2=v1”.
Here’s a public gist containing the template for creating this page. Create a new template with that code, then create a landing page based on that template. You’ll want a new page for every specific redirection use case so you can track clicks properly.
You can use it to redirect everyone with or without a query string. To redirect everyone to the exact same URL, fill in the “Destination URL” value.
To redirect everyone to the same URL but with different query strings, also fill in the “URL parameter in original URL” value. In the above example, this would be the letters “p1”. It will grab the attached value in the original URL (“v1” above) and re-attach it to the destination URL.
Then create an event that tracks visits to that page, like this:
Then create a smart list to keep track of everyone who has encountered that event, like this:
Finally, set the new smart list as the unenrollment trigger for the original workflow.
Questions? Holler on Twitter @superstrong