// Helper: pushes an event to the dataLayer.
// All ad platform tags (GA4, Meta, etc.) are managed in GTM.
function enrolHQPush(eventName, params) {
  window.dataLayer = window.dataLayer || [];
  var payload = { event: eventName, page_location: window.location.href };
  if (params) {
    for (var key in params) {
      if (Object.prototype.hasOwnProperty.call(params, key)) {
        payload[key] = params[key];
      }
    }
  }
  window.dataLayer.push(payload);
}

// Fires when an application for enrolment is submitted
function enrolHQOnEnrolmentSubmitSuccess(payload) {
  enrolHQPush('application_submit', {
    student_profile_id: payload && payload.studentProfileId
  });
}

1. Push student_profile_id to GA4 with each event using the hooks in this article.
2. Register student_profile_id as a custom dimension in GA4.
3. Look up each student's progress through the EnrolHQ API.
4. Combine the two in a spreadsheet or a reporting tool such as Looker Studio.

function enrolHQOnEnquirySubmitSuccess(payload) {
  var enquiries = (payload && payload.enquiries) || [];
  var enquiryIds = enquiries.map(function (e) { return e.id; });
  var studentIds = enquiries.map(function (e) { return e.studentProfileId; });
 
  window.dataLayer = window.dataLayer || [];
  window.dataLayer.push({
    event: 'enquiry_submit',
    enquiry_ids: enquiryIds.join(','),
    student_profile_ids: studentIds.join(',')
  });
}

When a carer pays the enrolment acceptance fee online, the payment success hook fires. Push it to the dataLayer as offer_accepted with the amount paid, and GTM sends it to GA4, Meta and Google Ads as a conversion. Add the following to EnrolHQ's Custom Scripts:

<script>
function enrolHQInitPaymentSuccess(payload) {
  if (!payload || !payload.paymentId) return;
 
  // The payment success page shows again if the carer revisits it,
  // so only send each payment once.
  var sentKey = 'enrolhq_payment_sent_' + payload.paymentId;
  try {
    if (window.localStorage.getItem(sentKey)) return;
    window.localStorage.setItem(sentKey, '1');
  } catch (e) {}
 
  window.dataLayer = window.dataLayer || [];
  window.dataLayer.push({
    event: payload.paymentKind === 'enr-a' ? 'offer_accepted' : 'application_payment',
    student_profile_id: payload.studentProfileId,
    payment_id: payload.paymentId,
    payment_kind: payload.paymentKind,
    value: payload.amount,
    currency: 'AUD'
  });
}
</script>

• Use GA4-style snake_case in an object_action pattern (e.g. enquiry_submit). Title_Snake_Case (e.g. Enquiry_Form_Submission) also works if applied consistently.
• Keep parameter names consistent across events: student_profile_id, enquiry_id, booking_id, event_id, payment_id, payment_kind, value, currency.
• Push one dataLayer event per hook and handle platform mapping in GTM. For example, enquiry_submit triggers GA4 generate_lead, Meta Lead and a Google Ads conversion.
• Map to each platform's standard events. Platforms optimise better on standard events than custom names.
• Mark only primary events as conversions/key events in GA4 and Google Ads. Secondary events and page views dilute bidding.
• Use paymentId as the de-duplication ID (transaction_id in GA4 and Google Ads, eventID in Meta).
• Never push names, emails or phone numbers into the dataLayer. Fetch them server-side through the EnrolHQ API using studentProfileId if ad-platform matching needs them.