Skip to content
Hive Check

Hive Check visited your website

MyJourneyAnalyticsHiveCheck is the checker of My Journey Analytics. It audits a website's tags and cookie consent for a customer of ours who manages that site. Here is what it does, and how to allow or block it.

For website owners

What the checker is, and what it does.

It visits public pages the way a visitor's browser does, records which tags load and what they send, before and after consent, and reports it to the person who ran the check.

What Hive Check is

An audit of a website's tracking: the tags on each page, the cookie banner, and the data the tags send before and after a visitor chooses.

  • It is run by a customer of My Journey Analytics who manages the site, such as its owner or their agency.
  • Only public pages: it never logs in, and never fills in or sends a form.
  • The results go to that customer's own workspace.
How Hive Check works

How it identifies itself

Every request carries the name MyJourneyAnalyticsHiveCheck in its user agent, with a link to this page.

  • robots.txt and sitemaps are read with the first user agent.
  • Pages are loaded in a real Chrome browser with the second, so banners and tags behave as they do for visitors. The Chrome version in it changes over time; the name stays.
User agents
MyJourneyAnalyticsHiveCheck/1.0 (+https://myjourneyanalytics.com/hive-check)
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 MyJourneyAnalyticsHiveCheck/1.0 (+https://myjourneyanalytics.com/hive-check)

It follows robots.txt

Before loading any page, the checker reads your robots.txt and follows the rules for MyJourneyAnalyticsHiveCheck, or the rules for all crawlers when there are none for it.

  • Pages robots.txt disallows are skipped, and the report lists them.
  • A Crawl-delay is honoured, up to 10 seconds between pages.
  • It never tries to get past bot protection, a firewall or a CAPTCHA: a page that is challenged is reported as blocked, never retried another way.

How often, and what it loads

A check runs when the customer starts one, or on a schedule they set: once a week, and again when they publish a new version of the site's Google Tag Manager container.

  • Up to 50 pages a check by default, from your sitemap or the home page's links, plus up to 20 pages of the customer's own journeys.
  • One page at a time, with at least 2 seconds between pages, and at most 15 minutes a check.
  • Each page loads with its scripts, images and tags, then the checker scrolls to the bottom and waits a few seconds.
  • The home page and two more load again after choosing reject, then accept, in your cookie banner.

Allow it

If your firewall or bot protection blocks the checker, allow visits whose user agent contains MyJourneyAnalyticsHiveCheck.

  • The customer who runs the check sees the exact address it visits from, under Allow Hive Check in their app, with steps for common bot-protection services.
  • If you can't let it in, they can run a guided check instead, browsing the site in their own browser.
Allowing the checker

Block it

To keep the checker out of your whole site, add these lines to your robots.txt. To block only part of it, disallow just those paths.

  • You can also refuse requests whose user agent contains MyJourneyAnalyticsHiveCheck at your firewall.
  • Blocking the checker doesn't affect your site's visitors or search engines.
robots.txt
User-agent: MyJourneyAnalyticsHiveCheck
Disallow: /

Questions about a visit?

Tell us the address of your site and when the checker visited, and we'll look into it.

Contact support