Blocklist Tag Plugin
The blocklist tag plugin helps you to configure whitelists and blacklists to include or exclude parameters that are sent to Oracle Infinity data collectors by the Oracle Infinity Tag. This helps to ensure that known PII or sensitive information is not accidentally sent.
If you use this plugin to specify a whitelist, only its specified parameters are included in data sent to Oracle Infinity. All other parameters will be removed.
If you use this plugin to specify a blacklist, only its specified parameters are excluded from data sent to Oracle Infinity. All other parameters will be allowed.
To enable the blocklist tag plugin, specify the blocklist option.
Important: When you enable this plugin, all parameters sent by the Oracle Infinity Tag are expressed as lower case values.
Options
blocklist
To enable the blocklist tag plugin, specify blocklist and blockCollect as follows:
blocklist: {'enable':true,'blockCollect':true}
You can specify additional supported options as needed:
blocklist: {'enable':true,'blockCollect':true, 'option1':true,..., 'optionN':true}
The default whitelist is enabled by default if the blocklist option is enabled—unless the blacklist option is specified.
blockCollect (required)
blockCollect forces the Oracle Infinity Tag to wait until the blocklist plugin loads data collection can begin. This option must be included with all other blocklist plugin expressions.
blacklist
You can use the blacklist option to specify a comma-delimited string of parameters that you want to exclude from the data collected by the Oracle Infinity Tag as shown in the following example:
blocklist: {'enable':true,'blockCollect':true,'blacklist':['parameter1',...,'parameterN']}
Important: If you specify the blacklist option, the default whitelist is automatically disabled.
commerce
Setting the commerce option to true enables the commerce whitelist in addition to the default whitelist, as shown in the following example.
blocklist: {'enable':true,'blockCollect':true,'commerce':true}
video
Setting the video option to true enables the video whitelist in addition to the default whitelist, as shown in the following example.
blocklist: {'enable':true,'blockCollect':true,'video':true}
whitelist
You can use the whitelist option to specify a comma-delimited string of parameters to be added to the default whitelist as shown in the following example:
whitelist: {'enable':true,'blockCollect':true,'whitelist':['wt.cg_n','wt.cg_s','wt.test','id']}
Default whitelists
commerceList = [
'wt.pn_sku',
'wt.tx_e',
'wt.tx_s',
'wt.tx_u',
'wt.tx_cartid',
'wt.tx_i',
'wt.tx_id',
'wt.tx_it',
'wt.pn_id',
'wt.pn',
'wt_tx_t'
];
videoList = [
'clip_n',
'clip_id',
'clip_secs',
'clip_mins',
'clip_ct',
'clip_perc',
'clip_ev',
'clip_duration',
'clip_t',
'clip_player',
'clip_provider',
'clip_vol',
'clip_res',
'clip_player_res',
'clip_duration_n',
'clip_tv',
'clip_mode',
'clip_screen'
]
whiteList = [
// page-related
'dcssip',
'dcsuri',
'dcsipa',
'wt.ti',
// browser-related
'wt.bh',
'wt.dl',
'wt.tz',
'wt.ul',
'wt.sr',
'wt.ce',
'wt.tv',
'wt.ct',
'wt.bs',
'wt.jo',
'wt.js',
// sessionization
'wt.co_f',
'wt.vtvs',
'wt.vt_tlv',
'wt.vtid',
'wt.vt_d',
'wt.vt_a_d',
'wt.vt_s',
'wt.vt_a_s',
'wt.vt_f',
'wt.vt_sid',
// onsite add
'wt.ad',
'wt.ac',
// offsite add
'wt.mc_id',
// content groups
'wt.cg_n',
'wt.cg_s',
// scenario analysis
'wt.si_n',
'wt.si_s',
'wt.si_p',
'wt.si_x',
'wt.si_cs',
// offsite search
'wt.srch',
// segmentation
'wt.seg_1',
'wt.seg_2',
'wt.seg_3',
'wt.seg_4',
// onsite search
'wt.oss',
'wt.oss_r',
// misc
'wt.rv',
'wt.tu',
'wt.ev',
'wt.cd',
'wt.nv',
'wt.dm',
'wt.gc',
'dcsdat',
'ora.tag_id'
];
Note: For more details about this implementation, contact your Oracle Infinity solutions consultant.