SmartValidate

SmartValidate is a prompt-based rule type within Taggun's Campaign Validation system. It lets an operator express one narrowly scoped, receipt-visible condition as a natural-language yes/no question, reducing the need to develop a bespoke rule for every campaign or promotion criterion.

📘

Current use and public examples

SmartValidate is in production use by Taggun customers. Taggun has not yet publicly documented specific customers' production implementations or use cases. The credit-card-payment example below is a generic illustration, not a description of a particular customer deployment.

Availability

📘

Availability: SmartValidate is part of receipt validation on the Advanced plan and above. Enable Campaign Validation and SmartValidate in your account Feature Settings when they are available on your plan. See Plans & Feature Access.

When To Use SmartValidate

Use the structured Campaign Settings Reference fields when they directly represent the requirement: dates, merchants, products, quantities, balances, or fraud checks.

Use SmartValidate when the campaign instead needs one narrow, binary condition that can be answered from evidence visible on the receipt. For example:

Does this receipt show payment by credit card?

SmartValidate is not a synonym for Campaign Validation, a generic document classifier, or a substitute for the structured fields. Avoid broad “anything visible” claims and compound questions that combine several business rules.

Configure a Prompt

Add one to three prompts under smartValidate.prompts when you create campaign settings. Each prompt contains:

• question — the yes/no question to answer from the receipt;
• example — an object with one clearly named boolean output key; and
• skip — optional; when true, the answer can be returned without adding the output key to the validation checks or affecting successful.

This generic example asks whether payment by credit card is shown:

curl --request POST \
     --url https://api.taggun.io/api/validation/v1/campaign/settings/create/payment-check-2026 \
     --header 'accept: application/json' \
     --header 'apikey: YOUR_API_KEY' \
     --header 'content-type: application/json' \
     --data '
{
  "smartValidate": {
    "prompts": [
      {
        "question": "Does this receipt show payment by credit card?",
        "example": { "is_credit_card": true },
        "skip": false
      }
    ]
  }
}
'

For every field and rule type, see Campaign Settings Reference.

Read the Result

When you validate a receipt, the configured output key and boolean answer appear under smartValidate. When skip is false, the same key appears in either passedValidations or failedValidations and contributes to successful.

{
  "successful": true,
  "failedValidations": [],
  "passedValidations": ["is_credit_card"],
  "smartValidate": {
    "is_credit_card": true
  }
}

Implementation Guidance

• Ask one specific true/false question about evidence the receipt can show.
• Use a structured rule instead when a documented campaign field already covers the condition.
• Test representative receipts before using the result in a customer workflow.

Need something not covered here? Contact [email protected] — see Contacting Support.