Overview
Link tracking and UTM parameters show you where the traffic and engagement from your workflow communications comes from. You can now control which UTM parameters get added to links — centrally, or for specific workflows and nodes. It gives you greater control over campaign attribution and helps preserve your existing tracking strategy.
When should I configure UTM parameters?
Configure UTM parameters when you want to:
- Track traffic generated by a specific workflow or communication.
- Use different campaign attribution for different workflows or nodes.
- Maintain a consistent tracking strategy across workflows.
- Add custom tracking parameters required by your analytics or reporting system.
- Prevent tracking parameters from being added or changed unexpectedly.
Example: Use workflow-level UTMs to identify traffic from a specific campaign, and node-level UTMs when one email or SMS needs different attribution.
How it works
Which UTM parameters can I configure?
You can configure the standard parameters:
- utm_source
- utm_medium
- utm_campaign
- utm_term
You can also add custom tracking parameters beyond the standard UTM fields if your reporting or attribution strategy needs additional information.
Where can I configure UTM parameters?
| Level | Applies to | Use it when |
|---|---|---|
| Global | All workflows, by default | You want one consistent tracking approach across your communications. |
| Workflow | Links within a specific workflow | You want to associate traffic with a particular campaign, workflow, or initiative. |
| Node | An individual Email or SMS node | One specific communication needs different tracking parameters from the rest of the workflow. |
Which configuration is used?
When more than one level has a UTM configuration, Sense applies this priority:
- Node-level settings
- Workflow-level settings
- Global-level settings
Sense first checks whether the node has its own UTM configuration. If not, it checks the workflow configuration. If no workflow-level configuration exists, it falls back to the global configuration. This lets you keep a centralized default while still overriding it for specific workflows or communications when needed.