• Setting Personzye to monitor visitor interactions with content/products

    For Personyze to generate meaningful recommendations, it has to know whenever visitors interact with a product/article/video, and what type of interaction they’re having.

    The first interaction is a view. Personyze knows whenever a visitor views a product, if they navigate to that product generically, or if they clicked on a Personyze recommendation widget to view that product. However they arrive, the next possible actions for them to take may be to “Like,” “Add to Cart,” “Purchase,” and other similar actions for content and video. Personyze tracks and is aware of all of these interactions.

    Once Personyze knows about the interactions listed above, it can generate recommendations that take them into consideration. For instance, what were the products most often viewed after this product? What products were bought together with this product? Furthermore, you can set visitor interests based on interactions with products; for example, if visitors buy baby car seats, you can set their interest to be a car owner and a family.

    The interactions being monitored need to be consistent with your product catalog. When you set Personyze to monitor and record the visitors viewing a product, the monitoring needs to be able to record a unique ID that represents a unique product in your product catalog, thereby allowing Personyze to take into consideration the product attributes and associated interests of that product.


    How to Set Personyze to Monitor Interactions:

    There are 2 ways you can programmatically set your site to fire a javascript event, by using the product ID and type of interaction, or use the Personyze simulator to grab the products from the page, whether it is in cookies or meta tags, or to be selected visually on the page, URL parameters. Basically, every data grabbing option in the simulator is available, as long as it does the job and sends Personyze the view event, whenever a visitor visits the page.


    Screen Shot 2017-05-11 at 3.33.10 PM



    What if you don’t have a product ID on the page that matches a product ID in your catalog?

    In this circumstance, you or your IT service can add the ID to the page as a Javascript variable, or inside a hidden HTML ID, or if that’s not possible, you can use a less unique identifier (if there is no other way) such as the product title.

    In that case, you can set Personyze to grab the product title/URL, and the title/URL is going to be used as ID. When you upload or synchronize your catalog, instead of using the product ID in the column, (“Product Internal ID”) you use the product title/URL; that way, Personyze can convert this text into a number, and make the connection between this number with the number sent as event from your  site whenever a visitor viewed a product.

    How to Set Add to Cart or Like Event

    If you need to send the event “Like” or “Add to Cart,” those events can be sent from a page without product ID. If they are sent from the same page URL that sent the product ID before, Personyze will automatically assign this event to that last ID.

    However, in case you need to send a specific ID, for example, if it was an upgrade product, you can send the Add to Cart event with the product ID, which will override the previous ID.

    You can use the simulator to grab the product ID, and send the Add to Cart event only if the visitor clicked on page elements such as the Add to Cart button.

    Screen Shot 2017-05-11 at 3.34.45 PM


    Special Event Type:

    Personyze remembers from it’s entire lifetime on your site (unless you clear it) the different interactions and states that the visitor has had with your products, meaning that if the visitor added a product to his cart, personyze will remember it, and might continue showing recommendations for that product, or send email alerts when the price changes for that product, until you tell Personyze that the visitor removed the product from his cart, or bought the product. You can use a special event to flash out all products together, for example “check out all events,” meaning you can set Personyze to remove these interests whenever a visitor clicked on the cart

    You can use a special event to flush out all products together; for example “Check Out All Events,” meaning you can set Personyze to remove these interests, whenever a visitor clicked on the cart checkout button, to check out all products that are currently in the visitor cart, or remove all when visitor clicked on the empty cart button.

    Screen Shot 2017-05-11 at 3.36.10 PM