By implementing v2.0 or later of the Acoustic Exchange-Google Analytics integration JavaScript, some of the more common Google Analytics identifiers and attributes mappings are available out of the box.
However, if you prefer to map identifiers and attributes on your own, you are free to do so. The common identifiers and attributes that are mapped out of the box do not interfere with your mappings. The Acoustic Exchange-Google Analytics integration JavaScript detects your mappings, and reacts accordingly.
The following table shows the identifiers that are supported out of the box.
| Identifier | Mapped value | Description |
|---|---|---|
adobecookie |
s_fid |
The value for the s_fid Adobe Analytics cookie is mapped to the adobecookie Exchange identifier. |
adobecookie |
s_vi |
The value for the s_vi Adobe Analytics cookie is mapped to the adobecookie Exchange identifier. |
googleanalyticscookie |
_ga |
The value for the _ga Google Analytics cookie is mapped to the googleanalyticscookie Exchange identifier. |
googleadscookie |
_gads |
The value for the _gads Google Ads cookie is mapped to the googleadscookie Exchange identifier. |
ECID |
spUserID |
The Campaign URL query parameter spUserID is mapped to the ECID Exchange identifier. |
ECID |
com.silverpop.iMA.uid |
com.silverpop.iMA.uid is a Campaign tracking cookie that is mapped to the ECID Exchange identifier. |
ECID |
SP_IDENTITY |
The value for the SP_IDENTITY Campaign tracking cookie is mapped to the ECID Exchange identifier. |
DAcookieId |
cmRetrieveUserID |
The value for the cmRetrieveUserID tracking cookie is mapped to the DAcookieId Exchange identifier. |
Some of attributes that are mapped out of the box offer the ability to take advantage of behavioral analytics platforms like Customer Experience Analytics or Tealeaf. For this Acoustic Exchange integration, when events from the same web or mobile session are published by multiple endpoints, they must have matching interaction IDs to appear in the same customer journey in your behavioral analytics platform. As such, if you use Customer Experience Analytics or Tealeaf, then the value of their interaction ID is mapped to the Acoustic Exchange attribute interactionId. If an Exchange interactionId is already set and an CXA or Tealeaf interaction ID is detected, the interactionId is overridden by the CXA or Tealeaf interaction ID.
The following table shows the attributes that are supported out of the box.
| Attribute | Mapped value | Description |
|---|---|---|
interactionId |
WCXSID |
The value for the WCXSID Tealeaf cookie is mapped to the interactionId Exchange attribute. |
interactionId |
TLTSID |
The value for the TLTSID Tealeaf cookie is mapped to the interactionId Exchange attribute. |
eventName |
eventCode |
If the eventName attribute is not defined for an event, then the event is automatically assigned the eventCode value for eventName attribute. |
Comments
0 comments
Article is closed for comments.