Sets the number of minutes between visitor profile refreshes. Only integers are supported, for example, “2” would be 2 minutes.
Collectors are modules that gather supplemental information from the device and append it to the data layer before it’s transmitted to the Tealium Customer Data Hub. Some collectors are included in the core library, while others are optional and installed as separate modules.
The following table lists the available collectors. Default collectors are denoted by a * next to the collector name.
These modules are enabled or disabled using the TealiumConfigcollectors property.
Defines the consent policy to adhere to. If no consent policy is defined on the TealiumConfig object, the consent manager becomes disabled.
The following consent policies are available:
Defines user consent preferences expiration.
The amount of time before expiration
The unit of time before expiration
new ConsentExpiry(90, TimeUnit.days)
The following time units are available:
Dispatchers are modules that send the data from your data layer to a Tealium endpoint. The following dispatchers are currently available:
At least one dispatcher is required. If no dispatchers are specified, no tracking occurs.
Sets the logLevel property, which controls how much information is logged.
The following logging levels are available:
Informational events that highlight the progress of the application
Debug-level events used for debugging an application
Error events such as critical errors and failures
No Logging (default)
Overrides the Tealium Collect profile to send data to a different Tealium profile.
config.overrideCollectProfile = "main"
Overrides the domain name in the Tealium Collect URL to send data to a different endpoint.
config.overrideCollectDomain = "my-company.com"
config.sessionCountingEnabled = false
The environment is one of three default environments (Dev, QA, Prod) or any custom environments that Tealium publishes to. Select one of these environments.
The visitor profile is an object that contains friendly names for each attribute. There is a currentVisit property that allows you to distinguish visitor/visit attribute types. Access each attribute value by ID using a subscript. If the attribute does not exist, null is returned. See the below list for examples.