Overview
The Campaign Requirements Summary is a plain-English overview of your campaign's configuration. It reads your campaign's QA jobs, validation rules, value transforms, form setup, and suppression logic, then produces a structured summary that makes it easy to understand what the campaign expects — and where potential issues may exist.
This guide explains how to access the summary, what you will see, and how to use it effectively in your day-to-day workflow.
What Campaign Summaries does
Instant campaign understanding — Generates a plain-English summary of required lead attributes, validation rules, form configuration, and QA logic — without you needing to open individual jobs or configuration screens.
Configuration risk detection — Flags potential setup issues before they cause delivery problems, with colour-coded red alerts (critical) and amber warnings (review recommended).
Supplier communication — Provides a copyable summary that can be pasted directly into emails or briefing documents to communicate campaign requirements to suppliers and partners.
Operational efficiency — Removes the manual overhead of cross-referencing forms, QA jobs, and validation configuration during campaign setup and onboarding.
Who is this for?
- Campaign Managers; Users responsible for ensuring campaigns are correctly configured and delivering quality leads.
- Supplier-Facing Teams; Anyone who needs to communicate what a campaign requires to external media partners or lead suppliers.
How to Access the Campaign Requirements Summary
The Campaign Requirements Summary can be opened from two locations within a campaign: the Overview tab and the Processr tab. The summary works identically regardless of where it is launched from.
Step 1: Open your campaign
Navigate to the campaign you want to review. You can do this from the Campaigns menu in the top navigation, or by searching by campaign ID or name.
The Campaign Requirements Summary is available on active campaigns. You will see a Summary link in the campaign header bar, alongside the campaign status indicator.
NOTE: The summary panel is labelled with the campaign ID and name — for example, 'CIDX - Campaign Name - Campaign Requirements Summary'. This makes it easy to confirm you are viewing the correct campaign when working across multiple campaigns.
Step 2: Open the summary panel
Click the Summary link in the campaign header. The Campaign Requirements Summary panel will open as a modal overlay on top of the current page.
When the panel first opens, you will see the AI and Beta badges in the top left, and a 'Generating summary...' loading state with a spinner. Summary generation typically completes within a few seconds.
NOTE: The summary can also be opened from the Processr tab. This is particularly useful when you are reviewing QA job configuration and want to see the AI's interpretation of your setup without navigating away from the Processr view.
Step 3: Review the configuration risk alerts
Once generated, the top section of the summary panel displays any configuration risk alerts. These are colour-coded banners that highlight potential setup issues detected by Convertr:
RED ALERT
Critical issue
A problem that is likely to cause lead rejection or delivery failure. Examples include: no form attached to the campaign, QA jobs referencing fields that cannot be confirmed as submittable, or field name mismatches in value transforms that cause leads to fail.
AMBER WARNING
Review recommended
A potential inconsistency that may not immediately break delivery but is worth investigating. Examples include: conflicting validation rules for the same field, conditional checks that depend on derived values, optional fields triggering hard-fail rules, or redundant suppression list jobs.
Each alert includes a plain-English description of what has been detected and why it is a concern. Read each one carefully and take action where appropriate before going live with the campaign.
IMPORTANT: A red alert does not always mean your campaign cannot deliver leads, but it does indicate a configuration issue that is likely to cause problems. Resolve red alerts before launching a campaign wherever possible.
Step 4: Review the summary body
Below the risk alerts, the summary is organised into sections that describe your campaign's configuration in plain English:
General Quality Checks
An overview of validation behaviour that applies across all leads. This section covers:
Whether a form definition is attached to the campaign, and what that means for summary completeness
How test_lead is validated and what values are accepted
Non-standard character checks across submitted fields
Date window restrictions on submitted data (e.g. asset download date must fall within the last 2 days)
Duplicate and repost detection logic
Whether any conditional pilot processes are active and what they trigger
Required field sections
Each field that the campaign requires is given its own section, labelled with the field name and '(REQUIRED)'. For example:
Email (REQUIRED)
Country (REQUIRED)
Asset Download Date (REQUIRED)
Each section lists the specific validation rules applied to that field — format requirements, allowed values, suppression list checks, and any conflicting rules detected between QA jobs.
Derived field sections
Fields calculated automatically by Convertr from submitted data are listed separately. These are not submitted directly by publishers, but they often feed into validation logic or delivery integrations and can be a source of configuration risk. Common derived fields include:
- Email Domain; generated from the submitted email address; used in suppression checks and to build Source Domain
- Source Domain; built from publisher name, email domain, and area; used for duplicate cap enforcement
- Job Title Pilot / Pilot Key; derived flags based on publisher name and country code that trigger conditional validation
- Phone Dedupe; built from telephone, extension, publisher name, and country; used for duplicate and repost detection
BEST PRACTICE: Use the summary body to cross-check your campaign configuration. If a required field appears with conflicting rules, or a derived field is flagged as having incomplete mappings, review the relevant QA jobs and value transforms in the Processr tab before going live.
Step 5: Use the Refresh button after making changes
The summary reflects the saved state of your campaign at the time it was last generated. The 'Last refreshed' timestamp shown in the top right of the panel tells you exactly when this was.
If you make changes to your campaign configuration — such as updating a validation rule, adding a QA job, or attaching a form — click the Refresh button to generate an updated summary. The button will change to 'Refreshing...' while the new summary is being generated, then display the updated content.
BEST PRACTICE: Always refresh the summary after making significant configuration changes. A refreshed summary may surface new risk alerts or remove previously flagged issues, giving you an accurate picture of the campaign's current state.
Step 6: Copy and share the summary
Click the Copy button to copy the full summary text to your clipboard. The content is formatted as plain text and can be pasted directly into:
Emails to suppliers or media partners
Supplier briefing documents
Internal onboarding materials or campaign handover notes
Team communication tools such as Slack or Microsoft Teams
The Copy function captures the complete summary — including risk alerts and all field sections — preserving the structure so it reads clearly when pasted into any application.
BEST PRACTICE: When briefing suppliers, the summary gives them exactly what they need to submit valid leads: required fields, accepted formats and values, email rules, and date restrictions — all in plain English. This reduces back-and-forth and helps suppliers get it right first time.
What Campaign Summaries cannot do
🚫 Modify campaign configuration. The summary reads and interprets your existing configuration — it does not make any changes to your campaign, QA jobs, or validation rules.
🚫 Generate a complete summary without a form. If no form is attached to the campaign, the summary is inferred from QA jobs and value transforms only. This means the list of publisher-submittable fields cannot be confirmed, and the summary will be flagged as incomplete. Attach a form to get a full and accurate summary.
🚫 Access or use lead data. The AI only reads campaign configuration — forms, jobs, rules, and transforms. Lead-level data, including any personal or contact information submitted through the campaign, is never used to generate the summary.
🚫 Replace campaign configuration review. The summary is a helpful guide, not a substitute for reviewing your campaign configuration directly. For critical campaigns, always verify setup in the Processr tab and relevant configuration screens as well as reviewing the summary.
🚫 Auto-update when configuration changes. The summary does not refresh automatically. You must click Refresh after saving any configuration changes to generate an updated version.