Tally

Finseo connects to Tally through the native webhook on each form. Add a "How did you hear about us?" question and an email field, point the webhook at your Finseo project URL, and every submission arrives pre-categorized. Finseo detects Tally's data.fields format, locates the attribution question by label, picks up the email automatically, and normalizes the free-text answer into channel buckets such as ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews. The email becomes a merge key, so a later Stripe payment, Pipedrive deal, or WooCommerce order is attributed back to the original AI source.

1. 01

   Lead source attribution

   Add "How did you hear about us?" to your demo request or contact form. Every submission tells you whether the lead found you through ChatGPT, Perplexity, Google AI Overviews, or another channel.

2. 02

   Signup attribution for SaaS

   Use a Tally form as your waitlist or onboarding survey. The answer and email are stored together, and the later payment from Stripe merges automatically within 90 days.

3. 03

   Post-purchase survey

   Embed a Tally form on your thank-you page or in the order confirmation email. Answers merge with orders from WooCommerce, Shopware, or Shopify via email.

4. 04

   Multilingual forms

   Run the attribution question in German, French, or any language. Map the field once under Attribution, Workflows and every future submission parses automatically.

5. 05

   AEO reporting

   See what share of form submissions name an AI engine over time and use it as a leading indicator for your Answer Engine Optimization (AEO) work in Finseo.

Tally is a popular free form builder for startups, agencies, and creators, and its forms often sit exactly where attribution matters: demo requests, waitlists, and checkout follow-ups. A self-reported "How did you hear about us?" answer is the most reliable way to catch AI search referrals, because ChatGPT and Perplexity visits usually show up as direct traffic in analytics. Finseo parses Tally payloads natively, so the question goes live in minutes without Zapier, Make, or field mapping, and the answers feed revenue attribution per AI engine.

1. 01

   Get your Finseo webhook URL

   In Finseo, click Connect on the Tally integration card, or open Attribution, then Set up attribution. Copy the webhook URL including the token.

2. 02

   Add the attribution question

   In your Tally form, add a question like "How did you hear about us?" and an Email field. Free text works best because Finseo normalizes the answers.

3. 03

   Connect the webhook

   Open the form, go to Integrations, then Webhooks, then Connect. Paste your Finseo webhook URL as the endpoint and save.

4. 04

   Submit a test response

   Fill in the form once with an answer like "ChatGPT". The response appears in Finseo within seconds, categorized into the AI Search bucket.

5. 05

   Map custom labels if needed

   If your question uses a very different label, open Attribution, then Workflows in Finseo and point the mapping at the right field. Future submissions parse automatically.

How does Finseo connect to Tally?

Through Tally's native webhook. Open your form, go to Integrations, then Webhooks, then Connect, and paste your Finseo project webhook URL as the endpoint. Tally POSTs every submission as JSON and Finseo parses the payload natively. No Zapier, Make, or custom code is required.

Through Tally's native webhook. Open your form, go to Integrations, then Webhooks, then Connect, and paste your Finseo project webhook URL as the endpoint. Tally POSTs every submission as JSON and Finseo parses the payload natively. No Zapier, Make, or custom code is required.

Do I need to map fields?

No. Finseo detects Tally's data.fields format, finds the attribution question by looking for labels such as "How did you find us?" or similar, and picks up the email field automatically. Only if your label is very different, for example in another language, do you map it once under Attribution, Workflows.

No. Finseo detects Tally's data.fields format, finds the attribution question by looking for labels such as "How did you find us?" or similar, and picks up the email field automatically. Only if your label is very different, for example in another language, do you map it once under Attribution, Workflows.

What happens to the answer text?

Finseo normalizes free-text answers into channel buckets. "ChatGPT", "asked an AI", or "Perplexity" land in AI Search buckets such as ChatGPT, Perplexity, Claude, Gemini, or Google AI Overviews, while "Google", "LinkedIn", or "a friend" go to their respective channels. You see the share per channel in the Attribution dashboard.

Finseo normalizes free-text answers into channel buckets. "ChatGPT", "asked an AI", or "Perplexity" land in AI Search buckets such as ChatGPT, Perplexity, Claude, Gemini, or Google AI Overviews, while "Google", "LinkedIn", or "a friend" go to their respective channels. You see the share per channel in the Attribution dashboard.

Can Tally answers be tied to revenue?

Yes. The respondent email is stored as a merge key. When a Stripe payment, Pipedrive deal, WooCommerce order, or Shopware order with the same email arrives within 90 days, Finseo attributes that revenue to the Tally answer, showing revenue per AI engine.

Yes. The respondent email is stored as a merge key. When a Stripe payment, Pipedrive deal, WooCommerce order, or Shopware order with the same email arrives within 90 days, Finseo attributes that revenue to the Tally answer, showing revenue per AI engine.

Why do submissions show the status parse_failed?

Finseo could not find an answer field by keywords, usually because the question label is unusual or in another language. Open the auto-created workflow under Attribution, Workflows and point the mapping at the right field. All future submissions from that form parse automatically.

Finseo could not find an answer field by keywords, usually because the question label is unusual or in another language. Open the auto-created workflow under Attribution, Workflows and point the mapping at the right field. All future submissions from that form parse automatically.

Why do responses have no email?

The form has no field of type Email, or it is optional and was left blank. Add an Email field to the Tally form and Finseo detects it automatically. Without an email, the answer still counts for channel share but cannot merge with later conversions.

The form has no field of type Email, or it is optional and was left blank. Add an Email field to the Tally form and Finseo detects it automatically. Without an email, the answer still counts for channel share but cannot merge with later conversions.

Does this work on the free Tally plan?

Webhooks are part of Tally's Integrations menu and are configured per form. Check Tally's current plan page for any limits, since Finseo does not add requirements of its own. All Finseo integrations, including Tally, are included on every Finseo plan without extra fees.

Webhooks are part of Tally's Integrations menu and are configured per form. Check Tally's current plan page for any limits, since Finseo does not add requirements of its own. All Finseo integrations, including Tally, are included on every Finseo plan without extra fees.

Is the Tally integration real time?

Yes. Tally sends the webhook immediately after a submission, and Finseo processes the payload and updates the Attribution dashboard within seconds. A test response you submit while setting up the webhook is visible in Finseo before you switch back to the browser tab.

Yes. Tally sends the webhook immediately after a submission, and Finseo processes the payload and updates the Attribution dashboard within seconds. A test response you submit while setting up the webhook is visible in Finseo before you switch back to the browser tab.