> ## Documentation Index
> Fetch the complete documentation index at: https://docs.markifact.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rename Fields

> Rename data fields in your datasets to standardize column names and improve data consistency.

**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

| Field              | Type   | Required | Description                                      |
| ------------------ | ------ | -------- | ------------------------------------------------ |
| **Data**           | Data   | Yes      | The dataset containing fields you want to rename |
| **Field Mappings** | Mapper | Yes      | Map current field names to new field names       |

***

## Outputs

| Output           | Description                                   |
| ---------------- | --------------------------------------------- |
| **Updated Data** | Dataset 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

<Accordion title="What happens if I try to rename a field that doesn't exist?">
  The node will ignore mappings for non-existent fields and process the rest normally. Your data won't be affected, but you won't see the expected field name change.
</Accordion>

<Accordion title="Can I rename multiple fields to the same name?">
  No, this would create duplicate field names which isn't allowed. Each field must have a unique name. Choose distinct names for all your renamed fields.
</Accordion>

<Accordion title="Does renaming affect the data values?">
  No, renaming only changes the field names (column headers). All your actual data values remain exactly the same.
</Accordion>

<Accordion title="Can I use special characters in new field names?">
  Yes, but consider where your data is going next. Some systems (like certain databases or APIs) may not accept spaces, special characters, or very long names.
</Accordion>

<Accordion title="What if I want to keep some original field names?">
  Only map the fields you want to rename. Any fields not included in your mappings will keep their original names unchanged.
</Accordion>

<Accordion title="How do I handle fields with similar names from different platforms?">
  This is perfect for standardization. Map similar fields from different platforms to the same standardized name. For example, map both "campaign\_name" and "camp\_name" to "Campaign Name".
</Accordion>

<Accordion title="Can I undo field renaming?">
  Not directly in the same node, but you can add another Rename Fields node with reverse mappings to change names back to originals if needed.
</Accordion>