> This page is for Product.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.feedonomics.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.feedonomics.com/_mcp/server.

# Inputs and what happens to them

> The four config setup inputs — purpose, brand voice, search keywords, and additional context — what each one steers and what gets retained.

Config setup asks you for four things. Each one steers the output differently, and knowing how helps you decide where to invest your effort.

![The Set the generation config step: purpose chips, a brand voice text area with an upload option, a search keywords file upload accepting CSV or TXT, and an additional context box.](/_fern-img/13e15c9387bb3f35052456f2c9d27779e3188bace5e288efc31e7c46f437996a.webp)

All four are read by an agent that writes the actual rules for your run, field by field — see [How your inputs become rules](/product/enrichment/generation-configs).

## The four inputs

### Purpose

A multi-select: what are you optimizing for? The options are **Google Ads/shopping**, **Website product data**, **SEO / organic search**, **Marketplace listings**, and **Email & social** — pick what applies. Purpose steers *how* every field gets written: copy optimized for ads leads with what earns the click; copy optimized for your site leads with what closes the sale.

### Brand voice

Free text plus optional document upload, **limited to 10,000 characters**. This is the highest-leverage input — [give it a full page of attention](/product/enrichment/brand-voice).

### Search keywords

Upload a `.csv` or `.txt` of your target keywords. The engine weaves them into descriptions and SEO fields where they fit naturally — no keyword stuffing, which would hurt both your rankings and your quality scores.

> **Tip**
>
> Use your actual search-query data, not aspirational head terms. The keywords real shoppers use are the ones enrichment can work into copy credibly.

### Additional context

Single-line instructions that fall outside your brand voice, or specific concepts you want the agent to pay attention to — positioning for this product line, an audience nuance, a detail about the catalog it wouldn't infer. Context steers generation for every field but isn't stored as a config setting; think of it as a briefing note for this config. See [Additional context](/product/enrichment/generation-configs#additional-context) for how to write them well.

## What's kept and what isn't

Your finished config and its plain-English summary are saved for reuse. The raw materials — uploaded documents, keyword files, context notes — are used to build the config and not retained.

Once your inputs are in, the config builder does the rest — see [Generation configs](/product/enrichment/generation-configs) for what it produces and the rules it follows.