Feed mapper is an essential feature that allows for seamless feed field remapping, making your feed compliant for Meta, or any other preferable advertising channel.
And if you’re missing product information, Feed mapper can also easily insert new fields with their values into the feed, following the rules of the channel that’s been advertised on.
Now, let’s start from the very beginning.
How mapping can be done?
Feed mapper is a required step in catalog creation, and for existing catalogs once you’re in desired catalog, navigate to the *Feed preview toggle, then click on the top right corner icon (with the pencil), to enable the edit mode.
Et voilà! Welcome to the Feed Mapper, now you should see something like this pop up on your screen.
Here, you'll be able to map all the columns that are currently in your feed. This is crucial because the system you're using may or may not align with Meta’s requirements or the rules of the platform being advertised on. Luckily now, you can easily remap your feed, all by yourself.
First, you'll notice two types of fields: Mandatory and Recommended. There are also Optional and Custom fields, but we'll explain those later in the article.
Let's focus on the main differences between Mandatory and Recommended fields:
Recommended fields, on the other hand, are optional. You can delete these columns or add more if needed.
What are the custom and optional columns used for?
Besides mandatory and recommended columns, you can also add custom and optional columns.
These are fields that Hunch supports and can be added in feed mapper. They can then be used on the template to provide more specific information and enhance the visual appeal of your visuals (e.g.”percentage_off” field).
Dynamic values in feed mapper
To use dynamic values, use the hashtag symbol (#), and a list of available fields will be displayed.
Static elements in Feed mapper
On the other hand, if your feed doesn't have information for some of the mandatory fields, or if you're unable to match the field, you can use a static text instead of a dynamic one.
To do this, simply navigate to the desired field and type in the text without using the hashtag symbol (#). Unlike dynamic fields, static fields won't be highlighted in green after you enter text (see example below). But using the static text, your feed will be ready to go!
Which transformations are supported?
Now, we’ll move on to the transformations section, and you might be wondering what options transformations offer. We're going to explain this in the next few examples.
Similar to previous steps, transformations can also be done within Feed Mapper.
As you may know, there are Meta standards for DPA feeds, such as restrictions on capitalization in the Description, Brand, and Title columns.
The standards for textual fields require that text must be written in a specific format known as 'Capitalize'.
Suppose your feed has these textual columns formatted in all caps. To change this, you can use transformations.
Simply choose the field you want to apply the transformation to, click the '+' button, and select first 'lowercase' and then 'capitalize’.
And there you have it! All the titles (in this case) from the product from your feed will be formatted accordingly.
Additionally, you can also change the currency format if needed.
To do this, simply navigate to the pencil icon located next to the price field and select the desired currency format from the drop down list.
Hunch offers a range of transformations to help you optimize your feed. Feel free to explore these options or reach out to your dedicated Customer Success Manager for assistance.
Once you've finished mapping and transforming the necessary columns, you'll be able to preview 10 items from your feed and see how they'll appear later on your template or ad. You can scroll through the products using the arrows on the right and left to get a better sense of the overall look and feel.
To save your changes, simply click the 'Save' button located in the bottom right corner of the page. This will initiate a sync and prepare your catalog for use.