In the past, DataFeedWatch customers used their source feeds to create shopping feeds for the channels. Every time they wanted a new shopping feed, they had to create and optimize that feed from scratch. There were no alternatives.
Therefore, the process of distributing the product catalog on other channels had to pass through this stage. Although it was a one time action, we knew that we had to do something to make it even easier for PPC Managers to launch multiple channels in as little time as possible.
Do you want to be able to create unlimited feeds for shopping fast and easy? Do you want to create rules only once and then apply them to all shopping channels with a click?
Let us introduce the DataFeedWatch Internal Fields.
Let’s see, step by step, some of the most important things to consider when implementing internal fields in your DataFeedWatch Account.
What are internal fields?
You can think of internal fields as a DataFeedWatch master feed from which you can create any output feed.
You upload your source feed to DataFeedWatch and adapt it to every single shopping channel. That means that you create rules and optimizations for every channel separately.
Mapping with Internal fields:
Internal fields are adding a new layer between your source feed and the shopping channel output feeds. Instead of mapping your output feeds directly from your source feed, you map them from the internal fields.
Wait, but a new step isn’t actually adding more work on my plate instead of saving me time? Not in this case.
Creating internal fields is quick and it follows the same mapping process as before. What internal fields do is enhancing your source feed.
Let’s put it best with an example: Let's say the Color attribute is missing from your source feed.
If you know that your colors can be found in the description you can create a rule that extracts that value from the description. A rule like that creates new color attributes based on the description would look like this.
The problem is that when you have to create this rule ten times for each channel.
If you create this rule with Internal fields then all you need to do when adding color to shopping channels is to map it from the internal fields.
If you want to see more examples of the best usage for Internal fields we have created a list of examples here: Practical Examples of Using Internal Fields.
That’s cool, but I already have all my mappings in place.
What are your mapping options in DataFeedWatch?
1. Continue mapping using the input fields from your source feed
You can continue to do your mappings using the input fields from the source feed. This might be a good solution for you if you don't send your feed to multiple shopping channels and already have your feeds in place and optimized.
2. Do the new mappings using internal fields
If you are working with lots of rules and channels, then it makes sense that you create them first in the internal fields tab and then use them for all the mappings.
3. Use both internal fields and input fields for mapping
Our new interface allows you to do channels mappings using both source fields and internal fields. For example, you can use your source feed for attributes that don't require optimization: ID, GTIN. The internal fields you can use them for those attributes that need further optimization: titles, descriptions, shipping rules and others.
4. Apply Internal Fields to existing mappings
If you have all your mappings in place and decide to use them we've made deployment pretty easy.
What are the benefits of using the internal fields?
1. Better overview of product data
You can define and keep track of all the product fields in your master feed in one place.
2. Faster mapping
If you want to change a field, eg. title, you will change it only once in the internal fields and it will be automatically updated on all the shopping channels.
3. Quicker optimizations all across the board
Let’s say you sell three types of apparel products: Dresses, Shoes, and Shirts. For each apparel product, you want a different title format to use across all shopping channels. Moreover, you need a general title format for all products for some channels. You can create these enriched titles in the Internal Fields section and they will be updated on all channels where you use them.
4. Avoiding errors and mismatching
By making all updates and optimizations in one place you are sure that all data is accurate on every channel.
How to create internal fields?
Creating internal fields in DataFeedWatch is very simple. Let's see what steps you need to take to start using them in your feeds.
1. You can set up the Internal Fields at a shop level
2. Start mapping your DataFeedWatch Internal Fields. You have two options here:
Select name from the list - the name of the internal field can be selected from a list of most common fields in data feeds;
Enter text - to name your internal field and then map it to the source fields.
How to use internal fields?
Let's walk you through the steps you need to take in order to apply the internal fields if you already have the mappings in your store.
Note: First of all, the internal fields are not mandatory. They will simplify your work a lot, so it would be great to add them, but you can decide if and when to implement them.
Steps 1-2 are similar to the mapping the new customers are doing.
1. What is different for old customers, that already have all their mapping in place is that after they've mapped the internal fields, they can hit the button Apply to existing channels if they want to use them in their feeds.
2. After that, you will be prompted with a page where you can review all the fields and the channels where Internal Fields will be applied automatically.
It is important to understand that this will have no effect on the output feeds, as the Internal Fields have exactly the same mapping as the mapping they replace.
3. In case there are fields that couldn't be mapped to internal fields, because you haven't set them up yet, on the next page we will show you what those fields are and you have the choice to leave them as they are or to create internal fields to map them too.
Note: Internal fields are NOT available for sub-accounts UNLESS the main account holder updates the settings for each sub-account.
Now, we would like to also hear your opinions and inputs on this topic at email@example.com