Skip to content

URL triggers

The URL integration in Uncanny Automator runs a recipe when someone visits a URL that carries specific parameters. It is useful for capturing visitor interactions, linking offline systems to your website, and starting recipes from unique links, with no forms, no input on the page, and no code.

The integration works for both logged-in users and anonymous visitors. The free plugin includes two triggers, and Uncanny Automator Pro adds two more that also check a parameter’s value.

What is a URL parameter?

A URL parameter is a piece of information added to the end of a URL to pass data to a website. Parameters are commonly used to track campaign performance, capture data, or trigger specific responses on a page.

URL parameters follow a “?” in the URL and use a key-value structure. For example:

https://yoursite.com/?color=blue

Here, “color” is the parameter name (the key) and “blue” is the value. To include several parameters, separate them with “&”:

https://yoursite.com/?color=blue&campaign=summer

There are two types of parameters:

  • GET parameters are added to the end of the URL and are visible to anyone who looks at the address bar. They can be bookmarked and shared, are less secure, and suit searches, filters, and campaigns.
  • POST parameters are sent behind the scenes, not in the URL, so visitors don’t see them in the address bar. They are typically used for forms, file uploads, and sensitive information such as passwords.

The URL integration’s triggers check both GET and POST parameters.

Available triggers

The free plugin provides two triggers:

  • A user visits a URL with a URL parameter set runs when a logged-in user visits a URL that includes the parameters you set in the trigger.
  • A URL with a URL parameter is visited runs for anyone, including logged-out visitors, which makes it the trigger for public pages and for campaigns shared by email or social media.

In both, you add each parameter name to look for (for example, color) under Parameters, and use Condition to choose whether Any or All of them must be present.

To match a parameter’s value as well as its name (for example, color=blue), use the Uncanny Automator Pro triggers A user visits a URL with a URL parameter set to a specific value (logged-in users) or A URL with a URL parameter set to a specific value is visited (anyone).

Available tokens

The URL triggers provide these tokens:

  • URL visited: the full URL that the user or visitor opened, including its parameters.
  • URL Parameter – [name]: one token for each parameter you add to the trigger, holding that parameter’s value from the GET or POST request. Use these to pass data through the URL into actions such as sending emails, tagging users, or updating custom fields.

Possible use cases

A few examples of what the URL triggers make possible:

  1. Link tracking and attribution: see how users and visitors arrived on your site, or which campaign brought them, by adding a unique parameter to the link (for example, ref=affiliate1). Combine this with actions such as tagging logged-in users in your CRM or tracking affiliate performance.
  2. Personalized onboarding: send a unique onboarding link (for example, one ending in invite=client123) that runs a recipe to grant access to specific content or send a welcome message when the link is visited.
  3. QR code and print campaigns: put URLs with parameters in QR codes or printed materials. When someone scans or visits one, Uncanny Automator can log the visit or run follow-up actions, even for anonymous visitors.

Best practices

  • Keep sensitive actions away from URL triggers. URLs are public and easy to share, so don’t use a URL trigger to control anything sensitive, such as granting membership access, logging users in, or starting financial transactions.
  • Limit how often the recipe can run. A URL can be visited over and over, for example by bots. If that is a concern, use the recipe’s Throttle setting to limit how many times the recipe can run in a period; see Recipe settings: times per user, total times and throttling.

Related: Recipe types: logged-in users and everyone, Managing tokens, Managing triggers

Comments (0)

Leave a Reply

Your email address will not be published. Required fields are marked *

Back To Top