Future Makers
Career Guide Platform

4.1 - iframe Implementation

The platform uses a standard <iframe> embed. No additional libraries are required on the parent page.

The iframe-resizer library is not currently implemented in the platform. At this stage, we recommend testing the standard embed before introducing any additional iframe libraries. If automatic height adjustment is needed after testing, this can be scoped as a follow-on development item.

4.2 - Height Strategy

Because the platform manages its own internal scroll, the recommended approach is to set height: 100vh on the iframe so it fills the full browser viewport height. This gives the cleanest user experience across devices.

1. Full viewport height (recommended): height: 100vh - the platform scrolls internally.
2. Fixed minimum height: A static min-height (e.g. 900px) is a simpler fallback but may clip content on shorter viewports.
3. Direct link: Linking to https://futuremakers.amanz.nz/ in a new tab avoids all iframe constraints entirely and is a valid option.

4.3 - What the platform provides

5.1 - iframe Embedding Permission

Before embedding, AMA must confirm with the platform hosting provider that futuremakers.amanz.nz is permitted to be framed from www.amanz.nz. This is a hosting-level configuration. Flume does not need to take any action - this is an item for AMA to resolve prior to go-live.

5.2 - iframe Attributes

7.1 - Two separate reporting layers

Acquisition and engagement are measured by two independent systems. They do not share data automatically and must not be read as a single source.

7.2 - iframe isolation (important)

iframes are isolated browsing contexts. AMA GA4 records the /careerguide pageview when the parent page loads, but it does not automatically capture interactions that happen inside the iframe. Conversely, the Career Guide's in-app tracker reads only the iframe's own URL — it cannot read the parent AMA page URL (cross-origin restriction). The two systems therefore measure different things by design.

7.3 - Forwarding campaign UTMs into the Career Guide (required for embedded attribution)

When a visitor lands on the AMA /careerguide page with UTM parameters (for example /careerguide?utm_source=facebook&utm_medium=social&utm_campaign=summer_2026), those parameters live on the parent URL. For the in-app tracker to attribute in-guide activity to that campaign, the parent page must pass the query string into the iframe src. Add this script immediately after the embed snippet:

<script>
  // Forward UTM / campaign params from the AMA page URL into the Career Guide iframe
  (function () {
    var qs = new URLSearchParams(window.location.search).toString();
    var iframe = document.getElementById('future-makers-embed');
    if (!iframe) return;
    iframe.src = qs ? 'https://futuremakers.amanz.nz/?' + qs
                    : 'https://futuremakers.amanz.nz/';
  })();
</script>

Once forwarded, the Career Guide captures the UTM parameters on entry, stores the first-touch campaign in the browser (persistent) and the current-session campaign (session), and attaches them to every in-app event recorded during that visit — so a later action such as downloading the guide still carries the campaign that brought the visitor in.

7.4 - Confirming AMA GA4 is recording /careerguide

Whether AMA GA4 is recording users and sessions arriving at /careerguide can only be confirmed from within AMA's own GA4 property. The Base44 environment does not have access to AMA's GA4 property and cannot independently verify it.

To verify, AMA needs to confirm one of the following:

• The GA4 tag / Measurement ID is present on the /careerguide page (check with Google Tag Assistant or GA4 DebugView), and
• GA4 is recording page_view events for /careerguide, and users/sessions are appearing in the GA4 Realtime and standard reports.
• Alternatively, share read access to the AMA GA4 property so the recording of /careerguide traffic can be independently confirmed.