Amplitude vs TechTouch in 2027: Analytics or In-App Guides

Amplitude vs TechTouch: the short answer

Amplitude vs TechTouch is mainly a choice between measuring what users do and changing what they see, and the two products sit on opposite sides of that line. Amplitude is a product analytics platform that records events from your product and reports on behavior. TechTouch, operated by Techtouch, Inc., is a digital adoption platform (DAP) that places operation guides on top of web systems without changing their code. Constellation Research says DAPs "help guide people directly within the context of the work task or process they are performing," according to Constellation Research (2026).

TL;DR: For an English-language small SaaS team, start with Amplitude. Consider TechTouch only if your operators work in Japanese and you can buy from a Japanese vendor on a written quote. Neither product replaces a workflow automation layer.

One scope change matters before you compare. Amplitude's May 5, 2026 announcement calls its Statsig deal "a strategic partnership" and says "Amplitude will take on Statsig's brand and customers," according to Amplitude (2026). That brings feature flags and experimentation into Amplitude's scope, so its side of this comparison is wider than analytics alone. We found no sign that TechTouch has been renamed, merged or discontinued; its Japanese site footer names Techtouch, Inc. as the company.

Market size is context, not a decision factor. Japan DAP market: ¥6.59 billion in FY2024, up 66% according to IT Leaders (2025). That article reports Information-Technology Research Institute (ITR) data from a survey of 35 domestic vendors and names no vendors. Techtouch's own press material says ITR ranked it first by DAP vendor revenue share. We treat that as a vendor claim, because the independent article does not confirm it.

Our read: a bigger category does not tell a small team which tool to buy. The useful questions are whether your problem is measurement or guidance, and whether the vendor serves your team's language.

Key Takeaways

• Amplitude and TechTouch do different jobs. Amplitude measures product use across events, funnels and retention, while TechTouch adds on-screen guidance to browser-based systems.

• Amplitude publishes a Free plan at $0 and a Plus plan that starts at $0, then quotes Growth and Enterprise. TechTouch publishes no prices on its own site.

• TechTouch's AWS Marketplace listing says the product is for Japanese customers only and that vendor support is in Japanese. For an English-speaking US team, that is the deciding constraint.

• Amplitude's Guides and Surveys lets you test in-app guidance inside the analytics product you may already be evaluating, with a small guide allowance on the free tiers.

• A DIY stack in Zapier, Make or n8n can run the same flows, but you own retries, deduplication, access and maintenance.

• Before comparing totals, ask TechTouch for a written quote that states the pricing unit, the contract term and what a guide edit costs.

How we evaluated these tools

We weighted seven criteria by how much they decide a small SaaS buyer's choice. The weights are our own judgment, not vendor or market data, and they are shown so you can change them. The "max contribution" column is each weight multiplied by a perfect score of 5, which shows how far each criterion can move a total on a 5-point scale.

The facts in the sections below come from vendor pages, a review site, a trade article, a research firm and a marketplace listing. Each is cited where it is used. Sentences that express our judgment are marked "Our read."

We could not open G2 or Gartner Peer Insights during this review, so we have no independent user rating to report for Amplitude. For TechTouch, the independent rating we could open is on ITreview, covered below.

What each product does on the same criteria

The table below is a map, not a scorecard. Amplitude's rows come from its own pricing and documentation pages. TechTouch's rows come from its Japanese site, its AWS listing, its ITreview product page and Macnica's English page. Where we found nothing, the table says so rather than guessing.

Our read: on the first criterion, the two products are not substitutes. Amplitude answers "where do users stall?" TechTouch answers "how does this operator complete this screen?" Amplitude does ship in-app guides, so a team that wants both measurement and guidance from one vendor should test Amplitude's Guides first, before buying a second product.

Pricing: what is public and what is quote-based

Amplitude publishes its entry tiers. Plus plan: starts at $0 with 2M events free according to Amplitude (2026). The same page lists the Free plan as "2M Events/month forever" with no credit card, and says the Plus plan requires a card. Growth and Enterprise are priced on "Event based pricing" through a sales contact, and the page publishes no monthly amount for either plan.

