For AI translation tools: which language pairs and countries bring paying customers.

01How they sell

• UsageWords or characters translated, billed per document or metered on API plans; one catalog job can be a single large charge.
• SubscriptionMonthly plans with a word allowance for teams who translate every week, and website translation plans priced by languages.
• One-offA single document paid at upload, such as a PDF or a contract, by someone who may never need another.

02Payments it reads

• PaddleA common choice when buyers are businesses across Europe and Asia who need VAT handled; transactions, renewals and adjustments are read.
• StripePer-document Checkout payments and metered API subscriptions, read with refunds and chargebacks.
• Lemon SqueezyUsed for word packs and plans by small teams; orders and subscription invoices are read.

03Where buyers come from

• Language-pair searchesSearches like translate a German PDF to English land on pair pages; the page breakdown shows which pairs bring revenue.
• Search in other languagesLocalized landing pages draw people searching in their own language; the country breakdown shows where those buyers are.
• CMS and design pluginsIntegrations listed in a CMS or design tool's directory send users who arrive from that listing's page.
• Subtitle tutorialsCreators learning to add subtitles in other languages arrive from video tutorials, often for one project first.

04What Tally answers

1. Which countries pay, and which only visit?

   The country breakdown puts revenue beside visitors on every row, so a market full of curious visitors and few payments stands out from one that buys.

   Sources with revenue

2. What does a business buyer look at before the first big job?

   The visitor list shows where each visitor is, their latest source, pages and engaged time; unfold a customer to read every visit before their first payment.

   Visitors and journeys

3. Which channels bring customers who come back?

   Lifetime value groups customers by first source with repeat rate and average lifetime revenue, so channels that send one-document buyers stand apart from those whose customers return each month.

   Lifetime value

4. How many visits does a team take before buying a plan?

   Path to purchase gives visits and pages before buying, the median time to purchase and the share who buy on their first visit.

   Path to purchase

5. Can we watch a launch in a new language market?

   Live shows who's on the site right now on a globe or a flat map, so a launch in a new country can be watched as it lands.

   Live

05Numbers worth watching

Revenue by source

Revenue behind each source, country and landing page, the main way to rank language pairs and markets.

Repeat rate

The share of customers who paid more than once, which separates single-document buyers from teams with steady work.

Visits before buying

Visits before buying; business buyers trying a sample document first push it up.

06An example

07Setting up

1. PaddlePass tally_visitor_id in customData when the upload page opens Paddle checkout for a single document.
2. Any HTML siteKeep the tag on every language version of the site, so each localized page shows in the breakdown with its revenue.
3. Send tally('upload') when a file goes up; the goals view then counts uploads and the revenue of the visitors who made them.

08Questions

• We price in euros, yen and dollars. How is revenue added up?

  Every payment is converted to US cents at the European Central Bank rate for its day, without tax, so all currencies sum into one figure you can compare by country.

• Does Tally count visitors to our customers' translated sites?

  No. Those visits belong to your customers' sites. Tally counts visits to your own pages and reads the payments for your plans.

• Can we see which language versions of our own site sell?

  Yes. Each localized page is its own row in the page breakdown, with the revenue of visitors who landed there.