Skip to main content
Element451CRMs and lead management

Inquiries pile up in Element451, but your ads can't say who applied

Admissions sees the inquiry count climb, yet Google Ads and Meta can't tell you which campaigns produced applications, let alone enrolled students. Element451 pushes events like formSubmitted, Application Submit and Event Registration into Google Tag Manager, but nothing fires until someone builds the triggers, and an iframe-embedded form never sees the ad's UTMs. We wire each admissions milestone to the right ad conversion and send applications back from your own Element451 records, so your career college or trade school bids on applicants instead of brochure requests.

Free30 minutesNo obligation

Element451 · what breaks

What goes wrong with Element451 and your ads

  1. 01

    "Google Ads counts more inquiries than Element451 shows"

    Element451 pushes formSubmitted, formSubmittedLong and botSubmitDetected to the data layer. A loose trigger counts bots or a second form event as inquiries, so bidding learns from contacts admissions will never call.

  2. 02

    "The form is on our website, but the UTMs are blank"

    Element451 documents that an iframe embed records activity inside the frame, so parameters on your parent page are lost. Your trade school's paid traffic lands in the CRM looking like direct visits.

  3. 03

    "We can't tell which ads filled the fall cohort"

    Element451 Sources hold only two levels, and its source-tracking guide covers UTMs without ever mentioning a click ID. If nobody keeps the click on the contact, an application submitted weeks later can't be tied back to the ad that started it.

  4. 04

    "Meta optimizes for info requests, not applicants"

    If only the inquiry form reports, Meta chases cheap brochure downloads while the campaigns that drive Application Submit and deposits get no credit and lose budget.

Element451 · the fix

What changes once it's fixed — Element451

  • One conversion per real inquiry

    Triggers keyed to the exact Element451 event names, with botSubmitDetected excluded, so the lead count in Google Ads lines up with your Form Submission activity.

  • Bids tuned to applicants, not form fills

    Application Submit and the application fee become the conversions your campaigns optimize toward, each with its own value, and enrollment joins them once we've confirmed how it leaves your instance.

  • Program-level answers for admissions

    Your director sees which campaigns produced applications for the welding certificate versus the nursing program, straight from Element451 records.

Element451 · architecture

What Element451 actually lets you hook into

All of this comes from Element451's own help center. Where it's silent, we test on your instance.

  1. 1

    Google Tag Manager container, global and per module

    Set once in School Settings for Applications, Appointments, Events, Forms, Messenger, Microsites, Pages, StudentHub and Surveys, with overrides on individual modules.

  2. 2

    Data layer events with metadata

    formSubmitted, formPaymentDone with the paid amount, Application Start, Complete and Submit, Appointment Scheduled and Canceled, and Event Registration, each with IDs and names.

  3. 3

    JavaScript or iframe form embeds

    The JavaScript embed captures URL parameters such as UTMs. The iframe embed doesn't capture the parent page's parameters.

  4. 4

    Webhooks from rules and workflows

    Send-only JSON for one contact record, built from an export template or tokens. 'Succeeded' means sent, not received.

  5. 5

    Zapier triggers and milestone actions

    Triggers include Application Submitted, Application Payment Submitted, Appointment Attended and Decision Released. Milestones such as Enrolled appear only as actions, which is why enrollment export needs checking on each instance.

Element451 · diagnose

Where Element451 tracking breaks, in the order we check

On Element451 the usual fault is a trigger that never fires or fires twice, so triggers come first.

  1. 01

    Confirm the exact event names in GTM Preview

    Element451's own help uses 'Form Submitted' in its setup example and 'formSubmitted' in its event table. A trigger on the wrong spelling never fires.

  2. 02

    Check which form events fire on one test submission

    Confirm whether formSubmitted and formSubmittedLong both fire, and that botSubmitDetected is kept out.

  3. 03

    Find iframe embeds on paid landing pages

    Any iframe form drops the ad's UTMs and click ID unless they're passed in another way.

  4. 04

    Test the click ID on a live contact

    Submit from an ad-tagged URL, open the contact and check whether the gclid survived in the Form Submission URL or a mapped field.

  5. 05

    Check domains and Meta verification

    Pages left on an Element451 primary domain such as page451.sites.451.io sit off your school's domain and aren't indexed, and Meta domain verification works only by DNS TXT on an external domain you've configured.

Element451 · prove

The QA evidence — Element451

Run on live Element451 forms, events and applications, not the form editor preview.

Source of truth

Element451 contact records: Form Submission activities with their submission URLs, event registrations, applications submitted and fees paid, and the Enrolled milestone

  • One inquiry from an ad-tagged URL with the click ID and UTMs confirmed on the Element451 contact.
  • Exactly one lead conversion per inquiry in Google Ads and Meta, with a shared event ID across browser and server.
  • A bot-flagged submission confirmed absent from every ad platform.
  • An Event Registration and an Application Submit each recorded once, under the right conversion action.
  • A webhook or Zap delivery confirmed on the receiving side, not just marked succeeded in Element451.
  • Applications and enrollments matched record by record against imported conversions over a closed window.
  • Repeated 30 days later and whenever a new form, Microsite or application site goes live.

Element451 · free audit

What we check in the free audit

  • Confirm the exact event names in GTM Preview
  • Check which form events fire on one test submission
  • Find iframe embeds on paid landing pages
  • Test the click ID on a live contact
  • Check domains and Meta verification

Checked against

Element451 contact records: Form Submission activities with their submission URLs, event registrations, applications submitted and fees paid, and the Enrolled milestone

Get my free conversion tracking audit

Free30 minutesNo obligation

Element451 · when not to buy

When you don't need us on Element451

Some schools need a short settings fix, and we'll say so.

  • If you don't run paid ads and only want Element451 Sources for college fairs and purchased lists, its built-in source rules cover that.
  • If your GTM triggers already match the documented event names and the ad platforms agree with your Form Submission activities, leave them alone.
  • If nearly all applicants come through Common App or a portal Element451 doesn't host, fix that handoff before tracking anything inside Element451.
  • If the only problem is an iframe embed on one landing page, switching it to the JavaScript embed may be all you need.

Element451 · what we deliver

The event map on Element451

  • Inquiry submitted

    From formSubmitted on an Element451 form or Page, with form name attached. botSubmitDetected is excluded.

  • Open house or info session registered

    From Event Registration, sent to Meta as CompleteRegistration. Campus visit bookings come from Appointment Scheduled.

  • Application started

    From Application Start, kept as a secondary signal so it never competes with submissions in bidding.

  • Application submitted

    From Application Submit, the primary conversion, mapped to SubmitApplication on Meta.

  • Fee paid

    From formPaymentDone on paid forms, which carries paymentAmount and currency, with the Application Payment Submitted Zapier trigger as the server-side record for application fees.

  • Enrolled

    Zapier lists Set Milestone Enrolled only as an action, not a trigger, so we confirm which rule, decision trigger or export can carry enrollments out before importing them. Withdrawals, StudentHub logins and Messenger chats stay out of acquisition.

Written guarantee

95%+ tracking accuracy

Measured against Element451 contact records: Form Submission activities with their submission URLs, event registrations, applications submitted and fees paid, and the Enrolled milestone. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Element451 questions, answered

Its help center mentions logging ad conversions through Google Tag Manager but gives no native Google Ads setup. Conversions are built as GTM triggers on Element451's data layer events, and enrollments go back as offline imports.

Free · 30 min

Find out which ads fill your Element451 pipeline

Free30 minutesNo obligation