TechTouch publishes no prices, plan names or pricing page on its Japanese site. The site offers a contact form and a trial, so TechTouch's price is quote-based. Its AWS Marketplace listing, which the vendor sells and limits to Japanese customers, says pricing depends on the duration and terms of the contract. TechTouch refund window: 7 days after contract according to AWS Marketplace (2026). The same listing describes a 12-month term and shows a per-unit figure in US dollars without saying what the unit covers, so we leave that figure out.

Pricing checked November 13, 2026.

Plan rows come from Amplitude's pricing page. The TechTouch row comes from the AWS Marketplace listing. Public numbers do not support a total-cost comparison. For Amplitude they cover the free allowance and the Plus starting point, but not the cost of events above those tiers. For TechTouch they cover nothing beyond a contract term.

Vendor profiles: best fit, limits, implementation and evidence

Amplitude

Best fit: a product or growth team that has an engineer able to send events and a specific question, such as where new accounts stop before their first useful action. Amplitude's HTTP V2 endpoint takes a POST at https://api2.amplitude.com/2/httpapi, and each event needs an event_type plus a user_id or device_id, per Amplitude's HTTP V2 documentation.

Limitations: Amplitude is an analytics product first. Its guide allowance is small on the entry tiers: the guide docs list one guide on Free and Plus, with add-ons for more, per Amplitude's guide documentation. User IDs must be at least 5 characters unless you override the min_id_length option, and Amplitude removes shorter IDs from the event, so a sloppy ID scheme loses data silently. Growth and Enterprise require a sales quote.

Implementation: plan on engineering time for event tracking before anyone builds a funnel. Guides are available on all plans, and the guide types are tours, announcements, checklists, carousels, banners, tooltips and card embeds. Our read: a product lead should approve every guide before it ships, the same as any other change to the user experience.

Evidence: Amplitude is Nasdaq-listed as AMPL and published its Q3 2026 results on November 4, 2026, per its Q3 2026 press release. That tells you the vendor is public and reporting, not whether its product fits your team.

TechTouch

Best fit: operations or customer-success teams that run browser-based internal systems, such as expense, ERP, HR or sales tools, in Japanese, and want guidance without writing code. Its Japanese site says guides can be created or edited without programming, and the AWS listing says it works with systems that run in a browser with no coding required.

Limitations: The AWS listing says "This product is Japanese customers only," directs customers outside Japan to a partner contact, and says vendor support is provided only in Japanese. One ITreview reviewer says the product runs as a browser add-on and has no iOS app support. Its generative-AI rating rests on a single review, so we do not treat that feature as proven. The product's analysis features are usage analysis and funnel-style views, and we found no event-level product analytics on its pages.

Implementation: guides overlay the existing web screen. The AWS listing says data integration can target guides by company unit, contract plan or individual user, and that the buyer must accept the vendor's EULA. Our read: a Japanese-speaking operator should approve each guide's wording before it goes live, because wrong text on a finance or HR screen is slow to fix.

Evidence: On ITreview, Techtouch's product page shows an overall TechTouch rating: 4.4 from 46 reviews according to ITreview (2026). The ITreview 2025 Spring ranking placed TechTouch in the top tier for the DAP category with a score of 4.6, according to ITreview's 2025 Spring ranking (2025). Those are user reviews, not market-share data. Macnica's English page describes TechTouch as "a domestically produced DAP compatible with LGWAN" and is mostly promoted for use with Box, which is a narrower use case than the Japanese site describes.

Who this is for

Who this is for: an owner or operations lead who must choose between measuring product use and guiding it, and who wants the answer before a sales call.

Red flags: choose Amplitude only if an engineer can send events, since without that it sits unused. Do not choose TechTouch if your team needs English-language support or a published price. Do not expect Amplitude's Guides to replace an operations DAP for internal Japanese systems.

Decision checklist:

• Can you name the question in a product metric, such as a step that loses users? If yes, evaluate Amplitude first.

• Do your users or your support staff need Japanese? If yes, TechTouch goes on the shortlist. If no, drop it.

