Zaius tracks visitors using browser cookies. When a visitor lands on your website, Zaius will check for an existing tracking cookie. If one does not exist, a cookie will be associated with that visitor and will register each page that the person visits moving forward.
There are a few things to be mindful of in regards to how Zaius handles tracking cookies:
- Zaius will attribute page views to an identified customer if they click a link in a tracked email that directs to a page with the Zaius JavaScipt tag installed.
- Visitors will be tracked before they become a known customer.
- If and when a visitor fills out a web embed or modal, Zaius will associate their previous anonymous page views based on their tracking cookie. If the email address used in the web embed or modal is associated with an existing customer, this visitor will be identified as the customer. This automatic association also applies to customers that were imported.
- Zaius utilizes customer identifiers such as a customer's email address and the VUID included in a customer's cookie to determine which events are associated with the customer. These identifiers are also used when determining if events from "different" visitors should be merged.
- If a visitor deletes their cookies, they will be considered a new visitor and will be assigned a new cookie. However, Zaius will automatically apply user resolution and merge submissions coming from the same email address, even if different cookies were associated with those submissions.
- If a customer uses a different browser or blocks cookies and doesn't provide identifiable information (e.g., Email address, login information, etc.) in their subsequent visits, their events will be counted as if they are multiple unique visitors. Ultimately, every event is provided a user ID. If the event can't be resolved to an existing customer profile, then it's considered unique.
- If multiple people share a single computer and browser, their submissions will result in unique customer profiles as long as a unique customer identifier (e.g., Email address) is provided. That said, the profile associated with the most recent submission would inherit the shared browser cookie/VUID, and all events would be incorporated into that profile until another high confidence submission from one of the "secondary" users occurred.
Effect on email campaigns
- Email campaigns can only be sent to identified customers. This requirement is particularly important to keep in mind when evaluating behavioral campaigns like cart abandonment. Zaius will qualify someone for a cart abandonment campaign if they add a product to their cart and then do not complete a purchase. However, if the event cannot be associated with a known customer email address via an identifier, like their browser cookie, an email cannot be sent. This means it's likely that you will observe more cart abandonment events than cart abandonment email sends.