> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/system-settings/tracking/tracking-how-to-make-tracking-stay-on-the-same-lead.md).

# Tracking - How to make tracking stay on the same lead?

In this article, we will cover how to make tracking stay on the same lead, even when they access your content from different devices.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2Fmipv92MWdSl6HiPxQaS3%2Fundraw_Mind_map_re_nlb6.png?alt=media&amp;token=65ad56a5-b412-4714-b3bd-ee713157f599" alt=""><figcaption></figcaption></figure>

### Introduction

Lead tracking is essential for understanding the behavior of your potential customers and optimizing your marketing strategies. However, ensuring that the tracking remains associated with the same lead can be a challenge, especially when the lead uses different devices to access your landing pages and forms.&#x20;

### Solutions to keep Tracking on the same Lead

**1. Ask the user to access using the same device**

One of the most effective ways to ensure consistent tracking is to ask the lead to access it using the same device, so you can associate all interactions with the same lead.

**2. Tracking via UTM**

Add UTM parameters to the URLs you send in email marketing campaigns or other communications. These parameters can help identify the lead when they click a link, regardless of the device.

{% embed url="<https://docs.sprinthub.com/topicos/configuracoes/tag-utm>" %}

**3. Automatically resolve conflicts**

You can configure areas of the system so that conflict resolution is done automatically; one example is in forms:

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2Foo1Di59qNlLQAQh8cDC0%2Fimage.png?alt=media&amp;token=0682fd97-8525-4a32-a940-e8ff2d956b91" alt=""><figcaption></figcaption></figure>