Session
This page provides parameter guidance for session-level common tracking examples:
In this page
Upon successful login of a user.
| Parameter | Name | Syntax | Sample Value | Notes |
|---|---|---|---|---|
wt.ev |
Event Type | $SignIn |
wt.ev=$SignIn |
- Required for Sign In within Behaviors - What does $ mean in the value for wt.ev? |
wt.dcsvid |
External Visitor Parameter* | {YOUR EXTERNAL-LEVEL IDENTIFIER} | wt.dcsvid=MYCUSTOMERID123 |
Allows Actions to work with Connections requiring person-level identification (for example, Oracle Responsys)** |
wt.email_sha256 |
SHA-256 Hashed Email Address | {SHA-256 HASHED EMAIL ADDRESS} | wt.email_sha256=588833DBA4CCAE4E7A33ADFA7F3F965073A4F3E4D05B5C2935BD642D22107247 |
Allows Actions to work with Connections requiring person-level identification (for example, Oracle Responsys)** |
*External Visitor Parameters can be set for any identifier (for example, your customer ID).
**See User-Identifiers.
Please see below for an example implementation using the Oracle CX Tag:
<script>
(function(){
// Send Data
var cxDataObject = {
"wt.ev":"$SignIn", // Required for behavior
"wt.tx_i":"132432ASP34",
"wt.email_sha256":"588833DBA4CCAE4E7A33ADFA7F3F965073A4F3E4D05B5C2935BD642D22107247",
"wt.dcsvid":"MYCUSTOMERID123"
};
// DO NOT EDIT BELOW THIS LINE - ORA.view() (you may also use ORA.click() depending on your scenario)
window.ORA = window.ORA || {productReady: []};
ORA.productReady.push(['analytics', function(cxDataObject) {return function() {return ORA.view({"data": cxDataObject})}}(cxDataObject)]);
})();
</script>
Please see below for an example implementation using the Data Collection API (why would I use this?) on a webpage (ensuring you persist the visitor ID as wt.co_f in your API calls):
<script>
(function() {
var xmlhttp = new XMLHttpRequest();
var url = "https://dc.oracleinfinity.io/v3/ACCOUNTGUID" // where ACCOUNTGUID is your account GUID
var payload = {
"static": {
"wt.co_f": "d19aabf1-f402-4854-b890-be077afa1b89" // Visitor ID : Take value of 'id' from ORA_FPC cookie
},
"events": [{
"wt.dl": "0", // Denotes Page View (or "1" for a click)
"dcsuri": document.location.pathname, // pathname
"domain": document.domain, // domain
"wt.ti": document.title, // page title
"wt.es": document.domain + document.location.pathname, // URL
"wt.ssl": (document.location.protocol === "https:") ? "1" : "0", // Secure/non-secure
"wt.ev": "$SignIn", // Required for behavior
"wt.email_sha256": "588833DBA4CCAE4E7A33ADFA7F3F965073A4F3E4D05B5C2935BD642D22107247",
"wt.dcsvid": "MYCUSTOMERID123"
}]
};
xmlhttp.onreadystatechange = function() {
if (this.readyState == 4 && this.status == 200) {
window.console.log("post was successful, response was " + this.response);
} else if (this.readyState == 4 && this.status != 200) {
window.console.log("post was not successful, response was " + this.response);
}
};
xmlhttp.open("POST", url);
xmlhttp.setRequestHeader("Content-Type", "application/json");
xmlhttp.send(JSON.stringify(payload));
})();
</script>
Upon sign out of a user.
| Parameter | Name | Syntax | Sample Value | Notes |
|---|---|---|---|---|
wt.ev |
Event Type | $SignOut |
wt.ev=$SignOut |
- Required for Sign Out within Behaviors - What does $ mean in the value for wt.ev? |
wt.dcsvid |
External Visitor Parameter* | {YOUR EXTERNAL-LEVEL IDENTIFIER} | wt.dcsvid=MYCUSTOMERID123 |
Allows Actions to work with Connections requiring person-level identification (for example, Oracle Responsys)** |
wt.email_sha256 |
SHA-256 Hashed Email Address | {SHA-256 HASHED EMAIL ADDRESS} | wt.email_sha256=588833DBA4CCAE4E7A33ADFA7F3F965073A4F3E4D05B5C2935BD642D22107247 |
Allows Actions to work with Connections requiring person-level identification (for example, Oracle Responsys)** |
*External Visitor Parameters can be set for any identifier (for example, your customer ID).
**See User-Identifiers.
Please see below for an example implementation using the Oracle CX Tag:
<script>
(function(){
// Send Data
var cxDataObject = {
"wt.ev":"$SignOut", // Required for behavior
"wt.tx_i":"132432ASP34",
"wt.email_sha256":"588833DBA4CCAE4E7A33ADFA7F3F965073A4F3E4D05B5C2935BD642D22107247",
"wt.dcsvid":"MYCUSTOMERID123"
};
// DO NOT EDIT BELOW THIS LINE - ORA.view() (you may also use ORA.click() depending on your scenario)
window.ORA = window.ORA || {productReady: []};
ORA.productReady.push(['analytics', function(cxDataObject) {return function() {return ORA.view({"data": cxDataObject})}}(cxDataObject)]);
})();
</script>
Please see below for an example implementation using the Data Collection API (why would I use this?) on a webpage (ensuring you persist the visitor ID as wt.co_f in your API calls):
<script>
(function() {
var xmlhttp = new XMLHttpRequest();
var url = "https://dc.oracleinfinity.io/v3/ACCOUNTGUID" // where ACCOUNTGUID is your account GUID
var payload = {
"static": {
"wt.co_f": "d19aabf1-f402-4854-b890-be077afa1b89" // Visitor ID : Take value of 'id' from ORA_FPC cookie
},
"events": [{
"wt.dl": "0", // Denotes Page View (or "1" for a click)
"dcsuri": document.location.pathname, // pathname
"domain": document.domain, // domain
"wt.ti": document.title, // page title
"wt.es": document.domain + document.location.pathname, // URL
"wt.ssl": (document.location.protocol === "https:") ? "1" : "0", // Secure/non-secure
"wt.ev": "$SignOut", // Required for behavior
"wt.email_sha256": "588833DBA4CCAE4E7A33ADFA7F3F965073A4F3E4D05B5C2935BD642D22107247",
"wt.dcsvid": "MYCUSTOMERID123"
}]
};
xmlhttp.onreadystatechange = function() {
if (this.readyState == 4 && this.status == 200) {
window.console.log("post was successful, response was " + this.response);
} else if (this.readyState == 4 && this.status != 200) {
window.console.log("post was not successful, response was " + this.response);
}
};
xmlhttp.open("POST", url);
xmlhttp.setRequestHeader("Content-Type", "application/json");
xmlhttp.send(JSON.stringify(payload));
})();
</script>
Yes, you can declare any parameters you like (for example, wt.mycustomparam=myvalue). Please see Parameters and Parameter Syntax.
Please see Full Parameter Reference for full definitions per parameter.
When declaring your Event Type (wt.ev), you can declare any value you want. However, when a $ sign is specified this means that this is a system-reserved value which must not be used by anything other than this purpose. For example, for wt.ev=$CompareProduct, you must not use this value for anything other than tracking comparing products.
If you do not wish to use the Oracle CX Tag on particularly sensitive pages (such as check out journeys) due to Javascript library constraints, the Data Collection API allows you to generate tracking requests to Oracle Infinity without using any externally hosted Javascript libraries.
The Data Collection API does not generate any cookies to store a persistent visitor ID between pages on your website. Assuming you are deploying Oracle Infinity through the Oracle CX Tag on your other website pages, you will need to take the visitor’s ID stored in the first-party cookie ORA_FPC and pass it in your Data Collection API requests as wt.co_f to ensure visitors are tracked with a consistent ID throughout their whole website journey.
If you are not using the Oracle CX Tag and do not have the ORA_FPC cookie available for the user, you will need to generate your own unique visitor ID to pass as wt.co_f.
For more information, please see Data Collection API.
Common Tracking Examples - Browse common tracking situations with their respective Infinity parameters..
Full Parameter Reference - View the full list of default Oracle Infinity parameter.
Oracle CX Tag - Implementation - Learn how to create tracking calls using the Oracle CX Tag.
Data Collection API - Learn how to send data into Oracle Infinity by API.
Oracle CX Mobile SDK - Behavior Tracking (Android) - Learn how to send data to Oracle Infinity using the Oracle CX Mobile SDK Infinity Module for Android.
Oracle CX Mobile SDK - Behavior Tracking (iOS) - Learn how to send data to Oracle Infinity using the Oracle CX Mobile SDK Infinity Module for iOS.