Suppression data

In order to achieve the most effective results when using Batch API with Suppression data, we recommend following these guidelines:

• Before running your input data against Suppression data, carry out a standard address cleaning session on your data first. If you have purchased any other additional datasets (for example Names, or Utilities data) these can also be configured in this initial session. Running a Suppression session against addresses that have already been cleaned and verified means that Batch API is more likely to find good suppression matches.
• Do not run your input data against both Suppression data and other additional datasets during the same session. A Suppression session should use only the core country dataset, and your selected Suppression datasets. Running a Suppression session at the same time as other additional datasets may prevent Batch API from finding good suppression matches in some cases.

The recommended workflow for using Batch API with Suppression data is shown in the diagram below:

Configuring Batch API give more information on this, including setting up additional datasets.

Effective use of Suppression data enables you to save time and money by excluding from your mailing list those households or individuals who will choose not to respond, or who are unable to do so.

Suppression data can be used to flag those people who have moved, who are deceased, or who have expressed a preference not to be contacted. In addition, you can filter out poor quality addresses which cannot be matched with confidence against the official postal address files. Removing these details from your mailing list will reduce the size of the list, while retaining its effectiveness.

To generate a high quality mailing list, follow these steps:

1. Clean your data against the official postal address files, in order to maximize the chance of delivery. The addresses in your database may be cleaned while retaining non-address information such as names and departments, depending upon the nature of the records.
2. Clean your data against your Suppression dataset.
3. Produce a file containing only those addresses which are likely to be worth mailing.

This should include both of the following:

• Addresses which produce Good or Verified matches when cleaned against the official address files. See Match Success for more information about match results.
• Records which were not matched against Suppression data.

Generating a complete mailing list

To generate a complete mailing list, use Batch API to produce a mailing list containing all addresses from your original database, regardless of quality, omitting only those which were matched against Suppression data.

This list will retain all other input records from your database, including those addresses which could not be matched against the official postal address files.

To generate a Suppression report, use the QABatchWV_CounterReport function in file mode, using the command:

batwv <input file name> <output file name> <report file name>

This function is described in terms of how to perform it using the C test harness supplied with Batch; however, you may choose to use your own implementation instead.

You may find it useful to add Suppression information to your current database, in order to carry out a statistical analysis of your data.

If you have configured Suppression DataPlus in your layout and an address record in your database has been matched against a configured Suppression DataPlus set, you will be charged a click for that match. You will be able to see which Suppression set the record has been matched against and will also be able to view DataPlus information such as date of death.

Refer to the Suppression Additional Data Guide that shipped with your data for more information about Suppression DataPlus.