Quick answer
UA stands for three things: Universal Analytics (Google's former analytics, which stopped processing data on 1 July 2023 or 2024), user acquisition (getting new users, measured by cost per install or per signup) and user agent (the string a browser or bot sends to identify itself).
What does UA stand for?
UA is an abbreviation with three common meanings in analytics and marketing, and the right one depends on where you read it. In a reporting or migration conversation it usually means Universal Analytics, Google's former analytics generation. In app marketing it means user acquisition, the work of getting new users to install or sign up. In web logs and technical documentation it means user agent, the string a browser or bot sends to say what it is.
The three never mean the same thing, and mixing them up produces real mistakes: a "UA report" can be a retired Google property, a marketing spend report, or a list of browser strings. Use the table below to decide which one you are looking at.
| Meaning | Where you see it | What it measures or describes | Typical sentence |
|---|---|---|---|
| Universal Analytics | Migration plans, old dashboards, UA-XXXXX-Y property IDs | Hits sent to a Google Analytics property | "Our UA data ended in July 2023." |
| User acquisition | App marketing, growth and finance reports | New users gained, and what each one cost | "UA spend rose 20% last month." |
| User agent | HTTP requests, server logs, bot lists | Browser, operating system, device or crawler identity | "Block that UA in robots.txt." |
UA as Universal Analytics: the dates that matter
Universal Analytics was the analytics generation that came before GA4. Its property IDs started with UA-. Google's own help page on the shutdown gives the dates:
- 1 July 2023: standard Universal Analytics properties stopped processing new hits. Universal Analytics 360 properties without a current 360 order did not get an extension and stopped on the same day.
- 1 July 2024: 360 properties with a current order, which had received a one-time processing extension, stopped processing. This is also the date after which previously processed data could no longer be accessed in the interface, the API or product integrations.
A quick calculation shows how long the overlap was: from 1 July 2023 to 1 July 2024 is 366 days (2024 is a leap year), so a standard property that never exported its history had a one-year window to do it, and that window has closed.
What this means today: if a document says "UA conversion rate", check its date. If it covers a period before July 2023 it came from Universal Analytics, and its definitions of a session and a conversion differ from the event-based model that replaced it, so a before-and-after comparison across the switch is not like for like. See the GA4 migration checklist for what to carry over.
UA as user acquisition: the numbers
In app and subscription businesses, user acquisition covers every activity that brings in new users: paid campaigns, referrals, store search, partnerships. Teams report it with a handful of ratios.
Sample data: an app spends $6,000 on one campaign in a month, which produces 2,000 installs. A quarter of the installers (25%) complete registration.
| Metric | Formula | Calculation | Result |
|---|---|---|---|
| Cost per install (CPI) | spend ÷ installs | 6,000 ÷ 2,000 | $3.00 |
| Registered users | installs × registration rate | 2,000 × 25% | 500 |
| Cost per registered user | spend ÷ registered users | 6,000 ÷ 500 | $12.00 |
The point of the second and third rows: a cheap install is not a cheap user. A campaign with a $3.00 install cost and a 25% registration rate is paying $12.00 for each person who actually signs up, so compare campaigns on the cost of the outcome you care about, not on the first step.
Store consoles define the first steps precisely. Google Play's help page, for example, counts a store listing visitor as a user who visited the listing and did not already have the app installed on any device, and an acquisition as a user who visited and installed the app. Know which definition your report uses before comparing numbers across tools.
UA as user agent: what the string tells you
A user agent is the software making an HTTP request, and the User-Agent header is the text it sends to identify itself. RFC 9110 says the field contains information about the user agent originating the request, which servers use to identify the scope of interoperability problems, to tailor responses, and for analytics about browser or operating system use. Anyone can set the header, so it is a claim, not proof. Details are in the user agent glossary entry.
Take this string, which is the shape Chrome sends on Android since user-agent reduction:
Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Mobile Safari/537.36
Parsing it gives: platform token Linux; Android 10, device token K, browser Chrome, major version 143, minor parts 0.0.0, and the word Mobile, which marks a phone. Two things stand out. The Android version (10) and the model (K) are fixed placeholder values, so they say nothing about the real device. And the Chrome minor version is always zeros. MDN documents this reduction as a privacy measure against fingerprinting; servers that need more detail must ask for User-Agent client hints.
Practical rules for reading a user agent:
- Trust the browser family and major version; do not trust the device model.
- Treat
Mobileas a hint for layout, not as proof of a phone. - Never block or allow a crawler on the string alone. Search engines and AI companies publish IP ranges or DNS checks because the string can be copied.
How to tell which UA you are looking at
Use this decision rule on any mention of "UA":
- A property ID like
UA-12345-1, or a date before July 2024? It is Universal Analytics. - Cost, installs, CPI, channels or a growth team? It is user acquisition.
- A long string with
Mozilla/5.0, or a log file, header or bot rule? It is user agent. - None of the above? Ask. Do not guess, because the three readings lead to different actions: a migration, a budget review, or a bot rule.
Where each meaning shows up in TapCub
Suppose you are the person who has to answer "what is going on with UA?" for a website that also runs paid campaigns.
- User agent. In Web analytics › Audience, the place and device list shows device, browser, screen, language and network per visitor group. TapCub reads brand and model from the browser's user agent, so reduced strings like the one above limit how specific the device can be. Use browser family and screen size, not the model name.
- Bots. In Web analytics › Bots, requests whose user agent and other signals mark them as crawlers are counted separately, so they do not inflate visitor counts.
- User acquisition. In Web analytics › Sources, the Channels, Referrers and UTM tabs show where new visitors come from, with sessions and conversions per channel. Visits that carry ad click IDs such as
gclidare classified as paid search by default. To compare spend with outcomes, import costs in All-platform analytics › Business › Channel ROI, which then shows cost per click, cost per acquisition and return on ad spend. - Universal Analytics. TapCub cannot import Universal Analytics or GA4 history one to one, because the two sides define metrics differently. Keep any exported reports you still hold next to TapCub's data and mark the switch date on a chart with Configuration › Annotations.
TapCub does not buy traffic or run campaigns. It only measures what happens after the click.
Sources
- Google Analytics Help, Universal Analytics will stop processing data.
- IETF, RFC 9110: HTTP Semantics, section 10.1.5 User-Agent.
- MDN Web Docs, User-Agent header.
- Google Play Console Help, Understand and grow your app's user base.
Was this explanation clear?
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.

Customer Experience Consultant
Writes about live chat, visitor conversations, and self-service, sharing practical ways to make customer communication clearer and more effective.