Community

Yes, Lytics recieve custom cookie data on a per-account basis with no extra development work. You can add custom cookies via the dashboard by navigating to Account Settings > Tag and editing the Customn Cookie keys field. For more details see Editing Your Account.

See the stream key under Configuration Options.

Lytics does a lookup based on user IP through service called GeoIP from a company called Maxmind.

Raw event keys can be hidden on the Data Streams section the user interface. It is important to note that once hidden, keys cannot be made visible again through the user interface - only through the API. It is recommended that a list is kept of hidden keys in the event one needs to be resurfaced at a later date. To hide a key: 1. Select the checkbox in the row of the key you wish to hide under "Raw keys in this Stream". 2. Click on the Remove selected key button. To unhide a key: Currently, hidden keys are completely invisible to the user interface. They may be re-added through the API. If you need assistance, please contact us at [email protected] with the key name and your account ID.

This is common, and can happen for a number of reasons. If the count relates to a number of users this is likely because Lytics is performing identity resolution across your data from all channels to merge profiles wherever possible. Sometimes this can result in smaller or larger user counts (depending on the id resolutions strategy) because Lytics has merged or not merged users based off of common identifiers. Keep in mind, if you are looking to compare user counts after a large bulk import, it may take some time for the import to finish processing in Lytics, so the user count may not be accurate during that time. If the difference is extremely large in your user counts, it is possible that unique identifiers are not being selected and mapped correctly. Unique identifiers (or "by-fields") are fields that can constitute merging within your Lytics account.

For sites not using Google Tag Manager, customer consent on the web can be managed in a few different ways. Consent triggers can be listened for by adding a snippet of custom JavaScript to your site. Another alternative, is to use a cookie consent solution. Github has documented a [free](https://github.com/osano/cookieconsent) solution with demos. The Lytics JS Tag can be configured to consume triggers from any of these solutions to manage consent for your customers.

Lytics is not an ad provider, therefore, the IAB Europe Transparency & Consent Framework does not apply. The IAB Global Vendor List contains any ad vendors, publishers or consent management platforms that have met the guidelines outlined by the IAB Framework.

The Recent Events section of the dashboard page provides a keyhole view of what Lytics is doing in the background. Here are a few types of "events" that you might see in your account: User X entered the audience Y Users may enter and exit audiences in real time based on their activity. In the recent events feed you may see users who have entered a Lytics the default Lytics audiences powered by data science such as "Lytics Highly Engaged" or "Lytics Disengaged". Webpage X was classified as topics Y, Z, and more. If the content affinity engine is enabled in your account, you may see these types of events. Lytics is crawling the contents of your website in the background and analyzing and extracting topics from it. These events pertain to a document that was recently classified and the topics that were extracted for that document. User X was merged from cross-channel users Y & Z User profiles can be merged together if Lytics receives an indication that two existing profiles from different sources are actually one person. For example, you may have an anonymous user profile for someone who has browsed your website, and a known profile from historical email data. When a user submits their email through a form on the website we can merge the two profiles off of the common email identifier.

At the most basic level, Lytics Identity Resolution leverages a graph style database, our own query language, and a set of unique identifiers to understand the relationship between fragments of data (from anonymous to known) about a person’s identity. These fragments are then enriched and surfaced in the form of an individual user profile in real time.

When sending Lytics custom data at the hour or minute level, if you do not specify the timezone in the data our system will default to UTC. In our UI the time fields displayed are calculated to your local machine time.