Rename Fields changes the names of columns/fields in your data without affecting the actual values. Essential for standardizing data from different sources, improving readability, or preparing data for specific systems.

​
When to Use It

  • Standardize column names from different advertising platforms
  • Make field names more readable for reports and dashboards
  • Prepare data for systems that require specific field names
  • Clean up messy column names from API responses
  • Rename fields before writing to spreadsheets

​
Inputs

FieldTypeRequiredDescription
DataDataYesThe dataset containing fields you want to rename
Field MappingsMapperYesMap current field names to new field names

​
Outputs

OutputDescription
Updated DataDataset with renamed fields, values unchanged

​
Credit Cost

Free to use - no credits required.

​
How It Works

Takes your data and renames the specified fields while keeping all values intact:

Example:

Original Data Table:
| camp_name    | impr  | clks |
|--------------|-------|------|
| Campaign A   | 1000  | 50   |
| Campaign B   | 2000  | 100  |

Field Mappings:
camp_name → Campaign Name
impr → Impressions  
clks → Clicks

Result Table:
| Campaign Name | Impressions | Clicks |
|---------------|-------------|--------|
| Campaign A    | 1000        | 50     |
| Campaign B    | 2000        | 100    |

​
Real-World Examples

Standardize Platform Data Before Merging:

Step 1: Google Ads Get Report
| Campaign Name | Impressions | clicks | spend |
|---------------|-------------|--------|-------|
| Campaign A    | 1000        | 50     | 100   |

Step 2: Meta Ads Get Report  
| campaign_name | reach | link_clicks | amount_spent |
|---------------|-------|-------------|--------------|
| Campaign B    | 2000  | 75          | 150          |

Step 3: Rename Meta Ads fields
Mappings:
- campaign_name → Campaign Name
- reach → Impressions
- link_clicks → clicks
- amount_spent → spend

Step 4: Merge Lists → Write to Google Sheets
Final unified table with consistent column names

​
Tips

Multi-Platform Standardization:

  • Create standard field names that work across all your data sources
  • Map platform-specific names to your standard naming convention
  • Use this before merging data from different platforms

Report Preparation:

  • Rename technical API field names to business-friendly names
  • Make column headers readable for stakeholders
  • Consider your audience when choosing new names

System Integration:

  • Check destination system requirements for field names
  • Some systems don’t allow spaces or special characters
  • Rename fields to match exactly what receiving systems expect

​
FAQ