For AI chatbot makers: which searches and integrations bring businesses that stay.

01How they sell

• SubscriptionTiers sized by conversations or messages a month, so a customer climbs a tier as its own traffic grows.
• UsageOverage on messages above the tier's allowance, billed at the end of the cycle on the same subscription.
• FreemiumA trial bot with a message cap, trained on the buyer's own help center, so the decision rests on how it answers their customers' questions.

02Payments it reads

• StripeTiered subscriptions with metered overage; Checkout, invoices and plan changes are read, chargebacks included.
• PaddlePicked when many customers are businesses abroad that need proper tax invoices; transactions, upgrades and adjustments are read.

03Where buyers come from

• Comparison searchesSearches for an alternative to a big help-desk bot bring support leads mid-switch who read pricing closely; path to purchase shows how many visits they need.
• Integration listingsA listing in the Slack Marketplace, Zapier or a CRM's directory sends teams already on that tool, and the referrer shows which listing it was.
• AI directoriesDirectory visitors poke at the demo bot and leave; revenue per visitor tells apart listings that bring buyers from ones that bring browsers.
• Agency partnersAgencies that build bots for clients come back with each new client, which shows in their repeat rate.

04What Tally answers

1. What did a new account read before choosing a plan?

   The visitor list shows where each person is, their latest source, pages, engaged time and what they paid. Unfold a customer and the journey lays out every visit before the first plan.

   Visitors and journeys

2. Do accounts from integration listings stay longer?

   Lifetime value gives each first source its customers, lifetime revenue, renewals and repeat rate, so listing-driven accounts can be set against search-driven ones after a few cycles.

   Lifetime value

3. Where do trials stall before the bot is trained?

   Session replay, off until you switch it on and with inputs masked, plays back visits to your onboarding pages, so you can watch where a trial stops before the first answer.

   Session replay

4. Which comparison post brought paying teams?

   Break revenue down by page and each comparison post's row carries the revenue of the visitors it brought, next to its visit count.

   Sources with revenue

5. A customer disputed a charge. Which channel did they come from?

   A chargeback is tied to the payment it reverses, so its receipt shows that sale's visits and credited source. Stripe and Paddle report chargebacks; Lemon Squeezy doesn't.

   Receipts

05Numbers worth watching

Renewals

Renewals by first source: a chatbot bought during a ticket surge and dropped when it passes shows here first.

Conversion

Paying visitors over all visitors per channel; integration listings and comparison posts often differ sharply on it.

Revenue by source

The money behind every source, which ranks partner listings by what they earned rather than by installs.

06An example

07Setting up

1. WebflowOn a Webflow marketing site, the tag goes in the site-wide custom code head, so pricing and comparison pages carry it.
2. StripeWhen the trial ends and your app opens Checkout, include tally_visitor_id in metadata and subscription_data, so later tier changes keep the link.
3. Call tally('identify', { email }) when a trial account is created, so a plan bought weeks later from the dashboard links by email.

08Questions

• Does Tally count chats on our customers' websites?

  No. The snippet runs on your own site; the widget on a customer's site belongs to their traffic, and its conversations aren't sent to Tally.

• Some customers pay through a commerce platform's app billing. Are they counted?

  Not as revenue. A platform that bills its merchants for your app pays you out itself. Only plans charged in your own Stripe, Paddle, Lemon Squeezy or Polar account are read.

• Can we get a Slack message for every new plan?

  Yes. Sale alerts post to Slack, Discord, Telegram, email or a webhook once the payment is linked, with the credited source in the message.