to do (link von ICEPortal): How will the photos via ICE Portal be distributed? (internal article)

The integration of the data delivered to ICE Portal (as of May 2021: all images and image information uploaded to Drive (without the content filtered out by GIATA for its own services) incl. the master data specified in Drive (regardless of whether they differ from MC, without GeoCodes), the specified channel IDs and room codes as well as room types) is the responsibility of the respective data recipient.

Thus, there is no actual push service, but only agreements on the type and frequency of data deliveries to third parties. In other cases or some partners use the API provided by ICE Portal to integrate the data directly into their own offer. Only in these cases can the content also be tracked. If the content is embedded individually or, moreover, passed on to third parties again, the actual usage cannot be tracked. All unclear cases can only be clarified individually via support requests.

In all cases, since the data is only visual content, it is mixed with other data sources. 

And in all cases a mapping to the respective data provider is necessary so that the data can be imported. Therefore, in individual cases (such as for Expedia) mappings are also emailed to ICE Portal in list form outside of the daily ICE Portal updates. However, most data consumers do the mapping themselves based on the master data supplied from Drive. This is more likely to result in errors, as the master data is often supplied incorrectly by the hotelier themselves. 

For the successful update and distribution of the data via ICE Portal, the following information must be supplied in the data set:

• At least 1 high-resolution image (image without flash symbol) with correct image motif (PreICE tag).
• Name and address
• GIATA-ID
• No conflict with an existing chain release in the existing ICE Portal distribution system (either via GIATA or via existing chain agreement with ICE Portal)

For some direct and indirect delivery channels, there are additional mandatory requirements listed here. Similarly, individual property-level distribution rules can be set via the ICE Portal dashboard, for example, excluding certain channels. 

If there are no restrictions, an update is currently done like this:

1. Hotelier uploads images and saves all changes in the Drive interface.
2. Via a nightly update, GIATA uploads the data (images, image types, room types, codes and master data) with the update date to an FTP server provided by ICE Portal.
3. ICE Portal checks daily for changed or new records and imports them. Others are ignored.
4. The data that meets the requirements is now distributed ("published"), i.e. data recipients can retrieve it via the interface.
5. Most data recipients, however, receive the data as delivered by the hotelier in a data package created by ICE Portal, which they import completely in the best case or - which is more often the case - integrate selectively according to their own requirements.
6. What has been published or delivered can be viewed in a daily report or checked after logging into the ICE Portal Dashboard and also edited individually. 

IMPORTANT:

There are special agreements and requirements that, depending on the data recipient, must also be set up separately with ICE Portal. For example, ICE Portal will only deliver images to Google if the respective hotel has been approved by ICE Portal in the Google Business account. Likewise, image data delivery is only made to Booking.com if the respective chain has arranged a corresponding agreement and release with its Booking.com account manager. Each desired data recipient must therefore be individually checked for functionality by ICE Portal, especially with regard to individual hotels, and set up again if necessary. Just because a certain OTA is on the distribution list of ICE Portal, no actual distribution takes place there.