Send Assets to Your Asset Families
Feature availability: This feature is available in the job: Bynder x Akeneo — Bynder medias to Akeneo assets (Bynder Akeneo Connector)
This page explains how to configure the mapping from Bynder to Akeneo — covering asset family targeting, filtering conditions, media URL setup, and metadata transfer.
⚠️ Important: Always save your configuration after modifying any mapping parameter.
Asset Family Code
Start by defining the destination: the Akeneo Asset Family that will receive your assets.
Enter the code of the target asset family. This is where the assets and their meta-properties will be sent.
⚠️ Case-sensitive: The asset family code must match exactly as defined in Akeneo.
In the example above, assets are sent to the atmosphere asset family. As with all configuration fields, use the code, not the label.
Refer to your Akeneo PIM settings to find the correct codes. See the Akeneo documentation for guidance.
Conditions
Akeneo organizes assets across multiple asset families. Conditions allow you to filter which Bynder assets are sent to each family.
How conditions work:
- You can define as many conditions as needed.
- An asset must satisfy all conditions to be selected (AND logic).
- For OR logic, create separate mappings.
→ See Filters for conditions for details on each comparison type.
To set up a condition:
- Select the Bynder meta-property to evaluate.
- Choose the comparison operator and define the expected value.
Media URL
The connector transfers asset URLs rather than files directly. You can configure multiple URLs to support different renditions or derivatives.
Each URL mapping requires two fields:
| Field | Description |
|---|---|
| Source – Bynder Metaproperty | The Bynder field containing the URL to retrieve |
| Destination – Akeneo Attribute | The Akeneo asset attribute where the URL will be stored |
To select the right URL, you need to know the derivative codes available in your Bynder configuration:
- If you use the Dynamic Asset Transformation (DAT) module, use the
transformBaseUrlderivative.
- Otherwise, contact Bynder Support to obtain the full list of derivative codes for your environment.
Once you have the correct code, paste it into the "Source – Bynder Metaproperty" field. If the option does not yet exist in the Connect Platform, click the "Add" button to create it.
Metadata
You can map as many Bynder meta-properties to Akeneo attributes as needed. For each mapping, configure:
- Source – the Bynder meta-property
- Destination – the target Akeneo attribute
- Additional options – depending on the meta-property type (e.g., locale, channel)
→ For a full reference, see Metadata Configuration.