This data is then sent to Lexer through a Payload that can map to a customer profile through an identifiable action (i.e. newsletter subscription, account login, account registration, transaction, etc.) enriching your existing customer data.
A list of all the product categories viewed by a customer while on site.
Date of last visit
The date of the customers last visit to your website.
A list of all the dates the customer visited your site.
The type of devices the customer used to browse your website.
Did complete conversion
A flag to say that the customer did checkout.
Did start conversion
A flag to say that the customer started the checkout journey.
Pages viewed to convert
The number of pages the customer viewed to checkout in their last session.
Products added to cart
A list of the products added to the customers cart while on site.
Data Punk t-shirt
Products removed from cart
A list of the products removed from the customers cart while on site.
Data Maiden t-shirt
A list of all the products viewed by the customer while on site.
Data Rockstar t-shirt
Profiles that have submitted a response to any of the surveys you have created within Lexer.
The site responsible for the visit - i.e. the customer clicked on a Facebook post.
Time spent to convert
The number of seconds it took the customer to checkout in their last session.
The name of the promotion or campaign that brought a customer to your site.
The specific content that brought the customer to your site.
The medium that brought the customer to your site, such as social or email.
The external site that brought the customer to your site, such as Facebook or Amazon.
The search terms that brought the customer to your site.
Device used: Did the customer browse on a Mobile, Tablet, or Desktop device?
Time spent to convert: How long did the customer spend on the site?
Referrer URL: The domain of the site the customer came from, only supported on some browsers.
UTM codes: How did the customer land on my site?
At the point of a customer’s conversion, you are able to send all captured data to Lexer by employing the 'lxt('converted')' command. This could happen when a customer makes a final action on your site, like completing the purchase of a product.
If you currently use UTM codes in your newsletters, the Lexer Tag will automatically collect that information once we have embedded some custom code into your newsletters/email campaigns. Contact Lexer Support ([email protected]) for assistance in setting this up.
Updated 3 days ago