Skip to content

Bring back visitors tracking #70

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from
Draft

Bring back visitors tracking #70

wants to merge 4 commits into from

Conversation

m-aciek
Copy link
Collaborator

@m-aciek m-aciek commented Feb 20, 2025

Use Plausible's top-stats endpoint, along with backoff configuration for retrying.

For reference, that's a sample full response content of the endpoint:

{
    "meta": {
        "imports_included": false,
        "imports_skip_reason": "no_imported_data"
    },
    "from": "2024-06-03",
    "interval": "month",
    "to": "2025-02-20",
    "sample_percent": 100,
    "top_stats": [
        {
            "name": "Unique visitors",
            "value": 45416,
            "graph_metric": "visitors"
        },
        {
            "name": "Total visits",
            "value": 50711,
            "graph_metric": "visits"
        },
        {
            "name": "Total pageviews",
            "value": 85781,
            "graph_metric": "pageviews"
        },
        {
            "name": "Bounce rate",
            "value": 72,
            "graph_metric": "bounce_rate"
        },
        {
            "name": "Time on page",
            "value": 124,
            "graph_metric": "time_on_page"
        }
    ],
    "comparing_from": null,
    "comparing_to": null,
    "includes_imported": false,
    "with_imported_switch": {
        "visible": false,
        "togglable": false,
        "tooltip_msg": null
    }
}

Refs #68.


📚 Documentation preview 📚: https://pydocs-translation-dashboard--70.org.readthedocs.build/


📊 Dashboard preview 📊: https://python-docs-translations.github.io/dashboard/70/merge/

@AA-Turner
Copy link
Member

How much do we need visitor numbers? I'd prefer to sort this out properly with Plausible (we're following up via internal channels). But even so, translation progress isn't clearly causally linked to demand for translated versions, and readership of translated versions might have a closer relationship to latent demand rather than progress (capturing 100% of a market 1% the size).

A

@m-aciek m-aciek marked this pull request as draft February 20, 2025 13:27
@m-aciek
Copy link
Collaborator Author

m-aciek commented Feb 20, 2025

I'd prefer to sort this out properly with Plausible (we're following up via internal channels).

Putting the PR to draft, to let sort it out properly first 👍

How much do we need visitor numbers? […] But even so, translation progress isn't clearly causally linked to demand for translated versions, and readership of translated versions might have a closer relationship to latent demand rather than progress (capturing 100% of a market 1% the size).

Visitor number reflects the impact of the translation on people. I agree that it's related to (induced by?) the completion. In my opinion it's an interesting metric to track. It can be motivating for the translations contributors.

@StanFromIreland StanFromIreland linked an issue Mar 7, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Builds failing on Plausible requests
2 participants