Metadata Logic

What is Metadata Logic?

Metadata logic lets you use hidden or system-provided data to control question behavior—such as visibility, required status, or logic branching. You can also prompt the participant to provide metadata only if it’s missing from your integrations (e.g., CRM, API, CSV).

Purpose

  • Embed metadata like transaction ID, order reference, timestamps, or user IDs
  • Use metadata to drive logic (e.g., only ask a question if OrderStatus is “Failed”)
  • Collect missing metadata from users if it’s not pre-supplied
  • Display participant-specific data in read-only mode when relevant

When to Use

  • System-integrated surveys where part of the participant data is passed via the survey link or backend
  • Hybrid surveys where partial metadata exists and needs manual fallback
  • When you want to filter, segment, or personalize the experience using metadata conditions

Best Practices for Metadata Fields

We recommend choosing MCQ or Open-Ended formats based on your use case:

Type When to Use
MCQs When you need segmentation or filtration based on fixed categories (e.g., Region, Channel, Role)
Open-Ended For capturing data that is unique, dynamic, or numeric in nature and not suitable for dropdowns

Common Examples:

  • Order Numbers
  • Transaction IDs
  • Timestamps
  • Dynamic Reference Codes
  • Email or Mobile Number (if not already passed via link)

Metadata Visibility Settings

Each metadata field in Zykrr supports the following configurations:

Option Function When to Use
Ask if not pre-populated Show the question only if its value hasn’t been passed via survey URL, file upload, or integration backend Use to collect fallback metadata
Never ask Always hide the question from the user; used only for embedding and logic behind the scenes Use when system always provides the data
Display in read-only mode Show the data to the participant but disable editing Use to transparently display ID fields like transaction ID, user ID
Always ask Ask this question every time (default setting if no logic is enabled) Use when data must be user-entered or confirmed every time

Dynamic logic can override static-logic.
For example, even if a metadata field is hidden by default, it can still be displayed if triggered by dynamic Display Logic rules.

How to Configure in Zykrr

  1. Create a metadata question as an MCQ or Open-Ended type.
  2. Under Visibility Settings, choose one of the modes:
    • Ask if not pre-populated
    • Never ask
    • Display in read-only mode
    • Always ask
  3. If needed, use this metadata field in Display/Hide/Required logic across the rest of your survey.

Example Use Cases

1. Transaction Validation

→ Embed Transaction ID as a hidden field
→ Use it to trigger alerts if feedback is negative

2. Region-Based Routing

→ Pass Region via URL
→ If not available, ask the participant using a fallback dropdown

3. Show User ID Transparently

→ Display Customer ID in read-only mode to reassure the participant that the feedback is linked to their account

This is part of the Logic and Controls Guide in Zykrr’s Documentation Hub.
Need help integrating metadata via links, files, or APIs? Contact support@zykrr.com.

Updated on 19 Jan 2025