• Resolved wordmax

    (@wordmax)


    Super plugin!

    I see in the settings the message “The plugin is currently not using an optimized tracking endpoint. To address, create a file named koko-analytics-collect.php in your WordPress root directory with the following file contents…”

    Seems easy enough to do this, but is there any documentation about what exactly this does in simple terms? What’s the benefit or comparison with vs. without using the .php file?

    Consider adding this info to the plugin’s info FAQs

    p.s. I actually just checked cPanel file manager (shared hosting) and the file koko-analytics-collect.php already did exist in the root of the (addon domain) folder. So I wonder why the plugin settings is telling me the file does not exist? Is it checking on the root folder of the primary domain for the shared hosting perhaps?

    Hmmm…

    Thank you!

    • This topic was modified 2 years, 5 months ago by wordmax.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Lap

    (@lapzor)

    The optimized enpoint is a way for Koko to collect analytics without loading the complete wordpress system every time it receives statistics. It’s a small PHP file that loads only the bear necessities needed for Koko to write statistics to a temporary file. The statistics are later collected from that temporary file and loaded into the WordPress database. For a high traffic site, having the optimized endpoint reduce server load and possibly increases page loading speeds.

    It should be checking the root folder of your WordPress installation, and it checks if it can write a file there. Maybe the existing file is not writable?

    Thread Starter wordmax

    (@wordmax)

    Ok, thank you for the info.

    What CHMOD permission setting do you recommend for the .php file? Right now it’s set at 644 by default, which is user write-able so not sure what’s going on.

    • This reply was modified 2 years, 5 months ago by wordmax.
    Plugin Author Danny van Kooten

    (@dvankooten)

    Hello @wordmax,

    Could you please post the contents of the koko-analytics-collect.php file in your root directory please?

    It could also be that while the file exists, the plugin is not able to use it due to it not being able to write to your uploads directory, for example. In order to determine whether Koko Analytics can use the optimized endpoint it goes through the following steps:

    1. Check if koko-analytics-collect.php exists in root directory. If not, attempt to create it.
    2. Send a test tracking request to the optimized endpoint.
    3. If it returns an “OK” response, start using it for live tracking requests.
    4. If it returns an error response, attempt to remove the file again and try again at a later time.

    If you could post the contents of your koko-analytics-collect.php file then I’d be happy to take a look. Does the content match what the plugin says the content should be in your analytics dashboard settings page?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Purpose/benefit of creating tracking endpoint? FAQ’ is closed to new replies.