Your First 30 Days

Taggun's self-service signup starts on the plan you choose. The first 30 days or first 1,000 scans, whichever comes first, are free; when either limit is reached, the selected plan becomes paid and billing starts. Use that free period to prove Taggun on your documents and prepare your integration. This page is the map; each step links to the page that does the work.

👍

The first decision: extraction or validation?

Running a promotion or campaign with qualifying rules? Use the validation endpoints — start with Receipt Validation Fundamentals. Receipt Validation is available on Advanced plans and above; select or upgrade to Advanced in the account dashboard and enable Campaign Validation in Feature Settings. Other supported receipt and invoice workflows — such as expense tools, cashback matching, and receipt or invoice data capture — use the extraction endpoints.

Before You Scan Anything: Define "Good"

Write down three things — they turn "playing with the API" into an evaluation you can put in front of stakeholders:

1. The fields you need. Check them against Data Fields That Taggun Extracts.
2. Your baseline. What does your current process — manual review team, incumbent OCR, nothing at all — get right, and what does it cost?
3. Your bar. Headline accuracy numbers don't transfer between document mixes; the number that matters is accuracy on your receipts, from your countries and merchants, measured against your baseline.

Week 1 — Prove It on Your Documents

1. Sign up and get your API key. The Quick Start takes about five minutes.
2. Switch on the features you need now — not on day twenty. Feature settings are self-service at taggun.io/account when your plan includes them; contact [email protected] if a control is not available or you need a pilot outside your current plan. See Plans & Feature Access.
3. Run a small smoke set in the playground. Use Upload File (verbose) to check authentication, request shape, and obvious field coverage.
4. Build a representative labelled evaluation set. Include your production countries, merchants, document types, image quality, and edge cases. Size it for the decision and variation you need to measure; a fixed document count is not a guarantee of statistical adequacy. Test With Your Own Receipts covers the test design, and structured pilots are available for larger-volume evaluations.
5. Score the results against the fields and bar you wrote down. See Understanding Your Results.

Week 2 — Make the Integration Decisions

Four decisions shape your build. All of them are easier to make now than to retrofit later:

Validating for a campaign? Create a test campaign now and submit known-good and known-bad receipts against it — see the Campaign Settings Reference and Validating Receipts.

Weeks 3–4 — Test Like It's Production

• Batch historical receipts with known outcomes and compare Taggun's results against what your process actually decided.
• Use real fraud, not fakes you make. A receipt you doctor yourself tests one technique; real confirmed fraud from past campaigns tests the patterns fraudsters actually use.
• Report what's wrong. Contact support with the email attached to your account, the affected trackingId when returned, the sample receipt or document when safe to share, and a clear description of the issue. See Contacting Support.
• Evaluating at volume? We run structured pilots — batch runs over your historical data with results reviewed together. Email [email protected].

Before Day 30 or 1,000 Scans

• Check plan fit. Scan volumes and feature tiers are on the pricing page. Campaign-based and seasonal pricing exist — contact us rather than forcing a fit.
• Know the mechanics. The selected plan becomes paid and billing starts as soon as either 30 days or 1,000 scans is reached; it does not wait for both limits.
• Run the go-live checklist in Performance & Response Times, and re-check Usage Limits against your launch volume.

Where Next

• Test the API on your documents — Test With Your Own Receipts
• Inspect the broader extraction response — Upload File (verbose)
• See what Taggun can extract — Data Fields That Taggun Extracts
• Validate receipts against campaign rules — Receipt Validation Fundamentals

Stuck at any step? Contact [email protected] — see Contacting Support.