Search

WordPress AI Recommendations
- SEO, conversions -

Forum Replies Created

  • mcl7
    Participant
    2 months, 2 weeks ago in reply to: Sending featured_image_url to Algolia? #38483

    Final request on this. I noticed that even though the images are now available for each of the products the taxonomy featured image is not available. So for example, brand and product category featured images are showing has having missing images in the Algolia UI.

    Should the change we made be addressing this?

    mcl7
    Participant
    2 months, 3 weeks ago in reply to: Sending featured_image_url to Algolia? #38474

    Ok great, it works. thanks.

    mcl7
    Participant
    2 months, 3 weeks ago in reply to: Sending featured_image_url to Algolia? #38472

    hmm. I tried this and I don’t see a field that includes the actual image path as needed.

    I do see a new field and another previously that stores the id’s of the images:

    _product_image_gallery_str [“99782,99783,99784”]
    _thumbnail_id_str [“99781”]

    However, neither of the above allows us to display the image within the Algolia UI’s (Merc Studio and the normal UI). We would need the absolute or relative paths to the image(s).

    images
    {
    thumbnail:
    { url: “https://mydomain.com/wp-content/uploads/2021/04/long-product-name-here-150×150.jpg”, width: 150, height: 150 }
    }

    Here is a screenshot of the options they give you when you click “Display Preferences” when viewing an index in the Algolia management UI.

    Screenshot-2024-01-05-at-9-26-45-AM

    mcl7
    Participant
    2 months, 3 weeks ago in reply to: Sending featured_image_url to Algolia? #38462

    any chance of an early release of 23.6?

    mcl7
    Participant

    They are visible only in each result’s individual record but they are not displayed as facets.

    mcl7
    Participant

    I worked on this today. You were right, that error was produced by Variable products. Moving the few that I had to draft solved the error. Now though I reindexed everything and it is available within the faceted search widget but the facets do not display (even though products on sale are in the results).
    Im confused at this point because I have deleted all my indices and recreated them but still nothing. What is strange is I just went through a similar process when adding In stock /Out of stock as a facet and didn’t have any problems.

    I have checked algolia and the wpsorl_sale_price is in there and populating accurately. However, it is not being displayed as a facet in the algolia admin. It is showing in the wp widget like mentioned above but the On Sale facet does not display.

    Also, trying to sort the results so that products on sale show up first then products not on sale followed with out-of-stock products but isn’t working either. Primary sort is stock_status asc and then wpsolr_on_sale desc. Does that sound right?

    mcl7
    Participant

    Just so I am clear. I get the error immediately after starting the redindex.

    mcl7
    Participant

    Im trying to get this exact thing to work but when I follow the instructions above I get the following error:

    Error on line 794 of file /www/mysite/public/wp-content/plugins/wpsolr-pro/wpsolr/pro/extensions/woocommerce/class-wpsolr-plugin-woocommerce.php: Trying to get property ‘name’ of non-object

    mcl7
    Participant
    2 years, 9 months ago in reply to: Algolia insights tracking #27055

    Ok cool, understood.
    Until then, the only thing that I technically need to make this happen is the actual Algolia queryID to be provided in the HTML source somewhere.

    If you can do that I can go through the whole process and document it for you and propose a way for you to integrate it with your plugin. I will be able to be very specific after I go through the entire process.

    Thoughts?

    mcl7
    Participant
    2 years, 9 months ago in reply to: Algolia insights tracking #27010

    Thank you for the feedback!

    UserToken: we are going to simplify this by only issuing hashes for users that have logged in. In the future, we may look to solving the problem you are talking about but right now its not a big concern.

    Personalization: anything that the user searches for, clicks on, or purchases are the starting point which is what Algolia Insights provides. Before we even get to talking about the Recommendations API implementing Algolia Insights is required to fully take advantage of the Analytics they provide from within their system.

    Considering the Recommendations API – there are a lot of things we can do but yes there is the actual personalization of any recommendations that are being presented but we also have the ability to present personalized results in other channels, specifically email.

    Lastly, I would say that the other benefit for us is to simply have all of the recommendations, categories, and search all powered by a single search provider.

    Is it possible to add the queryID to the source?

    mcl7
    Participant
    2 years, 9 months ago in reply to: Algolia insights tracking #27008

    Been a while since I posted this but not because it’s not important. It actually became more important because it’s required in order to utilize the Recommendations API that Algolia just launched.

    What is needed here is pretty straight forward and it could work a couple of ways (to answer your question).

    There are a few ways to implement this outlined in the Algolia documentation: Google Tag Manager, Segment.com, or just your own code.

    I’m going to be using Google Tag Manager but I believe what we need from WPsolr is independent of which option someones decides on (?). I suppose you could do different configurations for each option within a single addon? I will leave implementation for later though and just stick to the bare essentials for this to work for everyone.

    What is required to make this work are three things made available by WPSolr (in the HTML source of pages powered by WPSolr) so that they can be passed to Algolia Insights along with clicks, conversion:

    1. ObjectID – This is just the productID (1234-0). Note that there is a -0 after the productID in the source generated by WPSolr. I believe this is related to the index but I will confirm after my call with Algolia. Ideally, though, the -0 is appended to the product ID to keep it clean (not require us to add it).

    2. Position – No action is required here as it’s just a calculation that we need to do on our end that tells Algolia where the product was in the results.

    3. QueryID – This is just the Algolia queryID that needs to be made available in the HTML source as well so that it can be passed back to Algolia along with clicks and conversions.

    So, from here. The only thing we REALLY need is the Algolia queryID to be displayed in the HTML somewhere.

    However, the following is also required and I wanted to cover it even though it may be out of the scope of what is needed from WPSolr.

    4. UserToken – Here Algolia is asking for us to pass – and store on our end – a unique hash for each user that can be passed to Algolia. I am planning on using ACF for a custom field to store a hash for each user that we can also pass to Algolia. I don’t think we need anything from WPsolr for this but thoughts here are most welcome!

    So, lots of words here but I think all we really need from WPsolr to implement Algplia Insights is the queryID to be somewhere in the HTML.

    Is this something you can provide (or maybe is already there and I am missing it) in WPsolr?

    mcl7
    Participant
    2 years, 11 months ago in reply to: Noindex/No Follow all WPSolr URL’s #26318

    I am not longer using Yoast but curious I would accomplish this with perhaps a code snippet. Any advice?

    mcl7
    Participant

    ok cool, thank you.

    mcl7
    Participant
    2 years, 11 months ago in reply to: Google Analytics Issues? #25971

    Would you place in this in the head or body?

    mcl7
    Participant
    2 years, 11 months ago in reply to: Google Analytics Issues? #25950

    I put this on the back burner but picking it back up again. First of all, thank you for the code.

    I wanted to add to this that the Google Analytics tracking for filter URLs does actually work but ONLY when you do a hard refresh (or paste the URL in a new browser tab). This makes sense because without the hard refresh the GA code doesn’t fire and therefore the pageview is not passed to GA. However, when you reload the whole page of course it does and without modifying any code we see the page views reported in GA just fine.

    It’s only when refreshing just the result set that the page view is not passed. We played with the code you provided attempting different implementations to solve this but no luck.

    While we were going through – and saw the pageviews being reported in GA on a hard refresh – I started to question if the code you provided would result in a double count on a hard refresh (single pageview count if only using the filter which ideally fires your code)?

    Any ideas here?

Viewing 15 posts - 1 through 15 (of 102 total)