Setting Up Purchase Validation Campaigns
Purchase validation campaigns let you define receipt rules once, then validate each submitted receipt against those rules. A campaign can check receipt dates, merchants, product line items, product codes, balance owing, duplicate receipts, tampering signals, digital receipt signals, and Smart Validate prompts.
Start with the fundamentals: Receipt Validation Fundamentals
Access
To enable Campaign Validation on your account with the Advanced plan or higher that was created from June 2026, enable Campaign Validation through the Taggun account page: https://www.taggun.io/account#/. Otherwise contact Taggun support.
Campaign Validation Workflow
| Step | Page | Use it to |
|---|---|---|
| 1 | Create Campaign Settings | Define the rules for a campaign ID. |
| 2 | Validate Receipts | Submit receipt files or receipt URLs against a campaign. |
| 3 | Manage Campaign Settings | List, retrieve, update, or delete campaign settings. |
Integration Flow
- Choose a stable
campaignId. - Create campaign settings with
POST /api/validation/v1/campaign/settings/create/{campaignId}. - Submit receipts to either:
POST /api/validation/v1/campaign/receipt-validation/filePOST /api/validation/v1/campaign/receipt-validation/url
- Read the
successful,failedValidations, andpassedValidationsfields in the validation response. - Use the management endpoints to retrieve, update, list, or delete campaign settings as your campaign changes.
Core Concepts
| Concept | Meaning |
|---|---|
campaignId | Your identifier for the validation campaign. It is used in the settings endpoint path and in each validation request. |
| Campaign settings | The rules that receipts are checked against. These include optional sections for date, merchant names, product codes, product line items, balance owing, fraud detection, and Smart Validate prompts. |
referenceId | Your identifier for a submitted receipt. Use the same referenceId when resubmitting the same receipt; submissions with the same referenceId are not picked up by duplicate checks. |
userId | Optional identifier for the end user submitting the receipt. It helps duplicate checks compare receipts for the same user. |
| Validation keys | Machine-readable strings in passedValidations and failedValidations that identify which checks passed or failed. |