Every channel needs certain fields (output attributes) filled in - title, brand, price, GTIN, colour, and so on. Mapping tells Koongo where each of those values comes from. A feed or integration is only ready when every required output attribute has a working value. This is the part people find fiddliest - the assistant makes it easy.
Just ask
Show me which required attributes are still missing on my Google Shopping feed, then help me map each one to the right field from my store.
Other examples: "Map the brand attribute to my store's manufacturer field." · "Set condition to a fixed value of 'new'." · "My colours don't match Google's list - help me line them up."
The three ways to fill an attribute
Way | When to use it | Say something like |
From a store field | The value already exists in your store. | "Map |
A fixed value (constant) | The same value for every product. | "Set |
A rule | The value depends on conditions or needs transforming. | "Build a rule that sets shipping based on weight." |
You can also give a fallback: "Use my brand field, but if it's empty fall back to 'Generic'."
Matching values and dropdowns
Dropdown / fixed-choice attributes (e.g. Availability, Condition): the channel only accepts specific values. Ask "What are the allowed values for availability?" and the assistant sets the correct one.
Value mapping (e.g. your colours → the channel's colour list): ask "Map my colour values onto the channel's allowed colours." The assistant lists both sides and proposes matches for you to confirm.
Some required attributes only appear after category mapping. Channels often add category-specific fields once you've chosen a category. Do Category Mapping first, then ask the assistant to refresh the attributes - the new ones will show up.
Know when you're done
Ask "Are all required attributes mapped now?" When the count of unmapped required attributes reaches zero, the feed or integration is ready to export / activate.
Mapping is saved but does not reach the channel until the feed is exported (or the integration re-submitted). Finish mapping, then ask the assistant to export.
Behind the scenes (for the curious)
Behind the scenes (for the curious)
Feeds use get_feed + map_feed_attribute; marketplaces use get_marketplace_attributes + map_marketplace_attribute; ads use the _ad_ equivalents. Available store fields come from list_source_attributes. Dropdown choices come from get_attribute_options; value-to-value mapping is prepared with get_value_mapping_inputs and applied as a rule. Category-driven attributes appear after refresh_marketplace_category_attributes (or the ad/feed equivalent). Use only_unresolved to list just the gaps; a required-unmapped count of 0 means you're done.