Mapping of assets to asset families

This page will explain the configuration of the mapping for Bynder to Akeneo.

Warning : Never forget to save the configuration after the modification of the parameters in the mapping.

Asset Family Code

Let's start by the destination: Akeneo Asset Family.

Here you must put the code of the asset family in which you will send the assets and the meta-properties.

The information is case-sensitive.

In this example, we will send the asset to the “atmosphere” asset family. As in all configuration, we use the code of the asset family and not the label.

See your Akeneo PIM configuration to identify the codes. (see the Akeneo documentation to help you).

Conditions

In Akeneo, you will manage your assets in many asset families. To split the Bynder assets, you can apply some conditions.

You can put as many conditions as you want. An asset must fit to all conditions to be selected. If you want to apply some “OR” conditions, you must create different mappings. Follow this link to understand how each comparison works: Filters for conditions

• First you must identify the Bynder meta-property you want to use to apply a condition.
• Then you choose the type of condition.

Media URL

As we transfer only the URL, you must configure this part. You can send many URL if you want to manage different rendition and if you are not using DAT from Bynder.

An URL parameter is really easy:

The Bynder meta-property which contains the URL you want to get The Akeneo asset attribute code in which you want to send the URL

Metadata

Like for the URLs, you can send as many metadata from Bynder to Akeneo as you want.

For each meta-property, you will configure the source, the destination and depending on the type of meta-property, you will have to configure additional information (for example the local or channel you want to feed).

For more information about each metaproperty, you can follow the link Metadata configuration.