- Print
- DarkLight
- PDF
WT.mc_id
WT.mc_id=Campaign ID
Identifies a specific marketing campaign. Pass this query parameter to pages that you want to associate with a specific campaign. You can specify a single numeric or string value; this parameter carries only one value.
No errors are logged if you specify multiple campaigns with this parameter, but the Campaign ID string will be processed into visitor history as a single string, and be perceived by campaign attribution processes as a single campaign.
For example, if you specified: WT.mc_id=Campaign01;Campaign02;Campaign03
, the campaign value will be placed into visitor history as exactly this: Campaign01;Campaign02;Campaign03.
It will be exported back from visitor history in the parameter WT.vr.rac
, and the single campaign will appear in reports as Campaign01;Campaign02;Campaign03
. All campaign attribution, such as revenue or engagement, will be applied to the single string. Furthermore, if the same set of campaigns is specified in a different order, such as:
WT.mc_id=Campaign02;Campaign01;Campaign03
Webtrends reads it and records it as a new, separate campaign.
Webtrends Analytics Considerations
If you plan to export Webtrends Analytics report data to a SmartReport, values that are either characters or a combination of numbers and characters work best with Microsoft Excel.
If you enable Visitor History in a profile, Webtrends Analytics reads this parameter and stores it in the Visitor History database. The most recent value of this parameter is made available by Visitor History on every hit as WT.vr.rac
.
Webtrends Visitor Data Mart Considerations
Visitor Data Mart uses this parameter to identify Ad events. For more information about the parameter set used by Visitor Data Mart, see “Configuring Your Web Site to Collect Visitor Data Mart Data” in the Visitor Data Mart User’s Guide.
NWT.mc_id
replaces the WT.mc_n
and WT.mc_t
auto-configuration parameters in earlier versions of Webtrends.