Data Correction Module

The value of the reporting is only as good as the quality of the data in it. That’s why we created the Data Correction Module to empower administrators to maintain data integrity much more easily.

Considerations

• Fields updated: The ‘Raw’ fields (which inform the ‘Reporting’ fields)

• Purpose: Allows admins to “fix” (change) underlying messy data

• When it runs: Only runs one time per configuration on an ad hoc basis, only when configured and manually run by an admin

• Data Risk: This is destructive since it changes the underlying values in the “Raw” fields

Uses Cases

Use Data Correction when the underlying RAW data itself is wrong and needs to be permanently fixed.

• Marketing list upload mistakes: You uploaded a tradeshow list but accidentally set RAW FC UTM MED to "Trade Show" when your UTM Taxonomy requires "Tradeshow", or used "RSA 2024" instead of "RSA Conference 2024" for the campaign name.

• URL parameter mistakes: Your paid search campaigns have been running with UTM Parameters containing typos like utm_medium=ppc instead of utm_medium=paid-search, creating inconsistent Attribution data.

• Legacy values that don't match current taxonomy: Old Engagement records contain values like "cpc" and "adwords" that should be updated to match your current standardized UTM Taxonomy of "paid-search" and "google-ads".

Rule of Thumb: If the RAW data is incorrect, use Data Correction.

Distinction From The Data Mapping Module

To understand how and when to use this feature compared to the Data Mapping Module, see the Data Correction Module vs. Data Mapping Module article.

Permissions

Before you get started, ensure you have the required permissions.

The Data Correction Process

Each data correction operation follows a structured process:

1. Navigate to the Integrous Analytics App in Salesforce → Admin Settings → Data Correction → Processing

2. Enter a detailed reason for the correction

   1. This is key for understanding what records were updated, by whom, and why

3. Choose whether to save history records (in the checkbox to the right)

   1. This will create a record for each Engagement record updated that will be retained for a period of time

   2. This can be helpful in troubleshooting, but has an impact on Salesforce storage

4. Set criteria to identify Engagement records to be updated:

   1. Click "Add Criteria"

   2. Select fields, operators, and values

   3. Click "Validate" to confirm matching records

5. Configure value mappings:

   1. Click "Value Mapping"

   2. Select RAW attribution fields to update

   3. Specify current values to find and new values to insert

6. Preview changes:

   1. Click "Preview" to review affected records

   2. Verify old and new values

7. Execute the correction:

   1. Click "Execution"

   2. Read the disclaimer and check the authorization box

   3. Click "Execute Data Correction"

Reviewing Correction History

Review past corrections on the History tab, which shows:

• Execution date

• User who performed the correction

• History retention setting

• Reason for correction

• Status of the process

Click on a correction record for more details, including:

• Success/failure counts

• Record retention information

• Query used for record selection

• Value mappings applied

• Affected Engagement records (if history was saved)

This is a very useful and powerful tool. But it’s also dangerous since it alters underlying attribution data and cannot be automatically undone, so it should be used cautiously.