Taxi For Email
  • Getting started
    • Common Terminology and Definitions
    • Creating your first email
    • Structuring your Taxi for Email account
    • Which Account Structure Applies to You?
    • Previewing and testing your email
    • Exporting your email
  • Add-ons
    • Communication add-ons
      • Setting up the Microsoft Teams add-on
      • Setting up the Slack add-on
    • Image add-ons
      • Setting up and using the Akamai add-on
    • Translation add-ons
      • Set up details for the Transifex add-on
      • Setting up MemoQ in Taxi
      • Setting up Transifex in Taxi
      • Translation Spreadsheet add-on
      • Using MemoQ Add On in Taxi
      • Using the Transifex Add On in Taxi
      • What Version to make for Transifex Translation
  • Connectors
    • AWS S3
      • Exporting an email to AWS S3
      • Setting up the AWS S3 connector
    • Acoustic (IBM Silverpop) connector
      • Exporting an email to Acoustic (IBM Silverpop)
      • Setting up personalisation for Acoustic (IBM Silverpop)
      • Segmentation in Taxi
      • Setting up the Acoustic (IBM Silverpop) connector
      • Taxi and the Acoustic (IBM Silverpop) connector
    • Adobe Campaign connector
      • Building Taxi Email Design Systems for Adobe Campaign
      • Exporting an email to Adobe
      • Exporting to Adobe Campaign File connector
      • How Taxi for Email and Adobe Campaign connect
      • Setting up personalisation for Adobe Campaign
      • Setting up segmentation for Adobe
      • Setting up the Adobe Campaign connector
    • Amazon SES
      • Exporting an email to Amazon SES
      • Setting up the Amazon SES Connector
      • Using Dynamic Content with the Amazon SES connector
    • Blueshift Connector
      • Exporting an email to Blueshift
      • Setting up personalisation for Blueshift
      • Setting up segmentation for Blueshift
      • Setting up the Blueshift connector
      • Taxi and the Blueshift connector
    • Braze connector
      • Braze Preheaders
      • Exporting an email to Braze
      • Setting up personalisation for Braze
      • Setting up segmentation for Braze
      • Setting up the Braze connector
      • Taxi and the Braze connector
    • Campaign Monitor connector
      • Exporting an email to Campaign Monitor
      • Setting up the Campaign Monitor connector
    • Connectors
      • Connectors in Taxi
    • Dotdigital connector
      • Exporting an email to Dotdigital
      • Setting up the Dotdigital connector
    • Eloqua connector
      • Exporting an email to Eloqua
      • Setting up personalisation for Eloqua
      • Setting up segmentation for Eloqua
      • Setting up the Eloqua connector
      • Taxi and the Eloqua connector
    • Emarsys
      • Exporting an email to Emarsys
      • Setting up the Emarsys connector
    • Episerver
      • Exporting an email to Episerver Smart Campaign
      • Exporting to the Episerver Transactional connector
      • Setting up personalisation for Episerver
      • Setting up segmentation for Episerver
      • Setting up the Episerver Smart Campaign connector
      • Setting up the Episerver Transactional connector
      • Taxi and the Episerver connector
    • Epsilon connector
      • Exporting an email to Epsilon
      • Setting up the Epsilon connector
    • Google Cloud Platform (GCP)
      • Exporting an email to Google Cloud Platform (GCP)
      • Setting up personalisation for Google Cloud Connector
      • Setting up segmentation for Google Cloud Platform
      • Setting up the Google Cloud Platform (GCP) connector
      • Taxi and the Google Cloud connector
    • Hubspot Connector
      • Exporting an email to Hubspot
      • Setting up personalisation for Hubspot
      • Setting up segmentation for Hubspot
      • Setting up the Hubspot Connector
      • Taxi and the Hubspot connector
    • Iterable
      • Exporting an email to Iterable
      • Iterable Segmentation support
      • Setting up personalisation for Iterable
      • Segmentation in Taxi
      • Setting up the Iterable connector
      • Taxi and the Iterable connector
    • Klaviyo Connector
      • Exporting an email to Klaviyo
      • Setting up personalisation for Klaviyo
      • Setting up segmentation for Klaviyo
      • Setting up the Klaviyo connector
      • Taxi and the Klaviyo Connector
    • Mailchimp connector
      • Exporting an email to Mailchimp
      • Setting up the Mailchimp connector
    • Marketo Connector
      • Exporting an email to Marketo
      • Setting up personalisation for Marketo
      • Segmentation in Taxi
      • Setting up the Marketo connector
      • Taxi and the Marketo Connector
    • Omeda Connector
      • Exporting an email to Omeda
      • Setting up personalisation for Omeda
      • Setting up the Omeda connector
      • Taxi and the Omeda connector
    • Optimove
      • Exporting an email to Optimove
      • Setting up the Optimove connector
    • Oracle Responsys connector
      • Exporting an email to Oracle Responsys
      • Setting up personalisation for Responsys
      • Setting up segmentation for Responsys
      • Setting up the Oracle Responsys connector
      • Taxi and the Responsys connector
    • Pardot Connector
      • Exporting an email to Pardot
      • Setting up Pardot (Salesforce OAuth) Connector
      • Setting up segmentation for Pardot
      • Setting up the Pardot Connector
    • S3 Webex Campaign
      • Exporting an email to S3 Webex Campaign
      • Setting up personalisation for S3 Webex Campaign
      • Setting up segmentation for the S3 Webex Campaign Connector
      • Setting up the S3 Webex campaign connector
    • SAP Connector
      • Exporting an email to SAP
      • Setting up the SAP connector
    • Sailthru Connector
      • Exporting an email to Sailthru
      • Exporting an email to the Sailthru Template connector
      • Setting up personalisation for Sailthru
      • Segmentation in Taxi
      • Setting up the Sailthru Template connector
      • Setting up the Sailthru connector
      • Taxi and the Sailthru Connector
    • Salesforce Marketing Cloud connector
      • Exporting an email to Salesforce Marketing Cloud
      • SFMC Subject Line Updates
      • Salesforce Preheader
      • Setting up personalisation for Salesforce Marketing Cloud
      • Segmentation in Taxi
      • Setting up the Salesforce Marketing Cloud Exact Target connector
      • Setting up the Salesforce Marketing Cloud connector - Content Builder
      • Taxi and the Salesforce Marketing Cloud connector
    • Sendgrid Connector
      • Export all Mailings in a Project to Sendgrid
      • Exporting an email to Sendgrid Campaign Legacy
      • Exporting an email to Sendgrid Transactional
      • Exporting an email to the Sendgrid Marketing for Single Sends connector
      • Sendgrid Connector
      • Setting up personalisation for Sendgrid
      • Segmentation in Taxi
      • Setting up the Sendgrid Marketing for single sends connector
      • Setting up the Sendgrid connector
    • Sparkpost
      • Exporting an email to Sparkpost
      • Setting up the Sparkpost connector
    • Yes Marketing
      • Exporting an email to Yes Marketing
      • Setting up the Yes Marketing connector
    • Messagebird Engagement Platform
      • Setting up the Messagebird Engagement Platform (MEP) connector
      • Exporting an email to Messagebird Engagement Platform (MEP)
    • CleverTap connector
      • Setting up the CleverTap connector
      • Exporting using the CleverTap connector
  • Creating and editing an email
    • Creating and editing an email
      • Conversations in Taxi
      • Creating and exporting an email
      • Expectations in Taxi
      • How the module includer works
      • How to build an email in the editor
      • Reusable modules
      • Revision History in Taxi
      • What's new in the new Taxi for Email
  • Dynamic content, segmentation and personalisation
    • Dynamic content, segmentation and personalisation
      • Flexible Segmentation
      • Personalisation folders
    • Personalisation
      • Bulk upload Personalisation fields
      • Setting up personalisation fields
      • Using personalisation in a mailing
      • What is Personalisation
    • Segmentation
      • Creating and managing Segment Sets
      • Creating and managing Single Segments
      • Exporting Segmented Mailings - Via Connectors
      • Exporting Segmented Mailings Manually
      • Previewing Segments
      • Subject Line Segmentation
      • Using Segmentation in a mailing
      • What is Segmentation
  • Email Design Systems
    • Brands
      • Configuring Brands
      • Creating a Brand
      • Setting Brand Fields: Brands
      • What are Brands
      • What are sub-templates
    • Built-in Taxi Email Design Systems
      • Built-in Email Design Systems email client support
      • Using the Modern Standard Email Design System to create an email
    • Custom Email Design Systems
      • Custom-built Email Design System email client support
      • Understanding Email Design Systems uploader error messages
      • Updating an existing custom Email Design System
      • Uploading a custom Email Design System to Taxi
      • Uploading an Email Design System using a zip file
      • Using custom fonts in an email
    • Email Design System Owners
      • Setting up your Email Design System owner
      • Viewing your Email Design System owner in a Version
    • Email Design Systems
      • Check where your Email Design System is being used
      • Email Design System Module Statistics
      • Getting started with Taxi Email Design Systems
      • Managing your Email Design System
      • Setting Version Defaults
      • Setting a default Email Design System
      • Using built-in and custom Email Design Systems
      • What is an Email Design System Guide
      • What is an Email Design System
    • Layouts
      • How will Layouts help my team?
      • What are Layouts?
  • Email and Taxi for Email best practice
    • Dark Mode
      • Dark Mode Best Practice and Tips
      • Different Email Clients in Dark Mode
      • What is Dark Mode?
    • Email and Taxi for Email best practice
      • Adding images to your email
      • How to get Google Chrome Console Logs
      • Learn how to structure your account: Part 1
      • Learn how to structure your account: Part 2
      • Learn how to structure your account: Part 3
      • Learn how to structure your account: Part 4
      • Image saving:
      • Using ICS iCal files in Taxi
      • Using Taxi with ESP code
      • Why are my images not displaying?
      • Why is Gmail clipping my email?
  • Feeds & Link Tracking
    • Feeds
      • Extracting Data from your HTML Feed
      • Extracting the data from your feed
      • Feeds Configuration
      • Setting up a custom feed in Taxi for Email
      • Setting up a feed in Taxi for Email
      • Setting up search helpers when using feeds
      • Using Feeds in the Taxi editor
      • What is a feed
    • Fresh Relevance
      • Setting up Fresh Relevance in your Taxi for Email account
      • What is Fresh Relevance
    • Link Tracking
      • Configuring link tracking profiles
      • Creating a Tracking Profile
      • Creating a custom link tracking profile
      • Custom Attributes in Link Tracking Profiles
      • How to add Tracking Profiles to Link Groups
      • Link Groups
      • Link Tracking Manager - href settings
      • Link Tracking: Connector Types
      • Tracking Profiles and Link Groups
      • What is Link Tracking Manager
    • Liveclicker
      • Setting up the Liveclicker Integration on Taxi
      • What is Liveclicker
  • Manage Your Organisation Settings
    • CDN
      • CDN notification settings
      • Hosting images with the Taxi CDN
      • How to check your CDN usage
    • Manage Your Organisation Settings
      • Joining a company account
      • Support availability
      • Updating your profile
      • Whitelist Taxi IP Addresses
    • Security 2
      • Logging into a Taxi for Email account
      • Resetting a password
      • Setting up Enterprise Password Rules
      • Setting up and managing two-factor authentication
      • Two-factor Authentication (2FA)
  • Master Versions and Inheritance
    • Inheritance 2
      • Inheritance and managing inheritance
  • Misc
    • Misc
      • Branding Sub Templates: Setting Brand Fields
      • Can I re-add modules I've already removed?
      • Do I have to use the same template each time for my versions?
      • Exporting an email to Bronto
      • How do I build a master version from a built in or custom modular template?
      • How do I connect to Salesforce Marketing Cloud?
      • How do I create a new user in Taxi?
      • How do I download HTML documents?
      • How do I give a team the correct permissions?
      • How do I give a user full permissions?
      • How do I preview my emails so I can see how they will appear in mobile or on desktop?
      • How do I re-order the modules in my master version?
      • How do I remove modules I no longer need?
      • How do I send someone a notable link?
      • How do I structure my organisation into teams?
      • How do I view with images off using the preview pane?
      • How to Manage your Password
      • Setting up Fresh Relevance
      • Setting up personalisation for Marketo
      • Setting up the Bronto connector
      • To give a team specific permissions, follow these steps:
      • To remove Admin rights follow these steps:
      • Untitled article
      • What is the difference between an admin and a non admin user?
      • Who is responsible for setting up our Taxi account and adding new users etc.?
  • Partners
    • Partners
      • Manage your partner and sub accounts
      • Manage your partner and sub-accounts
      • What is a partner account
  • Projects, Mailings and Versions
    • Inheritance 1
      • Inheritance and managing inheritance
    • Mailing name conventions
      • Setting up mailing name conventions
      • Using mailing name conventions
    • Mailings
      • Creating and managing Mailings
    • Parent Versions and Child Versions
      • Creating and using Parent Versions
      • Synchronising content between the Parent version and other versions
    • Project Groups
      • Creating and managing Project Groups
    • Projects, Mailings and Versions
      • Understanding, Projects, Mailings and Versions
      • Using the Search function in Taxi
    • Projects
      • Creating and managing Projects
    • Version Sets
      • Creating and managing Version Sets
    • Versions
      • Creating and managing Versions
  • Setting Up Taxi
    • Setting Up Taxi
      • Setting up a Taxi for Email account
  • Support Info
    • Support Info
      • Browser support
      • Taxi and VAT
      • Taxi for Email pricing
      • Why you might not be receiving test emails from Taxi
      • Where is Taxi hosted?
  • Taxi for Email API
    • Taxi for Email API
      • API endpoints
      • Taxi for Email API
  • Testing and approving your emails
    • Testing and approving your emails
      • Connect your Litmus account to Taxi
      • Creating test email addresses
      • Exporting HTML
      • Exporting Screenshots
      • Exporting a PDF
      • Exporting a hosted URL
      • Logging out of Litmus in Taxi
      • Testing your email in Litmus
      • Using Email on Acid to test your emails
  • Users, Team Access, Permissions and Organisation Settings
    • Permissions
      • Connector Permissions
      • Email Design System Permissions
      • Personalisation Permissions
    • Security 1
      • Setting up IP Whitelisting
      • Setting up Image Domain Whitelisting
    • Teams
      • Creating and managing Teams in Taxi
      • Team Access and Permissions
      • Team and Global Permissions
    • Users, Team Access, Permissions and Organisation Settings
      • Bulk Uploading Users
      • SSO Set Up
    • Users
      • Admin & Non Admin Users
      • Creating and managing users in Taxi
      • Users access and permissions
