O'Hare Limo Transfers - About Us

This is a place to describe your Return and Refund Policy to buyers.

A Return and Refund policy usually consists of:

• Terms of return (i.e. number of days)
• State of return (e.g. unworn)
• Reason for return (e.g. damaged or wrong product)
• Process for return (i.e. how to initiate a return, how to contact customer service)
• Process of refund (i.e. terms of refund, duration, payment details)
• Contact details
• You are helping me set up conversion tracking for my transportation/limo business. My website has the "LimoFlow" booking form embedded on it. IMPORTANT — this is specifically my sub-brand "O'Hare Taxi Airports" booking form: its embed id is RES-V3-WQNXU0, and everything below applies ONLY to that form. If I run more than one brand, each brand has its own separate embed id, website, and tracking setup, so do not mix them up or apply this to another brand's form. I want to capture bookings as conversions in Google Analytics 4 and Google Ads (and optionally Meta/other pixels) using Google Tag Manager (GTM).
• 
  
• 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.

Privacy Policy Text

“For identity verification:

Where identity verification is enabled, the app may process biometric data (facial imagery) to verify your identity and prevent misuse. The app may use depth data for liveness detection. This depth data is processed locally on your device and is not stored or transmitted. The app may ask you to take a selfie, which may be securely transmitted to our trusted Service Providers solely for verification purposes and is deleted after verification is completed. Biometric data is used only for identity verification and liveness detection, and not for advertising, marketing, or profiling.”

Please note that we do not collect, store, or transmit any biometric data (including depth maps, face mesh, or ARFaceAnchor data) and do not create biometric templates. All data is used temporarily and discarded immediately after processing.