Weigh ticket
Example
31% tare
- GrossRecords your contract counts
- 412,300
- Cannot be emailed
- 61,845
- Duplicates
- 12,369
- Test and junk
- 8,246
- No activity in 12 months
- 45,353
- TareRecords nobody can use
- 127,813
- NetPeople you can reach
- 284,487
A Marketo contract is sized by the people in your database. Tare counts the ones no campaign can reach: unsubscribed, bounced, duplicated, junk, and long gone.
The file is read in this browser tab and is never uploaded. No export to hand? .
Weigh ticket
Example
31% tare
An example with invented numbers. Yours prints here.
Tare is the weight of the container. On a scale you subtract it to find out what you are actually carrying. Here it is every record that takes up room in your database and can never answer a campaign.
Each record is counted once, in the first group it falls into, so the lines on the ticket add up.
Tare finds the columns by their names and shows you what it matched. A column you leave out is not an error. That group is left off the ticket and the ticket says so.
Nowhere. This page is a set of plain files with no server behind it. Your browser opens the export, counts it in memory, and forgets it when you close the tab. Tare keeps totals only. Names are read to spot junk, such as a first name that is a link, and are not kept.
You can check this yourself: load the page, disconnect from the internet, then run it.
The export is the database. It says nothing about what runs on top of it: programs that have sat idle for a year, forms that no page uses, custom fields that no smart list or form reads, smart lists that repeat each other, and campaigns still running inside archive folders.
The full audit reads those through a read-only API user that you create and can switch off at any time. You get a written report with a fix list, in the order worth doing.