/** * order3000 ad-click attribution — first-party capture of the click identifiers * that appear on an ad's landing URL (Google Ads auto-tagging `gclid`/`gbraid`/ * `wbraid`; Meta `fbclid`). A reservation made later in the session is then * attributed to the originating ad click and reported to the ad platform * server-side — Google Ads offline conversions and the Meta Conversions API. * * **Provided by order3000 so every consumer captures attribution identically, * without re-implementing this logic.** Wire it in two lines on the restaurant * frontend: * * - call `persistAdClickIdsFromUrl()` once on landing (every page), and * - spread `getAdClickIds()` into the `reservations.make(...)` payload on * submit. * * No Google/Meta script is ever loaded — these are plain query params we read * ourselves and store in first-party cookies (browser-only; every function is a * no-op when `window` is undefined, so it is safe to import in SSR code). */ /** The ad-click identifiers order3000 captures from a landing URL. */ declare const AD_CLICK_ID_KEYS: readonly ["gclid", "gbraid", "wbraid", "fbclid"]; type AdClickIdKey = (typeof AD_CLICK_ID_KEYS)[number]; type AdClickIds = Partial>; /** * Read any ad-click ids from the current URL and persist them to first-party * cookies. Call once on landing (every page). Only a present id is written, so a * later non-ad navigation never clears an earlier attribution. */ declare function persistAdClickIdsFromUrl(): void; /** The persisted ad-click ids, for attaching to a reservation on submit. */ declare function getAdClickIds(): AdClickIds; export { AD_CLICK_ID_KEYS, getAdClickIds, persistAdClickIdsFromUrl }; export type { AdClickIdKey, AdClickIds };