Tracking

_Click

Email link click events with URL, link name, and resolved link content.

Schema last reviewed 2026-06-17

Open Interactive Workspace All data views

Opens _Click in the interactive canvas with SQL Sandbox.

Fields (15)

Field Type Flags Relations Description
AccountID Number — — Parent account ID (MID).
OYBAccountID Number NULL — Child Business Unit MID that owns the row; null on parent BU queries.
JobID Number PK, FK _Job.JobID
_Sent.JobID		 Email send job ID.
ListID Number PK, FK _ListSubscribers.ListID List ID used in the send.
BatchID Number PK — Batch ID for multi-wave sends.
SubscriberID Number PK, FK _Sent.SubscriberID
_Open.SubscriberID
_Click.SubscriberID
_Bounce.SubscriberID
_Complaint.SubscriberID
_Unsubscribe.SubscriberID		 Subscriber record ID.
SubscriberKey Text(254) FK _Subscribers.SubscriberKey
_Sent.SubscriberKey
_Open.SubscriberKey
_Click.SubscriberKey
_Bounce.SubscriberKey
_Complaint.SubscriberKey
_Unsubscribe.SubscriberKey		 Subscriber key identifier.
EventDate Date IDX — Timestamp when the click occurred.
Domain Text(128) — — Domain associated with the event.
TriggererSendDefinitionObjectID Text(36) FK, NULL _Sent.TriggererSendDefinitionObjectID
_Open.TriggererSendDefinitionObjectID
_Click.TriggererSendDefinitionObjectID
_Bounce.TriggererSendDefinitionObjectID
_Unsubscribe.TriggererSendDefinitionObjectID
_Complaint.TriggererSendDefinitionObjectID
_FTAF.TriggererSendDefinitionObjectID
_SurveyResponse.TriggererSendDefinitionObjectID		 Triggered send definition object ID.
TriggeredSendCustomerKey Text(36) NULL — Triggered send customer key.
URL Text(900) NULL — Tracked URL with AMPscript placeholders.
LinkName Text(1024) NULL — Link alias from the email.
LinkContent Text NULL — Resolved link URL after personalization.
IsUnique Boolean — — Whether this is the first click for the subscriber on this job.

Example query

SELECT TOP 100
  JobID, SubscriberKey, SubscriberID, EventDate, ListID, BatchID
FROM _Click
WHERE EventDate >= DATEADD(day, -30, GETDATE())
ORDER BY EventDate DESC

Valid in Query Studio and Automation Studio Query Activities. GROUP BY is only needed for aggregates; ORDER BY is optional but recommended with TOP so rows are meaningful. Narrow date ranges on large tracking views to avoid timeouts.