IN BLACK CAR SERVICE IN CHICAGO BY O’HARE LIMO, YOUR RESERVATION WILL BE CHARGED  WHEN BOOKING  OR CALL TO PAY TO DRIVER.

NO SHOWS OR CANCELLATIONS

• Airport Pickups and Point to Point (Sedans and SUVs) that are not cancelled 2 hours before the scheduled pick-up time WILL BE CHARGED the rate ( With some exception), no gratuity, no tax. All No-Show reservations will be charged the rate, no gratuity, and no tax.

• For ALL Charters, Weddings, Group Transportation (Limousine, Vans, and Buses), or out of state transportation, the reservation must be paid 48 hours before the pickup time. CANNOT be cancelled under 2 days. If the reservation is cancelled less than 2 days before the date of service, the full amount is charged, less the gratuity, to the credit card provided.

• Upon receiving this confirmation email, service is rendered on the requested date, and it serves as a credit card authorization. For any ride, after 10 minutes of waiting time ( DOESN’T APPLY IN AIPORTS ) or any extra stops, extra charges will apply.

Important Privacy Policy

Additional Charges and Policies

• For any airport rides, the vehicle type will be determined by the amount of luggage. Golf Clubs, Skis, Wheelchairs, Strollers: you will automatically be sent an SUV and charged the SUV price.

• All deposits are NON-refundable unless you meet paragraph 1 or 2 conditions

• Any credits are only available to use for future transportation within 6 months; after that period, the credit is voided.

• Smoking and eating are not permitted.

• Children under age 8 are required to be properly secured in a car seat. If you choose not to, O’Hare Limo Express LLC and the driver are not liable for any damages.

Authorization and Acknowledgment

I, the undersigned, hereby authorize O’Hare Limo Express LLC/Black cars Service to charge the above listed credit card account the amount indicated on all orders I approve by fax receipt, or by my signature (including anyone authorized by me to sign) at the time of receipt. I guarantee payment in the event of a charge-back or non-payment without just cause, by O’Hare Limo Express LLC. My signature confirms that I knowingly provided this credit card information as valid and true, and that I authorize personal and/or corporate use of this credit card for future services without further signatures.

HOW THE LIMOFLOW FORM HANDS OFF DATA (this is the contract — rely on it):

– The form does NOT install GTM, gtag, or any pixel. It assumes my own GTM container is already on the page. Its only job is to emit the booking data when a booking completes.

– Primary channel: on every completed booking the form dispatches a browser CustomEvent named «limoflow:bookingCompleted» on the page. Listen with:

    document.addEventListener(‘limoflow:bookingCompleted’, function (e) {

      var p = e.detail.params;             // the data object

      var redirectUrl = e.detail.redirectUrl; // thank-you URL, may be undefined

    });

– e.detail.params fields (empty/zero values are omitted):

    transactionId  -> unique booking id; USE AS the transaction/conversion id for de-duplication (e.g. «33614»)

    transactionIds -> comma-joined ids when one checkout booked multiple vehicles

    value          -> conversion value, 2-decimal string (see DEPOSITS below)

    currency       -> ISO-4217 code from the operator’s settings (e.g. «USD»)

    tip, paymentStatus («paid» | «processing» | «quote»)

    serviceType    -> one_way | round_trip | hourly | one_way_to_airport | one_way_from_airport | tour

    vehicleType, pickupDate (YYYY-MM-DD)

    trafficType    -> paid | organic | referral | direct

    originalReferrer, utmSource, utmMedium, utmCampaign, utmTerm, utmContent

    gclid, fbclid, msclkid, ttclid, liFatId, twclid, dclid  (ad click IDs)

    firstTouchSource/Medium/Campaign/TrafficType (first-touch metadata only)

    embedId        -> my form’s embed code («RES-V3-WQNXU0») = which brand’s form fired this (only needed if I run multiple brands in ONE shared GTM container)

    aliasCompanyId -> present only for a sub-brand booking

  NO personal data (name/email/phone) is ever included, by design.

– Alternative channel (if I set a thank-you page in LimoFlow): the same data is appended to my thank-you URL as snake_case query params (?transaction_id=&value=&currency=&gclid=&utm_source=…). Read with GTM URL variables. Don’t use BOTH this and the JS event for the same conversion unless you de-dupe on transaction_id.

– Fallback dataLayer events (don’t build on these): the form also pushes two thin events — limoflow_lead_created (lead_id + order_id, before payment) and limoflow_payment_completed (lead_id, order_id, value, currency, payment_method, payment_status, embed_id, alias_company_id). IMPORTANT: limoflow_payment_completed uses order_id/lead_id and has NO transaction_id, so do NOT wire the conversion off it — build on the limoflow:bookingCompleted CustomEvent above (which carries transactionId for de-dup).

DEPOSITS / «PAY LATER»:

– By default «value» is the FULL trip total even when the customer paid only a deposit or chose authorize/pay-later (a deposit means the trip is booked — best for ROAS). paymentStatus tells you paid vs processing vs quote so you can segment.

ATTRIBUTION:

– Conversions are last-touch (utm_*, gclid, trafficType). first_touch_* fields are metadata for discovery-channel analysis. trafficType/originalReferrer are provided so analytics doesn’t mis-attribute everything to «referral / the form’s domain». Click IDs (gclid etc.) fall back to the first qualifying visit’s value if the last visit didn’t have one, so an earlier ad click isn’t dropped.

ENHANCED CONVERSIONS (if I ask about this):

– LimoFlow never exposes customer name/email/phone client-side, so there is NO client-side gtag(‘set’,’user_data’,…) call to build from this event — don’t try to read PII out of the booking form’s DOM. Enhanced Conversions is instead a LimoFlow-hosted, server-side, opt-in feature: I connect my Google Ads account under Admin -> Company -> Embed Code -> Advanced -> Server-Side Conversions (OAuth, not an API key), and LimoFlow’s backend hashes my customers’ email/phone and sends them to Google Ads alongside the gclid. This is separate from everything else in this prompt — don’t try to build it via GTM/gtag, and it currently requires a gclid to be present on the booking.

WHAT I WANT YOU TO PRODUCE:

1. A GTM Custom HTML tag (fire on All Pages) that listens for «limoflow:bookingCompleted» and pushes e.detail.params into the dataLayer as an event «limoflow_booking», exposing value/currency/transaction_id (in an ecommerce object for GA4) plus flat copies for Google Ads.

2. A GTM Custom Event trigger on «limoflow_booking» (with an option to fire only when paymentStatus == «paid»).

3. The Data Layer Variables I need.

4. A GA4 «purchase» event tag using transaction_id/value/currency.

5. A Google Ads Conversion tag using value/currency and transaction_id (for de-dup), plus the Conversion Linker on All Pages.

6. Exact click-by-click steps to create each in GTM, and how to verify in GTM Preview / GA4 DebugView / Google Ads.

Ask me for my GA4 Measurement ID (G-XXXX) and Google Ads Conversion ID (AW-XXXX) + Conversion Label before writing final tag values. My LimoFlow Embed ID is RES-V3-WQNXU0.

I have read and understand all policies of O’Hare Limo Express LLC/Black Car Service listed in this Reservation Form. My signature signifies understanding.