airport-one-embeddable-widgets 2.16.0 → 2.17.0

package/README.md

@@ -36,6 +36,8 @@ You can customize the behavior and appearance of the element by setting its attr
 | departureAirportLabel | string | null    | The label for the departure airport input   |
 | departureDateLabel    | string | null    | The label for the departure date input      |
 | returnDateLabel       | string | null    | The label for the return date input         |
+| consentAdvertising    | string | null    | Dynamically turn off/on consent for Advertising - by passing a "true" or "false" |
+| consentAnalytics      | string | null    | Dynamically turn off/on consent for Analytics - by passing a "true" or "false"   | 
 
 ## Examples
 
@@ -208,3 +210,27 @@ flight-search-form::part(flight-search-widget-search-button-svg) {
   fill: #fff;
 }
 ```
+
+# Consent Management
+
+## How to dynamically manage user consent preferences and pass them into the widget
+
+There are two consent categories that can optionally be turned off/on via DOM manipulation and modifying attributes on the widget.
+
+```javascript
+<flight-search-form origin="JFK" destination="LAX"></flight-search-form>
+
+...
+
+// Call a similar function via your CMP integration to pass in the consent values for Analytics or Advertising
+function changeConsent(consentAdvertising, consentAnalytics) {
+  // Select the flightWidget element
+  var flightWidget = document.getElementsByTagName('flight-search-form');
+
+  // Set user's advertising consent from CMP
+  flightWidget.setAttribute('consentAdvertising', consentAdvertising); // consentAdvertising param should be a string of "true" or "false"
+
+  // Set user's analytics consent from CMP
+  flightWidget.setAttribute('consentAnalytics', 'true') // consentAnalytics param should be a string of "true" or "false"
+}
+```