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 unvailable 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.
Whitelist domains public API: List of domains to whitelist for Public Personalization API regarding referrer.
Whitelist fields for public API: List of fields to whitelist for Public Personalization API.
Blacklist IP CIDR ranges for all API endpoints: Provide a list of valid CIDR Ranges. For any API endpoint ensure it is not coming from an IP in given disallowed ranges.
Whitelist IP CIDR ranges for all API endpoints that require authorization: Provide a list of valid CIDR Ranges. For any API endpoint that requires auth, ensure it is coming from an IP in given allowed ranges.
Collect entire user agent string?: Check box to collect entire user agent string.
Entity Timeout (ms): Max time entity-public API waits before cutting off and returning what it has.
Content paths blacklist: Content paths to prevent content if it contains path.
Content domains blacklist: Content domains to prevent content from (
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 whitelist: Content domains to limit content to.
Content paths whitelist: Content paths that must exist for content to be included.
Allow Public Personalization API?: Check box to allow the user profile of anonymous users to be exposed to user for personalization. Will only include whitelisted fields.
Content topic blacklist: Blacklisted topics will be hidden from overall content taxonomy.
Content topic whitelist: List of topics that are required to be in the topic graph and are candidates for content affinitiy.
Private fields: List of fields in schema that are PII/Private and should be hidden unless explicit role allows viewing private fields.
Enforce password history: Check box to prevent re-use of 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.
_uid, to Krux for improved identity resolution.
_uid, to Lotame for improved identity resolution.
Allow event block:
1- allow with campaign
2- on permanently
Global stylesheet (CSS) URL: This stylesheet will be loaded for Personalization experiences and campaigns.
Personalization (Pathfora SDK) JSON config: Enter Personalization JSON config.
URL whitelist for Orchestrate: List of strings that, if matched, will result in orchestrated experiences being evaluated in place of legacy campaign variations.