• Resolved clip1492

    (@clip1492)


    For any unkown reason, Woocommerce Product Archives are not showing on analytics. Nor category archives. This means the /store/ URLs and /cat/category1/ . However everything else appears correctly, including Woo products and Woo my-account area.

    On my attempt to solve it myself, I’ve spent around 10 minutes searching on google how to create endpoints: Searched on 1) Koko analytics documentation, 2) GitHub and 3) the WordPress Plugin forums. All with no luck. I haven’t found a comprehensive guide to create them. Neither on the plugin Settings on Admin, that is the first place where I expected to start creating endpoints. 10 minutes after I found something interesting on the snippets here:

    define(‘KOKO_ANALYTICS_CUSTOM_ENDPOINT’, ‘/path-to-your-custom-endpoint-file.php’);

    and changed the path to ‘/store/’ but it didn’t worked.

    Did the same on koko-analytics-collect.php located at the root of WP, but I got no results. Still unlisted.

    TThe process seems really complex, and after attempting to understand something, I abandon here after more than an hour lost, not before giving a chance to disabling all plugins (except Woocommerce and ACF) (and theme functions.php) while the error still was reproducing, so abandoned. I’ve a ton of work to complete, and understood that endpoints are not so straight and unclear, or maybe I’m in the wrong direction.

    There is any straight guide to set custom end points somewhere? Or I’m experiencing a bug or plugin incompatibility with /store/ and /categories/ or I’m missing something?

    • This topic was modified 2 months, 1 week ago by clip1492.
Viewing 1 replies (of 1 total)
  • Plugin Author Danny van Kooten

    (@dvankooten)

    Hello @clip1492,

    I’m sorry to hear about the time you already spent on this.

    Right now, Koko Analytics only tracks pageviews to pages with an internal post ID (ie: anything in the wp_posts table) + the homepage as a special case. It does not track taxonomy archives. This has to do with the plugin not storing actual page URL’s but piggybacking on top of WordPress post ID’s, so adding in the other pages that a website typically has would require a fair amount of engineering that we have yet to do without slowing down the plugin and/or breaking backwards compatibility…

    We will add this to the plugin FAQ and knowledge base so it is more clear. I’m sorry that this is probably not what you wanted to hear, especially after digging into it yourself already.

    Best,
    Danny

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.