# Analytics ## How analytics behave by the publish method ### 1- Simple Embed or Custom Domain Integration When Maker content is added via **Simple Embed** or a **Custom Domain integration**, it’s injected directly into your page’s DOM and behaves like any native element. Any trackers or heat-mapping tools already on your site (Google Analytics/GA4, GTM, Segment, Mixpanel, Hotjar, Clarity, etc.) will automatically record page views, clicks, and conversions. ### 2- iFrame Embed or Maker-Hosted URL When Maker content is loaded in an **iframe** or published on a **Maker-generated URL**, it runs in a separate browsing context: * On an iframe, scripts on the parent page **cannot see inside** the frame, so interactions are not logged by default. * On a Maker-hosted URL, your site’s trackers **aren’t present** unless you add them. To capture analytics in these cases, choose one (or both): 1. **Add your trackers to the Maker project** (inject scripts into the page). 2. **Bridge events with `postMessage`** from the iframe to the parent page, then log them with the parent’s trackers. *** ### Examples for iFrame Embed or Maker-Hosted URL Use a prompt/instruction like:\ \&#xNAN;**“Add the following tracking snippet to the `` of every page in this Maker project.”** #### Example: Meta (Facebook) Pixel ```html ``` #### Example: Google Ads ``` ``` ### Bridge iframe events with `postMessage` #### In the Maker (iframe) page — send events ```html ``` #### On the parent page — receive and log ```html ``` **Tips** * Prefer a **specific `targetOrigin`** in `postMessage` (not `'*'`) once you know the parent domain. * Standardize an **event naming convention** (e.g., `snake_case` or `camelCase`). * Ensure **cookie/consent** settings align with your CMP (especially across domains). * If third-party cookies are restricted, cross-domain sessions may fragment; consider first-party GA4 tagging or server-side tagging. ### Tracker verification (recommended) Users can install this plugin to check whether trackers are integrated properly and are firing on the page. Before launch, confirm that all required analytics/pixel tags are installed and firing correctly. * Install a Chrome extension such as **Taghound: Analytics/GTM/Pixel Helper** to inspect tags and events: * Load the page and walk through key flows (page view, add to cart, checkout/purchase). * In the extension panel, verify that GA4/GTM/Meta Pixel (and any other trackers) load and that the expected events fire once with the correct parameters (e.g., currency, value, content IDs). * If your content is in an **iframe** or on a **Maker-generated URL**, run the extension on that page as well (or ensure you’re sending events via `postMessage` to the parent page if needed). * If something doesn’t appear, check: tag installation, consent settings, ad-blockers, and GTM Preview/DebugView for errors.