_SocialNetworkTracking
Social Forward tracking events with subscriber-level engagement keys.
Schema last reviewed 2026-06-17
Opens _SocialNetworkTracking in the interactive canvas with SQL Sandbox.
Social Forward tracking events with subscriber-level engagement keys.
Schema last reviewed 2026-06-17
Opens _SocialNetworkTracking in the interactive canvas with SQL Sandbox.
| Field | Type | Flags | Relations | Description |
|---|---|---|---|---|
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. |
ListID |
Number | PK, FK | _ListSubscribers.ListID | List ID used in the send. |
BatchID |
Number | PK | — | Batch ID. |
SocialSharingSiteID |
Number | — | — | Social network ID. |
SiteName |
Text | — | — | Social network name. |
CountryCode |
Text(10) | — | — | Social network country code. |
PublishedSocialContentID |
Text | — | — | Published content area ID. |
RegionTitle |
Text | — | — | Social Forward region title. |
RegionDescription |
Text | NULL | — | Region description. |
RegionHTML |
Text | NULL | — | Region HTML. |
ContentRegionID |
Text | NULL | — | Content region ID. |
OYBMemberID |
Number | NULL | — | On-Your-Behalf account ID. |
TransactionTime |
Date | — | — | Time the content was shared. |
IsUnique |
Boolean | — | — | Whether the event is unique. |
Domain |
Text | — | — | Domain from which content was shared. |
PublishedSocialContentStatusID |
Text | — | — | Published content status ID. |
ShortCode |
Text | — | — | Published content short code. |
PublishTime |
Date | — | — | Time the social content was published. |
SELECT TOP 100
SubscriberKey, SubscriberID, ListID, BatchID, SocialSharingSiteID, SiteName
FROM _SocialNetworkTracking
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.