• Do you need a dollar price before the first call? Amplitude's Plus starting point is public. TechTouch's is not.

• Who edits guides, and who signs off on the wording?

• Will you need your data outside the vendor? Confirm the export or API route on your plan before you buy.

Worked example: a 2.5 million event month

Take a hypothetical 10-person SaaS team that sends 2,500,000 events in one month. The Free plan covers 2,000,000 events per month, so 500,000 events (2,500,000 minus 2,000,000) fall above it and would need the Plus plan. Plus starts at $0, but the page publishes no price for events above the first 2M, so the monthly cost of those 500,000 events cannot be calculated from public figures. A quote is needed to price those 500,000 events. Every event still needs an event_type and a user_id or device_id, and every retry should reuse the same insert_id, because Amplitude ignores an event that repeats an insert_id from the past 7 days, per Amplitude's batching guide.

Where US Tech Automations fits next to DIY stacks

Zapier, Make and n8n can run flows like these, and when configured they keep run histories, retries and error branches, and they can produce an audit trail. The buyer still designs and owns the parts that fail quietly: deduplication, which is why Amplitude's own insert_id window matters; escalation when a step fails; access controls on the Amplitude credential; and maintenance when an event name changes. Building that in-house is possible, but it is an ongoing engineering job, not a one-time setup.

Here is a proposed, configurable workflow that could sit beside Amplitude, built with US Tech Automations. The trigger is a weekly schedule. The action pulls the prior week's counts for the signup-to-first-action steps from an Amplitude export or API route your plan supports, compares each step with the week before, and flags any step that falls by more than a threshold your team sets. The output is a short list posted to a shared channel. Prerequisites are that export route, a read-only credential and a named owner for the threshold. The review point is a product lead who decides whether any change ships, because this design reports and does not edit product settings or guides.

A second proposed US Tech Automations design covers the TechTouch side. The trigger is a user opening a back-office screen for the first time. The action selects a guide from a list an operations lead maintains, and the output is a log row recording which guide was shown to which user. Before this works, the team must confirm that TechTouch's data integration can target guides by user, company unit or contract plan, as its AWS listing describes, and that Japanese-only vendor support is acceptable. The review point is a Japanese-speaking operator who approves each guide's wording before it goes live.

When NOT to use US Tech Automations

A simpler tool wins in three cases. If you only need one product tour on your own app, Amplitude's Guides on the plan you already have, or your product's own onboarding, is less work than any workflow layer. If you only need to know which step loses users, Amplitude's analytics answers that directly and a custom flow adds nothing. If your operators only need Japanese-language guidance inside a browser-based system and you have no reporting need, TechTouch as a single purchase is simpler than a multi-step automation built around it.

Frequently asked questions

Can Amplitude replace TechTouch?

Partly: Amplitude's Guides can show tours, tooltips and checklists, but it is built around analytics, so use it to test guidance on your own product rather than to replace an operations DAP for internal systems.

Is TechTouch available outside Japan?

We found no public evidence that it is. Its AWS Marketplace listing says the product is for Japanese customers only and directs customers outside Japan to a partner contact.

What does TechTouch cost?

Its price is not published. Its Japanese site lists no prices, and its AWS listing says pricing depends on the duration and terms of the contract, so you need a written quote.

Does Amplitude have a free option?

Yes. Amplitude's Free plan is listed at $0 with 2M events a month and no credit card required, and Plus starts at $0 for its first 2M events but requires a card.

Do I need a developer to use Amplitude?

Yes for event analytics: each tracked event needs an event_type and a user_id or device_id, so someone must instrument the product before any funnel means anything.

What happened between Amplitude and Statsig?

Amplitude announced on May 5, 2026 that it would take on Statsig's brand and customers under what it calls a strategic partnership, and it said it would keep developing the current Statsig platform.

Conclusion

For most English-speaking small SaaS teams, start the evaluation with Amplitude. Treat TechTouch as a Japanese-language option that needs a written quote, Japanese-language support and a pilot run by Japanese-speaking operators before anyone signs. Check the export route, the data owner and the review points before any contract. To see how a proposed design would be configured for your stack, see how US Tech Automations configures this.