Account Information

Under the account menu in the main navigation, find Account Settings.

You should see your account information, such as the name of your account, domain, the account owner's email, and more.

You can edit the name, domain, and contact email from this page at any time. Once you change one of these values, you will be prompted to save or undo the changes.

There is also a setting called Allow access via API. Under almost every circumstance, it should remain checked. Unchecking this option will make audience membership information unavailable in the public API requests that power personalization.

Account ID and account number are never editable. They are assigned at account creation and are permanent identifiers.

Lytics API

Allowlist domains public API: List of domains to allow for Public Personalization API regarding referrer.

Allowlist fields for public API: List of fields to allow for Public Personalization API.

Entity Timeout (ms): Max time entity-public API waits before cutting off and returning what it has.

Content

Content paths blocklist: Content paths to prevent content if it contains the path.

Content domains blocklist: Content domains to prevent content from (requires an exact match of the domain to filter: example.com, sub.example.com).

Content created since date: Only include content in the index if the created date is after the specified date.

Content custom properties: Content List of meta tags to include as custom topics.

Custom content properties delimiter: Delimiter to use when parsing custom content topics on HTML meta tags.

Observe robots.txt in content enrichment: Observe robots.txt and meta directives:

robotstxt - Observe only robots.txt directives.
meta - Observe only directives in meta tags.
none - Do not observe any directives

Content since date: Only include content in the index if the enriched date is after the specified date.

Content domains allowlist: Perform content filtering based on exact matches of domains in a URL. Any entries should include relevant subdomains.

Content paths allowlist: Perform content filtering based on partial matches of any component of a URL.

Allow Public Personalization API?: Check the box to allow the user profile of anonymous users to be exposed to users for personalization. It will only include allowed fields.

Content topic blocklist: Blocklisted topics will be hidden from the overall content taxonomy.

Content topic allowlist: List of topics that are required to be in the topic graph and are candidates for content affinity.

Schema

Private fields: List of fields in the schema that are PII/Private and should be hidden unless the explicit role allows viewing private fields.

Promoted Fields: List of user fields to promote in data science modeling and reporting. These fields will be included as candidates for Insights.

Hide Private Fields: Hide PII/Private fields from audience exports and scans initiated by users that do not have access to private fields.

Security

Enforce password history: Check box to prevent re-use of the same password.

Enforce password complexity: Check the box to ensure users have high-password complexity.

Enforce two-factor auth.: Check the box to ensure all users have two-factor auth.

Enforce password bad count: Check the box to lock the user account if too many invalid password attempts are used.

Password max age: Number of days before password must be changed. 0 means no max age.

Logon session days: Number of days a logon session is valid.

Logon session timeout minutes: The number of minutes a logon session with no activity is valid.

Two-factor Authentication

Two-factor authentication is a technique that helps to make your account more secure. It does this by adding a second step to your login process.

Single-factor authentication uses your email address and password to authenticate your Lytics session.

The second factor comes from the Authy app using an Authy SoftToken, a secret token that changes every 20 seconds. Entering a correct token provides an extra level of verification.

What is an Authy SoftToken

An Authy SoftToken is a secret token that is broadcasted to the Authy app every 20 seconds. This unique token serves a second factor by which Lytics can authenticate your session. Authy is available to download for free as a desktop and mobile app: Download Authy.

Using Two-Factor Authentication

The only difference between two-factor authentication and single-factor authentication is an extra step during login. After providing your password, you will then be asked for your Authy SoftToken.

Using Two-Factor Authentication also requires every user to provide their phone number. Logging in with two-factor authentication for the first time will walk a user through this workflow.

Enabling Two-factor Authentication

To enable two-factor authentication for your account, navigate to your account menu at the top right of the Lytics app and select Manage Account. Then go to Security and select the option to Enforce two factor auth.

Tag

JavaScript Tag TTL (3.0): Time to cache the core tag in seconds. This should be used only for testing and based on particular customer needs.

Automatically place the Krux sync img tag onto your site?: Check this box to allow the Lytics JavaScript tag to pass the current visitor's unique identifier, _uid, to Krux for improved identity resolution.

Automatically place the Lotame sync img tag onto your site?: Check this box to allow the Lytics JavaScript tag to pass the current visitor's unique identifier, _uid, to Lotame for improved identity resolution.

Automatically place the Amazon DSP sync img tag onto your site?: Check this box to allow the Lytics JavaScript Tag to pass the current visitor's unique identifier, _uid, to Amazon DSP for improved identity resolution.

Automatically place the Criteo Sync img tag onto your site?
Check this box to allow the Lytics JavaScript Tag to pass the current visitor's unique identifier, _uid, to Criteo and receive a unique Criteo GUM ID for improved identity resolution.

Automatically place the The Google DV360 sync img tag onto your site?: Check this box to allow the Lytics JavaScript Tag to pass the current visitor's unique identifier, _uid, to Google's Cookie Matching endpoint for real-time bidding.

Automatically place the Taboola sync img tag onto your site?: Check this box to allow the Lytics JavaScript Tag to pass the current visitor's unique identifier, _uid, to Taboola and receive a unique Taboola ID for improved identity resolution.

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:

Value	Description
0	Turns event block `off`.
1	Turns on as long as one or more campaigns are active.
2	Turns on permanently.

Global stylesheet (CSS) URL: This stylesheet will be loaded for Personalization experiences and campaigns.

Integration blocklist: List of disabled JavaScript tag-based integrations such as Google Tag Manager or Facebook. The blocklist is defined by adding a "string" that represents the integration. Below we have outlined all available web-based integrations that can be blocked. The value in the slug column represents the "string" you enter in the UI.

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.

Custom Data Layer: List of variable names to be collected at load time by the Lytics JavaScript tag.

Enable pageview event on first send (JS Tag V3 only): When enabled, this ensures the pageview event is tracked on the first call to jstag.send() per page load. This account setting only applies if you've implemented version 3 of the JavaScript tag.

Disable Automatic Initial Pageview (JS Tag V2 only): When checked, this prevents a jstag.send() call from being made automatically on page load. This can be helpful if you want to send your pageview events manually. This account setting only applies if you've implemented version 2 of the Lytics JavaScript tag, which is in the process of being deprecated.

Custom cookie keys: List of cookie names to be collected at load time by the Lytics JavaScript tag.

Personalization (Pathfora SDK) JSON config: Enter Personalization JSON config.

URL allowlist for Orchestrate: List of strings that, if matched, will result in Experiences being evaluated in place of legacy campaign variations.