> For the complete documentation index, see [llms.txt](https://help.leadboxer.com/leadboxer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.leadboxer.com/leadboxer/capture-website-and-email/email/individual-emails/linkedin-inmail-or-invite-link-tracking.md).
# Linkedin InMail or Invite Link Tracking
In this document, we provide an overview or Best Practices on how to track link clicks within your InMail or automated invite campaigns. This will (also) allow you to identify leads who click through to your site, so that you can see what articles and content interest them. This is a type of qualifying behaviour we use to identify Buyer Intent.
The problem to overcome is that LinkedIn does not allow you to (visually) link a piece of text, meaning the full URL will be visible in the InMail or Invite.
The goal is to track the links. Obviously however, your leads are less likely to click a link if they see you are tracking them. So we developed 2 options for a workaround:
1. Add an innocent looking parameter to the url and identify the person on the site manually after they clicked.
2. Use a URL shortener such as bit.ly to mask the full URL and tracking parameters (this will not work for automated campaigns)
#### 1. Manual identification using a URL parameter
In most cases, this is the best option.\
Let's assume you have a list of the high-value target contacts that you are going to automatically send invites or InMails to, and you have selected a tool that can customise the message with custom variables.
Here are the steps:
1. Modify your list of recipients you want to contact via InMail or invite and add a column with an ID.\
This ID can be anything, in this example we simply choose to use a number.
2. Upload the list to the automation tool you have chosen and make sure the ID is added as a custom field in your audience list
3. Compose your InMail or Invite message, add your website link and append the link with a parameter that includes the ID.
**Example:**\
[https://www.leadboxer.com?ref=23](https://www.leadboxer.com/?ref=23)
4. Send out your campaign (ALWAYS good practice to test)
5. next, in LeadBoxer, create (and save) a new Segment by filtering for the leads that visited a URL with this parameter (see screenshot)
6. When leads show up, you can manually update the anonymous lead by adding their name, email, and role, by looking them up in your spreadsheet.
7. **Cool! you can now see who is actually interested and engaging with your invite or InMail and all their subsequent visits and pageviews**
8. If they subsequently return to your site, we will identify them again automatically and build up the leadscore to qualify
**Note:**\
Make sure our tracking pixel is installed on your website or the landing page!
***
#### 2. Automatic identification using a link shortener
Another option is to use the automatic identification using the default parameters.
* Compose the links like this:\
* Use a link shortener to mask the url and paste that in to your mail
* LeadBoxer will automatically pickup the values of these parameters and update the leads
* NOTE: some email systems will then display a message saying something like: Malicious emails can use shortened links, etc. In other words, recipients will have to click 'Proceed'.
Still need help? [Contact us](mailto:hello@leadboxer.com)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.leadboxer.com/leadboxer/capture-website-and-email/email/individual-emails/linkedin-inmail-or-invite-link-tracking.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
