Convertr Govern: Creating an Account Level Policy. Follow

Account-Level Policy Rules let you set your data requirements once and have them applied automatically to every campaign, source, supplier, and market — instead of configuring rules separately for each campaign.

Before you start

• Who can do this: Admin users only.
• What you'll need: a clear picture of what your business requires before a lead or contact record can be used — for example, a required consent field, or approval from only certain sources.
• What doesn't change: your existing campaign-level rules keep working exactly as they do today. Account-level policy sits above them; it doesn't replace anything you've already configured.

Creating a new policy

1. Go to Govern > Policies.
2. Click Add Policy.
3. Enter a Policy Name and click Save.
4. Your new policy appears in the Policies table — disabled by default — alongside its running totals: Leads Processed, Lead Failures, and Lead Exceptions.

Add validation jobs to your policy

A policy is made up of one or more jobs — each one a check that runs against every lead the policy applies to.

1. Click Configure next to your policy in the Policies table to open its Jobs page.
2. Click Add Job.
3. Choose a job from the Job dropdown. Each option describes what it checks — for example, First and Last Name Check, Duplicate Email Check, Profanity Check, or Conditional Validation.
4. Some jobs need extra configuration. For example, First and Last Name Check asks you to map its firstName and lastName inputs to the matching fields in your data — Govern offers fields from across your whole account, since a policy job runs against leads from every campaign. Others, like Profanity Check, let you set exclusions and allowed words.
5. Click Save. The job appears in the Jobs table, enabled by default, with its condition set to Catch All (it always runs) unless you configure one.

Combine jobs with grouping and conditions

• Group and Add New Job on a job's row groups it with a new job you're adding; Add Job to Group adds an existing job to that group instead. Ungroup removes a job from its group.
• Within a group, set each job to Catch All to run it against every lead, or turn Catch All off and use Field, Condition, and Value to run it only when a lead matches that condition.
• Use the Enable toggle — on the policy itself, and on each job — to turn checks on or off without deleting them.