Skip to main content
PopuliCRMs and lead management

Your ads fill the Populi inquiry list, but Google can't see who enrolls

Your Populi inquiry form and initial application sit in an iframe, so your tags see a visit and then nothing. Google Ads and Meta optimize for page views while your admissions team watches leads move from Inquiry to Enrolled inside Populi. We catch the two events Populi already sends out of the frame, then feed accepted and enrolled students back from Populi's webhooks, so campaigns learn from people who start class.

Free30 minutesNo obligation

Populi · what breaks

What goes wrong with Populi and paid ads

  1. 01

    "Google says zero leads, but our inquiry list is full"

    The form lives in a Populi iframe, so a submit never reaches your page's tags unless someone listens for it. You keep paying for clicks while Smart Bidding has no inquiries to learn from.

  2. 02

    "Every inquiry counts the same, even the ones that never apply"

    Even when someone wires up the inquiry message, a three-field Name, Email, Message inquiry counts the same as a finished application with a paid fee, so Meta learns to find people who ask questions, not people who enroll in your HVAC or massage therapy program.

  3. 03

    "The lead source just says 'Website'"

    Populi ties a lead source to the embed code you pasted, not to the ad someone clicked, so Google, Meta and organic visitors through one form share a source and you can't say which campaign filled the class.

  4. 04

    "We find out who enrolled weeks later, and the ads never do"

    Accepted, Confirmed and Enrolled happen in Populi weeks after the click. Without them, your ad accounts keep rewarding the cheapest inquiry.

Populi · the fix

What changes after we fix it — Populi

  • Inquiries and application starts counted once

    Populi's own submit messages fire one conversion each, with a shared event ID so the browser and server copies never double count.

  • Campaigns judged by students who enroll

    Lead Status Updated webhooks send Accepted and Enrolled back to Google Ads and Meta, so bidding favors the ads that produce real starts.

  • A source you can trust per campaign

    Ad traffic gets its own lead source and embed, and the click ID is kept first-party on your site, so admissions reports and ad reports finally line up.

Populi · architecture

What Populi actually lets you hook into

Populi has no built-in Google Ads, GA4 or Meta Pixel setting. What it does document is enough to build tracking properly, as long as each piece is wired outside the iframe.

  1. 1

    Embed codes for inquiry and application forms

    Copied from Admissions settings, with a lead source chosen per code. The initial application is a gateway: after it, the applicant moves on to the main application form.

  2. 2

    Iframe messages to the parent page

    Populi documents two: populi.inquiry.submitted when an inquiry form is sent, and populi.application.start when the initial application form is submitted.

  3. 3

    Webhooks with signed payloads

    Account Admins can subscribe to events including Inquiry Created, Lead Status Updated, Application Status Updated and Application Fee Paid, each signed with an RSA SHA256 header we verify.

  4. 4

    REST API and Zapier

    The current API exposes inquiries, leads and applications with source and status fields. Populi's Zapier integration needs an invite from Populi support.

  5. 5

    Custom CSS only, no script field

    The settings we found allow styling the embedded application, not adding tags inside it. Confirm on your account whether anything else is available.

Populi · diagnose

Where Populi tracking breaks, in the order we check

The iframe is usually the first break; mislabeled lead sources are the second.

  1. 01

    Does anything listen for Populi's messages?

    Submit a test inquiry and watch whether a tag fires on the parent page. Usually nothing does.

  2. 02

    Which lead source did each embed get?

    Check every pasted code. Ad landing pages often reuse the main website embed.

  3. 03

    Is the click ID kept before the form?

    Load a page from an ad-tagged URL and confirm the GCLID or fbclid is stored first-party before the visitor reaches the iframe.

  4. 04

    Do later statuses go anywhere?

    Look for webhooks on Lead Status Updated and Application Status Updated. Without them, enrollment never reaches the ads.

  5. 05

    Are fee payments mixed with enrollment?

    An application fee and an enrolled student need separate events and values.

Populi · prove

The QA evidence — Populi

Run on the live page that holds your Populi embed, from ad-tagged URLs, not from Populi's form preview.

Source of truth

Populi Admissions records: inquiries, applications and lead statuses by date, lead source and program

  • One test inquiry from an ad-tagged URL, firing exactly one conversion with a shared event ID.
  • One initial application submitted, with the application-start event confirmed in Google Ads and Meta.
  • An application fee payment recorded at the right value and a waived fee confirmed absent.
  • Enrolled leads from a closed term matched record by record against each ad platform.
  • Repeated after the next start date and after any change to the embed or website template.

Populi · free audit

What we check in the free audit

  • Does anything listen for Populi's messages?
  • Which lead source did each embed get?
  • Is the click ID kept before the form?
  • Do later statuses go anywhere?
  • Are fee payments mixed with enrollment?

Checked against

Populi Admissions records: inquiries, applications and lead statuses by date, lead source and program

Get my free conversion tracking audit

Free30 minutesNo obligation

Populi · when not to buy

When a Populi school doesn't need us

Some Populi schools need a quick answer, not a project.

  • If you don't run paid ads and recruit through referrals, high school visits or employer partners, Populi's lead source reports already answer your questions.
  • If you only want inquiry counts in GA4 and no bidding depends on them, a developer can add Populi's documented message listener in an afternoon.
  • If your full application lives on a separate site and Populi only receives imported leads, the tracking work belongs on that site first.
  • If you enroll a handful of students a term, offline matching by hand may be enough, and we'll tell you so.

Populi · what we deliver

The event map on Populi

  • Inquiry submitted

    From the populi.inquiry.submitted message the iframe sends to your page. The top-of-funnel lead, low value.

  • Application started

    From the populi.application.start message after the initial form, the point where Populi creates the lead and asks for contact details.

  • Application fee paid

    From the Application Fee Paid webhook, valued at the fee you set. Waived fees and discount-code zero charges are excluded.

  • Application completed

    From the lead status moving to Application Completed: a qualified applicant your team now has to decide on.

  • Accepted and Confirmed

    Sent server-side when the status changes, so campaigns learn which applicants your school actually wants and which ones commit.

  • Enrolled

    The main conversion, fired when Populi marks the lead Enrolled after course registration. Applications marked Declined or Withdrawn never fire it.

Written guarantee

95%+ tracking accuracy

Measured against Populi Admissions records: inquiries, applications and lead statuses by date, lead source and program. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Populi questions, answered

Not through a built-in setting we could find in Populi's documentation. Tracking is built around it, using the iframe messages, webhooks and API Populi does document.

Free · 30 min

Find out which ads bring students Populi marks Enrolled

Free30 minutesNo obligation