[WEBSITE] Correct Google Analytics Tracker

[szha]

Description

(Brief description on what this PR is about)

Checklist

Essentials

Please feel free to remove inapplicable items for your PR.

• The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
• Changes are complete (i.e. I finished coding on this PR)
• All changes have test coverage:
• Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
• Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
• Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
• Code is well-documented:
• For user-facing API changes, API doc string has been updated.
• For new C++ functions in header files, their functionalities and arguments are documented.
• For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
• Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
• To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

• Feature1, tests, (and when applicable, API doc)
• Feature2, tests, (and when applicable, API doc)

Comments

• If this change is a backward incompatible change, why must this change be made.
• Interesting edge cases to note here

[aaronmarkham]

Hi @szha - So the config for the ID should be here:
https://github.com/apache/incubator-mxnet/blob/master/docs/static_site/src/_config_prod.yml
It is there, so any mention of the tracker ID should be using the variable, not be statically defined.

[aaronmarkham]

It is setup to use it here: https://github.com/apache/incubator-mxnet/blame/master/docs/static_site/src/_includes/google-analytics.html

I'm not sure why there are two analytics files. Maybe this one should be deleted. I think the config is setup correctly because if you view source the ID is -1.

[aaronmarkham]

nevermind... I guess each micro site needs its own setup. Though, I'd much rather this was maintained centrally in one config.

My mistake... looking at the jekyll config, not the python one. Though we should definitely have comments in there that mention where these files reside.

[ThomasDelteil]

@aaronmarkham the python docs header is done through the theme which is loading the analytics file that @szha changed

[marcoabreu]

Yeah agree, would be good to have these settings centralized