/**
 * Matomo Tag Manager (MTM) integration.
 *
 * Loads a Matomo Tag Manager container and exposes a typed helper to push
 * entries to the `_mtm` data layer. Works with both the App Router and the
 * Pages Router, and integrates with the server-side proxy
 * (`withMatomoProxy()`) so the container script can be served from your own
 * domain.
 *
 * @module tag-manager
 */
/** An entry pushed to the Matomo Tag Manager `_mtm` data layer */
export type TagManagerDataLayerEntry = Record<string, unknown>;
declare global {
    interface Window {
        /** Matomo Tag Manager data layer */
        _mtm?: TagManagerDataLayerEntry[];
    }
}
/** Options for {@link initTagManager} */
export interface TagManagerSettings {
    /**
     * Matomo base URL (e.g. "https://analytics.example.com").
     *
     * When using the server-side proxy (`withMatomoProxy()`), you can omit this
     * and the library will automatically load the container through
     * `NEXT_PUBLIC_MATOMO_PROXY_PATH` (so the browser only talks to your own
     * domain).
     */
    url?: string;
    /**
     * Container ID, as shown in Matomo → Tag Manager → your container
     * (e.g. "aBcDeF12"). The container script is loaded from
     * `{url}/js/container_{containerId}.js`.
     */
    containerId?: string;
    /**
     * Full container script URL. Takes precedence over `url` + `containerId`.
     *
     * Useful for non-live container environments, whose file names carry an
     * extra suffix (e.g. `container_aBcDeF12_staging_….js`).
     */
    containerUrl?: string;
    /**
     * When `true` (default), and if `NEXT_PUBLIC_MATOMO_PROXY_PATH` is defined,
     * the container is loaded through the server-side proxy instead of the
     * provided `url`.
     *
     * @default true
     */
    useProxy?: boolean;
    /** CSP nonce added to the injected `<script>` tag */
    nonce?: string;
    /**
     * Name of the Trusted Types policy used for the script URL.
     *
     * @default "matomo-next"
     */
    trustedPolicyName?: string;
    /** Called when the container script fails to load */
    onScriptLoadingError?: () => void;
    /** Log configuration problems to the console */
    debug?: boolean;
}
/**
 * Reset the module state so `initTagManager` can run again.
 *
 * @internal Exposed for tests.
 */
export declare function resetTagManager(): void;
/**
 * Loads a Matomo Tag Manager container.
 *
 * Seeds the `_mtm` data layer with the `mtm.Start` event and injects the
 * container script — the equivalent of the snippet Matomo shows under
 * _Tag Manager → Install Code_. Safe to call from a `useEffect`: subsequent
 * calls are no-ops.
 *
 * Note: out of the box, Matomo Tag Manager only tracks the initial page load.
 * For client-side navigations (App Router / Pages Router route changes),
 * enable a **History Change** trigger in your container, or push your own
 * events with {@link pushTagManager}.
 *
 * @example
 * ```tsx
 * "use client";
 *
 * import { useEffect } from "react";
 * import { initTagManager } from "@socialgouv/matomo-next";
 *
 * export function MatomoTagManager() {
 *   useEffect(() => {
 *     initTagManager({
 *       url: process.env.NEXT_PUBLIC_MATOMO_URL,
 *       containerId: process.env.NEXT_PUBLIC_MATOMO_CONTAINER_ID,
 *     });
 *   }, []);
 *
 *   return null;
 * }
 * ```
 */
export declare function initTagManager(settings: TagManagerSettings): void;
/**
 * Push an entry to the Matomo Tag Manager `_mtm` data layer.
 *
 * Use it to fire custom events your container's triggers listen to, or to
 * expose variables to your tags. Can be called before `initTagManager` —
 * entries are queued and processed once the container loads.
 *
 * @example
 * ```ts
 * import { pushTagManager } from "@socialgouv/matomo-next";
 *
 * pushTagManager({ event: "order-completed", revenue: 42 });
 * ```
 */
export declare function pushTagManager(entry: TagManagerDataLayerEntry): void;
//# sourceMappingURL=tag-manager.d.ts.map