Head to head · Analytics events · October 2026 research run

Heap vs Woopra

Heap scores 53 (D) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments & pricing. Both do analytics events.

Which one, for what

Heap D

Good for An agent that records backend events or enriches user and account properties in a company's existing Heap project, or that files privacy deletions.

Ahead on

  • Schema & documentation, 57 against 45
  • Security & auth, 41 against 22
  • Maintenance & community, 63 against 9

Watch for

No query, export or definitions endpoint in the developer reference. Reading results needs the app, Heap Connect or the MCP server we couldn't read

Woopra E

Good for An agent that reads a company's existing Woopra reports, looks up or edits customer profiles, or exports raw sessions on a schedule.

Ahead on

  • Reliability, 80 against 72
  • Payments & pricing, 30 against 25

Watch for

Report endpoints run a report saved in the web app by report_id. No endpoint to define a query, funnel or segment was found in the reference

Score by category

CategoryWeight this runHeapWoopraEdge
Reliability16%207280Woopra +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25745Heap +12
Agent ergonomics13%16.24945Heap +4
Security & auth14%17.54122Heap +19
Payments & pricing10%12.52530Woopra +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8639Heap +54
Transparency & trust7%8.86461Heap +3
Negative events≤1500
Total53 · D44.4 · E

Facts side by side

FactHeapWoopra
KindHTTP APIHTTP API
VendorContentsquare (Content Square, Inc.)Woopra, Inc.
Hosted endpointhttps://heapanalytics.comhttps://www.woopra.com/rest/3.10
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
Price for analytics eventsnot published$999 per month (plan)
x402nono
LicenceProprietary service under Contentsquare's master services agreement. The React Native bridge and the Node client on npm are MITProprietary service under Woopra's terms of service. The browser tracker and the SDKs on GitHub are MIT, and the Node package is ISC
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-062026-03-16
Terms last updatedno date given2025-12-10
Privacy policy last updatedcouldn't be read2025-08-01
Customer content may train modelsyesnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity213 npm/wk415 npm/wk

Verdicts

Heap

Heap's server-side API suits an agent that records events. Limits are published, bulk calls take 1,000 items and track accepts an idempotency key. The API returns no analytics, and ingest calls carry no secret beyond the environment ID. Heap's help centre lists a Heap MCP article, which a bot check stopped us reading, so the MCP server is ungraded.

Woopra

Woopra's REST API returns saved Trends, Journeys, Retention and Attribution reports, profiles and raw session logs, with published limits of 300 calls a minute and 3,000 a day per project. A report must first be built in the web app, the tracking endpoints accept events without a secret by default, and no changelog or SLA was found.

Before you call either

Heap

  1. Send EU projects to https://c.eu.heap-api.com instead of https://heapanalytics.com. The path stays the same
  2. Pass one of identity or user_id on track, never both
  3. Set idempotency_key on every track event so a retry doesn't duplicate it
  4. Stay under 30 requests per 30 seconds per identity, or batch up to 1,000 events in one bulk call
  5. For deletion, exchange the app_id and API key of the Main Production environment for a token first. Any other environment ID returns Unauthorized

Woopra

  1. Ask the owner to build and save each report in the web app first, then pass the last path segment of its URL as report_id
  2. Authenticate REST calls with HTTP Basic, using the App ID and Secret Key from the Access Keys tab, against https://www.woopra.com/rest/3.10/
  3. Stay under 300 calls a minute, 600 an hour and 3,000 a day per project. A 429 carries no documented retry interval, so back off on your own schedule
  4. Reuse the snapshot ID from the first response when paging with offset, or pages past 1,000 records may not agree
  5. Send cookie or a cv_ identifier such as cv_email on every track call. Without one the event lands on a random profile that can't be identified later
  6. When reading /logs/export, delete the profile named in each type: "delete" line. The following lines log its data again under new_id

Questions

Which is better for AI agents, Heap or Woopra?

Heap scores 53 (D) on agent readiness against Woopra's 44.4 (E), and leads in 5 of 7 scored categories. Woopra leads on reliability and payments & pricing.

Do Heap and Woopra need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Heap and Woopra without installing anything?

Yes. Heap has a hosted endpoint at https://heapanalytics.com and Woopra at https://www.woopra.com/rest/3.10.

Other comparisons with Heap or Woopra

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.