More in Getting started
- Install TapCub on your website
- Add a website, app or mini-program
- How do I add TapCub to WordPress?
- How do I add TapCub to Shopify?
- Where do I paste the TapCub tracking code?
- Can I install TapCub with Google Tag Manager?
- How do I track a React, Vue or Next.js app?
- How do I check that TapCub is collecting data?
- Why does TapCub show no data after I installed it?
- What is a site, and how many can I add?
- Which time zone should I pick for a site?
- Which domains do I need to register?
- How do I keep my own visits out of the reports?
- Why does my visitor count differ from Google Analytics 4?
- Can I run TapCub alongside Google Analytics 4?
- How do I move my goals and events from GA4?
- Can I import my historical data from GA4?
- How do I add TapCub to Squarespace?
- How do I add TapCub to Wix?
- Which Content Security Policy rules does TapCub need?
- Do ad blockers block TapCub?
- How do I send events from my server?
- How do I install TapCub on React?
- How do I install TapCub on Nuxt?
- How do I install TapCub on Vue?
- How do I install TapCub on Next.js?
- How do I capture a HAR file for TapCub support?
- How do I create and manage API keys?
- How do I send events with the HTTP API?
- All guides in this category
Still have a question?
Could not find it? A person reads every message, usually within a few hours on business days.
Chat with usAnswered step by step on their own pages:
The one-week plan
Migrating analytics is mostly about trust, not data transfer. Historical reports stay where they are; what moves is the report your team opens each morning. The safest way is to run both tools for a week:
- Day 1 — install. Add the TapCub snippet next to your existing tag. Follow the install guide. Do not remove anything yet.
- Days 2–5 — compare. Open both tools each day and compare the three numbers below. Write down the ratio, not the difference.
- Day 6 — recreate goals. Build the goals and events your team actually reads. Usually there are fewer than ten.
- Day 7 — switch. Make TapCub the link people open. Keep the old tag for one more month as a fallback, then remove it.
Compare definitions, not totals
Totals from two analytics tools never match exactly, and that is not a defect in either one. They count different things under similar names. Before you compare, line up the definitions:
| Metric | What differs | What to compare |
|---|---|---|
| Visitors | Cookie-based tools count a device with a cookie; TapCub counts a daily or site-level pseudonym without cookies, and excludes recognized bots by default. | The trend shape week over week. Expect TapCub to be lower when the old tool counted bots, higher when cookie consent blocked the old tag. |
| Sessions | Both split on idle time. TapCub defaults to 30 minutes and a 24-hour cap, both adjustable. | Sessions per visitor. It should be within a few percent. |
| Pageviews | Closest metric. Differences come from blocked scripts and single-page-app route events. | Top 10 pages by share. The ranking should match. |
| Bounce rate | Engagement-based tools call a session engaged after 10 seconds; TapCub counts a bounce as one pageview with no event. | Direction by channel, not the absolute number. |
Visitor totals are the number most likely to differ. The blog post Why UV never matches walks through every reason with examples you can show your team.
UTM and ad click IDs
UTM parameters need no mapping. TapCub reads utm_source, utm_medium, utm_campaign, utm_term and utm_content exactly as you already tag links, and keeps them as separate breakdowns under Web analyticsSourcesUTM.
Ad click IDs are read automatically for 14 platforms, including Google Ads, Meta, TikTok, Microsoft Ads and the four largest Chinese ad networks. Clicks with gclid, msclkid or bd_vid are classified as paid search without any setup. The raw ID is hashed before it is stored.
Channel groupings are different from the tool you are leaving. If your team relies on a custom grouping, recreate it under ConfigurationWeb settingsChannel rules — your rules win over the defaults. Details are in Sources and UTM.
Map goals and events
Do not try to recreate every conversion event on day one. List the goals someone opens weekly and recreate only those:
| In your current tool | In TapCub |
|---|---|
| Destination / page goal | A page goal under Web analytics › Goals: exact path, prefix or wildcard. |
| Event-based conversion | An event goal on an event name, optionally with one property condition. |
| Purchase with value | An event goal with revenue enabled, or a server-side event for order amounts you need to be exact. |
| Funnel / path exploration | A funnel in Insights › Behavior, 2–20 steps, window up to 180 days. |
| Audience | A segment in Insights › Users. |
Goal conversion rates in TapCub divide by distinct visitors, not sessions. If your old report divided by sessions, the percentage will look different while the count matches.
Cutover checklist
- Snippet is on every template, including landing pages built outside the main CMS.
- Hostnames for all domains and subdomains are registered.
- UTM links in running campaigns use the same parameters they always did — nothing to change.
- Weekly goals are recreated and have shown data for at least two days.
- Team members are invited with the right role (see roles).
- Bookmarks and dashboards point to TapCub.
- Old tag removed after the fallback month, and its consent banner entry updated.
Old data does not need to move. Keep read access to the previous tool for year-over-year questions; TapCub keeps your new data for 6 months on Free, 12 months on Pro and 24 months or more on Max and Ultra.
Did this answer your question?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.