The following configuration options are available within the account settings JavaScript Tag section.
Client Side Integrations
A set of client-side integrations is facilitated by the core Lytics SDK. Each of those integrations is either deployed or disabled based on a series of checkboxes under the "Client Side Integrations" section. Each of those options follows the pattern outlined below.
Checking the box enables the integration and will result in either audience membership or attributes being passed to a partner if that particular integration's associated tags and configurations are also in place on the page.
Client-side integrations supported out of the box:
Amazon DSP: Allow Lytics to pass the current visitor's _uid to Amazon DSP for improved identity resolution.
Amazon DSP Confirmation Events: If false, confirmation events will not be sent to the amazon_dsp stream upon successful sync completion.
Criteo: Allow Lytics to pass the current visitor's _uid to Criteo and receive a Criteo GUM ID for improved identity resolution.
Google Ads Partner API: Allow Lytics to use the Google Partner API to make Google Ads calls.
Google Analytics 4 (GA4): Allow Lytics to pass the current visitor's _uid and audience membership to GA4.
Google DV360: Allow Lytics to pass the current visitor's _uid to Google DV360 and receive a unique DV360 ID for improved identity resolution.
Krux: Allow Lytics to pass the current visitor's _uid to Krux for improved identity resolution.
Lotame: Allow Lytics to pass the current visitor's _uid to Lotame for improved identity resolution.
Taboola: Allow Lytics to pass the current visitor's _uid to Taboola and receive a unique Taboola ID for improved identity resolution.
The Trade Desk: Allow Lytics to pass the current visitor's _uid to The Trade Desk and receive a unique Trade Desk ID for improved identity resolution.
Yahoo Ads: Allow Lytics to pass the current visitor's _uid to Yahoo and receive a unique Yahoo ID for improved identity resolution.
In addition to those outlined above, many automatic client-side integrations are included within the Lytics core SDK. These integrations automatically sync enabled profile data with other tools if those tools have been configured on your site, too. For instance, Lytics will sync audience membership for the current visitor with Meta if the Meta pixel is also present on the page. To prevent these syncs, each integration can be blocked by adding the proper key to the "Integrations Blocklist" as outlined below:
In this example, we have added the "google_analytics_dimensions" slug to the blocklist to prevent sending profile data to custom dimensions in Google Universal Analytics.
Available client-side integrations and their associated slugs:
Name
Slug
Description
Adroll
adroll
Adds a record named adroll_segments to the user, which houses audience membership.
AddThis
add_this
Adds the current audience membership to the __attag cookie.
Amazon DSP
amazon
Adds the Amazon DSP pixel to the site.
Facebook Ads
facebook_ads
Pushes Lytics audience membership as an array to the custom Lytics Audiences value for the user.
Google Analytics
google_analytics_dimensions
Pushes audience membership as a comma-separated string to a predefined custom dimension. It also emits a noninteraction event each time the sync occurs for a user.
Google DFP
google_dfp
Sets audience membership to a targeting param with the name LyticsSegments.
Google Tag Manager
gtm
Collects the dataLayer object when the Lytics tag loads. It also passes audience membership to GTM as a push event.
Krux
krux
Adds the Krux pixel to the site.
Lotame
lotame
Adds the Lotame pixel to the site.
Optimizely
optimizely
Pushes a custom tag with the audience membership.
Pathfora
pathfora
Allows for the installation of Pathfora (Lytics Personalization SDK).
Qubit
qubit
Collects the universal_variable object when the Lytics tag loads.
Lytics Audience Cookie
segments_cookie
Stores current audience membership for the user as a cookie.
Taboola
taboola
Adds the Taboola pixel to the site.
Tealium
tealium
Collects the utag_data object when the Lytics tag loads.
JavaScript Tag TTL (3.0)
The amount of time to cache the core JavaScript SDK in seconds. This should be used only during testing to ensure settings configured are reflected more often, but it may result in degraded performance for high-traffic production use.
Enable pageview event on first send (3.0)
Enables the automatic pageview event (_e: pv) in the first send event of every page load in JStag v3.
Allow Pathfora
Check this box to allow the Lytics JavaScript tag to automatically add the Pathfora personalization library to your site (default). Uncheck to disable any Pathfora-powered web-based personalization.
Allow Event Block
Check this box to allow the Lytics JavaScript tag to automatically add the Pathfora personalization library to your site (default). Uncheck to disable any Pathfora-powered web-based personalization.
0: Turns event block off. 1: Turns event block on if there are one or more active Lytics Experiences. 2: Turns event block on permanently at all times.
Global Stylesheet URL (CSS)
This custom stylesheet will be loaded in support of Lytics-managed Experiences.
URL Allowlist for Orchestration (Experiences)
List of strings that, if matched, will result in Experiences being evaluated in place of legacy campaign variations.
Personalization (Pathfora SDK) Generalized Config
The hashed JSON configuration is to be loaded globally for all Lytics-managed experiences.
Custom Cookie Keys
A list of cookie names that should be automatically collected by the core Lytics SDK.
Custom Data Layer
A list of JavaScript variables that should be automatically collected by the core Lytics SDK.
