Alias Mapping Tables

You receive logical alias keys in contextData and should use Processing Rules to map these to your own eVars/props or merchandising dimensions.

The placeholders below (e.g., eVar{X}, prop{Y}) should be replaced per your availability.

Alias (contextData key)	Meaning / Use Case	Suggested Adobe Target (placeholder)	Friendly Label Example
lsc.clockDriftInMs	Clock skew diagnostics	prop{CLOCK_DRIFT}	Clock Drift (ms)
lsc.eventDate	Client-side timestamp (for sync/diagnostics)	prop{EVENT_DATE}	Client Event Date
lsc.eventId	Unique event instance for dedupe/debug	prop{EVENT_ID} (optionally eVar)	LiSA Event ID
lsc.eventType	Semantic kind of event (used for segmentation/funnels)	eVar{EVENT_TYPE}	Event Type
lsc.locale	Visitor-level segmentation	eVar{LOCALE}	Locale
lsc.mediaItemId	Media content being interacted with	eVar{MEDIA_ITEM_ID}	Media Item ID
lsc.mediaItemType	'live', 'replay' or 'story'	eVar{MEDIA_TYPE}	Media Item Type
lsc.progress.currentTimeInMs	Playback position	prop{CURRENT_TIME_MS}	Current Time (ms)
lsc.progress.durationInMs	Total duration	prop{DURATION_MS}	Duration (ms)
lsc.progress.elapsedTimeInMs	Watch engagement	prop{ELAPSED_TIME_MS}	Elapsed Watch Time (ms)
lsc.progress.isLive	Underlying stream live state	eVar{IS_LIVE}	Is Live
lsc.progress.isPlaying	Playback active state	prop{IS_PLAYING}	Is Playing
lsc.storeRef	Filtering / cross-store comparison.	eVar{STORE_REF}	Region or Store
lsc.visitorExternalId	Your visitor/user identifier	prop{VISITOR_EXTERNAL_ID}	Visitor External ID
lsc.visitorId	LiSA visitor identifier (persistent per user)	eVar{VISITOR_ID}	Visitor ID
lsc.visitorSessionId	Session-scoped identifier	eVar{SESSION_ID}	Visitor Session ID

You should create Processing Rules such as:

• If contextData key lisa.visitorId exists → Set eVar{VISITOR_ID} = value of lisa.visitorId (label “LiSA Visitor ID”).

• If contextData key lisa.eventType exists → Set eVar{EVENT_TYPE} = value of lisa.eventType.

See Adobe’s documentation on mapping contextData to props/eVars via Processing Rules.