Powered by GitBook
On this page
  • Getting started
  • Custom Fields
  • Choosing which links to track
  • Applying tracking to one set of links and not tracking other links
  • Applying different tracking to different links
  • Excluding specific links from tracking
  • Project Groups, Projects, Mailings and Versions
  • Connectors
  • Modules
  • Targeting different links within one module
  • Prepends
  • Assign
  • Capture
  • Split
  • Replace
  • Line breaks and spaces
  1. Feeds & Link Tracking
  2. Link Tracking

Link Tracking Manager - href settings

PreviousLink GroupsNextLink Tracking: Connector Types

Last updated 1 year ago

When setting up custom link tracking profiles, there is a section named 'href settings'. This is where you control exactly how links will be formatted when you export your emails from Taxi. For example, you can define all the parameters you need adding to your links, have exclusions (if some links don't need tracking) or set up rules if various links need different tracking.

Taxi enables you to use in the href settings to give you all the control you need.

This article explains the different ways you can use liquid when setting up your link tracking.

Getting started

Whatever you input into this code field will define exactly what the links look like when you export an email out of Taxi. Typically you will start off with whatever link someone inputs to a link field in a version.

To do this you use:

#{{linkfields.original_href}}

If you have only this in the href settings, and in the version you input , in the exported HTML you will have href=“

When tracking gets appended to a link a question mark is needed to separate the url from the tracking parameters. However, if the original url already contains a question mark an ampersand is needed to separate the url from the tracking.

To make sure the right character is used, include a custom filter in the original_href variable:

#{{linkfields.original_href | url_arg_prefix}}

This filter means, if the link contains ? then put a & at the end of the link, but if it doesn't contain ?, then add ? to the end of the link. It removes the need to manually add this in for every link in your emails.

Custom Fields

In link tracking profiles you can create custom fields. These are used to set variables that can be used in your link tracking, such as a hardcoded value of 'email' or something that can change, such as a campaign name. .

To use this in your links, use:

#{{linkfields.name_of_custom_field}}

If the custom field is called utm_campaign you'd reference it like this:

#{{linkfields.utm_campaign}}

You can also hard code parts of the link if they are always needed in the tracking and don't need to ever change. For example, utm_campaign= is always included, but the value is set from a custom field.

#{{linkfields.original_href | url_arg_prefix}}utm_source=#{{linkfields.utm_source}}&utm_medium=#{{linkfields.utm_medium}}&utm_campaign=#{{linkfields.utm_campaign}}

Everything inside the liquid brackets #{{ }} is a variable and everything else will always be included in the link as it is.

The above example would mean that all links would have exactly the same structure of tracking without exception, but there is a lot more control we can add using various liquid functions.

Choosing which links to track

All of your links may not need exactly the same tracking, or even tracking at all. You can target specific URLs or types of links to track or not track using if statements.

Applying tracking to one set of links and not tracking other links

Here, if the link contains taxiforemail.com, then it will have tracking applied to it, but any other link won't get tracked at all. This can be useful when you have links going to external websites that aren't relevant to the traffic to your site.

#{{linkfields.original_href | url_arg_prefix}}utm_source=#{{linkfields.utm_source}}&utm_medium=#{{linkfields.utm_medium}}&utm_campaign=#{{linkfields.utm_campaign}} #{{linkfields.original_href}}

Applying different tracking to different links

In this example, if the link in the email contains taxiforemail.com, one set of tracking parameters is used. If the link contains sparkpost.com, another set of parameters will be used. Any link that doesn't match either of these conditions will have no tracking.

#{{linkfields.original_href | url_arg_prefix}}utm_source=#{{linkfields.utm_source}}&utm_medium=#{{linkfields.utm_medium}}&utm_campaign=#{{linkfields.utm_campaign}} #{{linkfields.original_href | url_arg_prefix}}utm_source=#{{linkfields.utm_source}}&utm_medium=#{{linkfields.utm_medium}}&utm_campaign=#{{linkfields.utm_campaign}}&utm_term=#{{linkfields.utm_term}} #{{linkfields.original_href}}

Excluding specific links from tracking

Whereas the above examples enable you to target specific links to be tracked, you can also target links to not be tracked. This is often used for mailto links.

#{{linkfields.original_href}} #{{linkfields.original_href | url_arg_prefix}}utm_source=#{{linkfields.utm_source}}&utm_medium=#{{linkfields.utm_medium}}&utm_campaign=#{{linkfields.utm_campaign}}

This means if you include a mailto link in an email, this won't get tracked, but every other link will get the tracking applied.

Project Groups, Projects, Mailings and Versions

If you use specific naming conventions for these different parts of your Taxi account, and these also need to be included in your tracking, you can reference them in link tracking profiles.

Project Group - #{{project_group.name}}

Project - #{{project.name}}

Mailing - #{{mailing.name}}

Version - #{{version.name}}

These can also be used in conditional statements if tracking changes depending on what project group the email is in for example.

Newsletter Triggers

Connectors

You can also target ESP connectors in tracking profiles if you have different tracking needs for the different ESPs you use. This is often useful if you use separate ESPs for different emails, or are in the process of transitioning between two and emails could be exported to either.

There are two ways to target connectors in your account.

- Connector Type

This relates to any connector for one specific ESP. For example with this code:

You are targeting any Salesforce connector you have in your account. So anytime you export to Salesforce this tracking will be included, even if you have multiple connectors.

- Connector Name

This means you can target a specific connector by using the name you give it when creating it in your account.

In this example, only the connector you have named My Salesforce connector will get this tracking. If you have another Salesforce connector with a different name, this tracking won't get applied when using that one.

This approach is also useful when the links you send to the ESP aren't valid until the email is actually sent. For example, if there are ESP personalisation tags that break the link unless it is converted to an actual value.

Using the above if statement would mean that when exporting to the ESP the link would include all the tracking needed. If this was included when sending a test from Taxi, the link could appear broken if it needs to go through the ESP first. The ESP code is only included when using the connector so when you use this liquid rule, you can test the links in Taxi too.

Salesforce is used as an example here. This approach can be used with any ESP we have a connector with.

Modules

If part of your link tracking changes depending on which part of the email the link is in, you can target the modules of your Email Design System and have different tracking per module. For example, if you have parameters that determine whether recipients click on buttons, images or text.

Use context.module.name to do this.

The name here comes from the name of the module in the Email Design System.

If you want to target a module that is outside of a modulezone, the syntax is slightly different.

Add 'modules' before the name of the module.

Targeting different links within one module

When you click inspect element in a version in Taxi for a specific piece of content, you will notice an attribute named 'taxi-scope'. This tells you the name of an editable that this specific piece of content is in.

For example, this tells us that the image is in an editable named ‘image’:

And this tells us that some text is inside an editable called 'headline':

In the link tracking profile we can target this taxi-scope. For example:

Prepends

Most often, the first part of the liquid will be #{{linkfields.original_href}} as this is the url used in an email and it goes before any tracking.

Sometimes the url used in an email can form part of a longer url, for example when you have a different url for users opening on mobile taking them straight to an app page, not a browser.

An assign tag allows you to create new liquid variables. For example, if you had a long bit of personalisation that needed to be included multiple times in your link tracking profile. Instead of typing it out every time you could create a variable using assign and then repeat the variable instead of the long personalisation string.

#{{ID}}

Anytime you use this variable, you will be using whatever value is set in the assign.

This is similar to assign but enables you to create a variable from more complex liquid, as opposed to just a static value.

For example, let's say you want to control some of the tracking based on a module that is used. You can include the logic for this inside a capture tag to create it as a variable, and then use this variable name in your link tracking.

#{{linkfields.original_href | url_arg_prefix}}utm_source=email&utm_medium=newsletter&utm_term=#{{module}}

The variable 'module' will be using the if statement in the capture. If this is needed multiple times in your link tracking it can be easier to use this approach than repeating the full if statement.

The hashtag and everything after it needs to go at the end of the link so the browser understands this is the part of the page you need to be taken to. If you add tracking to these links the anchor will no longer be at the end so it won't work as intended.

To ensure the tracking and the achor both work we can use the split filter. This means we can 'split' the link where there is a hashtag and put the tracking before it, so the anchor will still be at the end.

#{{split_href[0] | url_arg_prefix}}TRACKING

First, we are using an assign and the strip filter to separate the url when there is a #. Then split_href[0] is referencing everything before the #, so this goes before the tracking.

##{{ split_href[1] }} means that if there is a hashtag and something after it in the original link then this will be placed after the tracking.

This filter can take something that has been typed or pasted into a link and replace it with another word or character. This can be a useful filter when it comes to avoiding some mistakes or errors in your links.

For example, if someone accidentally types a space into a link:

#{{linkfields.original_href | url_arg_prefix | replace: ' ', '' ”}}

This will replace any space with whatever is in the second pair of quotation marks, in this case nothing.

The strip filter could also be used in the above scenario.

Line breaks and spaces

If you have a complicated link tracking profile set up, it can be useful to have the liquid split onto new lines to make it easier to read. The trouble with this is that the new lines can be interpreted as a space in the links, so there could be spaces in the urls when you export from Taxi.

If you are using this approach you can use hyphens in liquid tags to stop these spaces from appearing.

…. ….

You can find the exact type of your connector in this

In your Email Design System, you can use to break up the editor into different sections so it is easier to navigate and use. For example, if you have a module with an image and some text, you could have an editable for the image and an editable for the text.

In this example, we need to go before the actual url of the webpage. You can include this before the #{{linkfields.original_href}} in the href settings section.

Anchor links are urls that enable you to be taken to a specific part of a web page. For example, would take you to the contact us section of this page.

If the original link was it would become

article
editables
https://taxi.onelink.me/Uy67?web_url=#{{linkfields.original_href}}&mobile_link=APP_LINK
https://taxi.onelink.me/Uy67?web_url=
Assign
Capture
Split
https://www.mywebsite.com#contactus
https://www.mywebsite.com#contactus
https://www.mywebsite.com?TRACKING#contactus
Replace
liquid
https://www.taxiforemail.com
https://www.taxiforemail.com”
Read more about these fields here