Editing Your Account
In Lytics, an account represents all data, audiences, campaigns, and integrations. This is separate from account users, who may be a member of multiple accounts.
Finding & Editing 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.
At any time you can edit the name, domain and contact email from this page. Once you change one of these values you will be prompted to save or undo the changes.
Account ID and account number is never editable. They are assigned at account creation and are permanent identifiers.
Profile Access Control
Also under Account Settings, there is an option called Profile access control. On this page there is a setting called Allow access via API. Under almost every circumstance, should remain checked. Unchecking this option will make audience membership information unavailable in the public API requests that power personalization.
Previously, Lytics provided users with a Full API Key and a Data API Key. These have been deprecated in favor of API tokens which you can generate from the Lytics dashboard, see Managing API tokens for more information.
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 paths blocklist: Content paths to prevent content if it contains path.
Content domains blocklist: Content domains to prevent content from (requires an exact match of the domain to filter:
Content created since date: Only include content in index if created date is after 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 index if enriched date is after 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 box to allow the user profile of anonymous users to be exposed to users for personalization. Will only include allowed fields.
Content topic blocklist: Blocklisted topics will be hidden from overall content taxonomy.
Content topic allowlist: List of topics that are required to be in the topic graph and are candidates for content affinitiy.
Enable Decisioning Scores: Turn on "needs_message" and "next_event" scores.
Private fields: List of fields in schema that are PII/Private and should be hidden unless 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.
Enforce password history: Check box to prevent re-use of the same password.
Enforce password complexity: Check box to ensure users have high-password complexity.
Enforce two factor auth.: Check box to ensure all users have two-factor auth.
Enforce password bad count: Check box to lock user account if too many bad 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: Number of minutes a logon session with no activity is valid.
_uid, to Krux for improved identity resolution.
_uid, to Lotame for improved identity resolution.
_uid, to Amazon DSP for improved identity resolution.
_uid, to Google's Cookie Matching endpoint for real-time bidding.
_uid, to Taboola and receive a unique Taboola ID for improved identity resolution.
Allow event block:
|0||Turns event block |
|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.
slug column represents the "string" you enter in the UI.
|Adroll||adroll||Adds a record named |
|AddThis||add_this||Adds the current audience membership to the |
|Amazon DSP||amazon||Adds the Amazon DSP pixel to site.|
|Facebook Ads||facebook_ads||Pushes Lytics audience membership as an array to the custom |
|Google Analytics||google_analytics_dimensions||Pushes audience membership as a comma separated string to a predefined custom dimension. Also emits a |
|Google DFP||google_dfp||Sets audience membership to a targeting param with the name |
|Google Tag Manager||gtm||Collects the |
|Krux||krux||Adds the Krux pixel to site.|
|Lotame||lotame||Adds the Lotame pixel to 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 |
|Lytics Audience Cookie||segments_cookie||Stores current audience membership for user as cookie.|
|Taboola||taboola||Adds the Taboola pixel to site.|
|Tealium||tealium||Collects the |
Enable pageview event on first send (JS Tag V3 only): When enabled, this ensures the pageview event (
_e: pv) is tracked on the first call to
Disable Automatic Initial Pageview (JS Tag V2 only): When checked, this prevents a
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.