---
schema_version: "1"
id: 9228f2f425f8df231f33aca3f8a15f890f46338cb5a0d70d3072f17c7218070a
title: Considerations for Activity Tracking
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mktg_tracking_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mktg_tracking_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2ff8666bc200b062f304d120db283c4223b1ebe3615682eea771dd7ebf1ea718
description: Before you turn on activity tracking, review considerations, compliance details, and cookie information.
products:
  - Marketing
release: "264"
---
# Considerations for Activity Tracking

Before you turn on activity tracking, review considerations, compliance details, and cookie information.

[View supported editions](https://help.salesforce.com/s/articleView?id=mktg.mktg_editions.htm&release=264.0.0&type=5 "Marketing Cloud Next is available in Growth and Advanced editions, and requires Salesforce Enterprise or Unlimited editions. Some features are limited by edition or purchased add-on. All functionality is available in Lightning Experience only.").

## Compliance

You're responsible for complying with privacy laws and regulations applicable to your business. To protect the privacy of site visitors, use the default consent banner on landing pages and external sites. You can choose not to collect consent to track.

If you require consent to track, we don't record each visitor’s first page view because it occurs before they provide consent.

## Implementation

Landing pages are served using the Experience Cloud Sites framework. The default Marketing Landing Pages site operates behind the scenes. Don’t add content to it.

You design consent banners in Salesforce CMS. All marketing landing pages use the same consent banner. You can use different consent banners across external websites.

## Tracked Data

After you configure web tracking, these activities are tracked.

- Page views
- Form submissions
- Link clicks
- Button clicks

## Identity Stitching

Identity stitching links a visitor’s anonymous web activity to a known profile. When someone visits a tracked landing page or external site, we use tracking cookies to record their activity. Cookies store a unique identifier for each visitor but don't store personally identifying information. Interactions, such as page views and clicks, are attributed to the anonymous individual ID.

When a visitor identifies themselves by submitting a form or clicking a tracked link, identity resolution rules create a connection between the known individual, such as a lead or contact, and the anonymous visitor activity. It can take up to 24 hours to connect visitor activity to a known individual.

## Tracking Cookie Reference

On Salesforce-hosted domains, tracking cookies are set at the subdomain level such as example.my-salesforce.com. If you use a custom domain, tracking cookies are set at the root domain level.

To make sure that activity is tracked, set up your website to use first-party tracking by aligning all of your web pages and Salesforce content under your root domain. Industry standards are moving away from third-party cookie tracking, and we recommend using first-party domain alignment.

   
| Cookie Name | Duration | Classification | Details |
| --- | --- | --- | --- |
| guest\_uuid\_essential\_<15-char SiteID> | 365 days | Not required | This cookie is no longer used but is set when someone visits a landing page or tracked site. |
| \_sfid\_${domainHash} | 730 days | Not required | When someone visits a landing page, the \_sfid\_${domainHash} cookie is set and creates a unique ID for that visitor. |
| sfmc\_consent | 365 days | Required | Set when a visitor opts in or out of tracking from the consent banner. If a visitor opts in, the value is set to True, and the visitor is tracked. If the visitor opts out or ignores the consent banner, the value is set to False, and the visitor isn’t tracked. |