import { ProjectUIDL } from '@teleporthq/teleport-types';
export declare const COOKIE_CONSENT_KEY = "cookieConsent";
export declare const COOKIE_CONSENT_ACCEPTED = "accepted";
/**
 * Dispatched on `window` by the `storage-local-set` / `storage-local-remove`
 * workflow steps (teleport-plugin-next-workflows). A write in the visitor's own
 * tab fires no `storage` event, and the cookie banner's Accept is such a write.
 */
export declare const LOCAL_STORAGE_WRITE_EVENT = "teleport:local-storage";
/**
 * True when the project loads a Google Analytics tag or a Tag Manager
 * container — script assets the editor's project mapper builds from the
 * merchant's ids — or anything else that writes `window.dataLayer`.
 */
export declare function loadsGoogleTag(uidl: Pick<ProjectUIDL, 'globals'>): boolean;
/**
 * True when a workflow can store the visitor's Accept: the cookie banner's
 * Accept button. Without one nothing could ever grant consent, so a site with
 * an Accept-less banner (or none) keeps its Google tags as they were.
 */
export declare function hasCookieBannerAccept(uidl: Pick<ProjectUIDL, 'workflows'>): boolean;
export declare function needsGoogleConsentMode(uidl: Pick<ProjectUIDL, 'globals' | 'workflows'>): boolean;
/**
 * Google Consent Mode v2 for a site with a cookie banner. Runs in `<head>`,
 * before the Google tag and the Tag Manager container (both in `<body>`), so
 * their first look at `dataLayer` finds the default. A visitor who already
 * accepted starts granted; one who accepts on this page is granted at once,
 * with no reload. Commands must be pushed as `arguments` objects — Google's
 * tags ignore plain arrays.
 */
export declare const GOOGLE_CONSENT_MODE_SOURCE: string;
//# sourceMappingURL=google-consent-mode.d.ts.map