LoupeED FAQs

Question 1

What is LoupeED?

Accepted Answer

LoupeED is a CRM-native intelligence platform built on Salesforce. It pulls online engagement signals into a single, real-time timeline inside the records your enrolment, student success, and alumni teams already work in.

What your teams learn about a person shapes what that person experiences next. Website content adjusts to reflect where someone is in their student journey. Outreach is triggered by what they actually did, not a generic communications schedule. Enrolment conversations open with real context. Where a decision involves more than one person, such as a student and a parent weighing an offer together, LoupeED creates shared spaces in which each of them sees content matched to their own questions.

Question 2

What does LoupeED solve for me?

Accepted Answer

Most institutions are data rich and insight poor. What a prospective student does across your website sits apart from what the enrolment team can see, and by the time someone assembles the picture the moment to act has passed. LoupeED closes the distance between signal and action by surfacing engagement inside the CRM as it happens.

When your teams work from what is actually happening rather than guessing, the conversations change. A prospective student hears from you about the programme they keep returning to. An offer-holder gets help with the visa or accommodation step they are stuck on. A student going quiet is noticed while there is still time to do something about it. Alumni are approached as people you know rather than names on a list.

Stronger yield, less melt, and better retention follow from getting those interactions right.

Question 3

How does LoupeED work?

Accepted Answer

LoupeED sits inside your Salesforce CRM and connects to your websites through a lightweight browser layer called Send2CRM, which captures behavioural and form data and streams it into Salesforce in real time. The connection runs both ways, so information from the CRM also flows back to the website to shape what each visitor sees.

Data processing and intelligence logic live inside the CRM. There is no third-party data store and no separate platform for your team to maintain.

Question 4

Does LoupeED work with any website technology?

Accepted Answer

Yes. LoupeED runs as client-side script in the visitor's browser, so it does not depend on a particular website platform or content management system. That matters in a sector where the main institution site, the faculty sites, and the campaign microsites are rarely built on the same thing.

The same approach also works in web workers and server-side applications for advanced use cases.

Question 5

Where is data collected from website visitors stored?

Accepted Answer

In your Salesforce org.

A managed package extends the Salesforce data model to hold website session information, and LoupeED acts when new engagement occurs. Because the intelligence layer lives in the CRM rather than on the website, it works across whatever web platforms your institution runs and stays straightforward to maintain.

No third-party data store, no offshore routing, and no external servers sit between your visitors and your CRM. Where data residency is a condition of doing business, the data stays in the Salesforce region your institution already holds.

Question 6

How does LoupeED keep the CRM updated as students browse the website?

Accepted Answer

When someone submits a form or returns to the site, their Salesforce record updates with the new behavioural and form data. The browser also sends ongoing updates during the session and when the session closes. Update frequency is configurable and runs in the background, so it does not affect how the website performs through peak periods such as results release or clearing.

Question 7

How does LoupeED handle the large volumes of data from website interactions?

Accepted Answer

CRMs are not built to hold raw clickstream data, and storing it there creates performance and cost problems. LoupeED summarises and aggregates behavioural signals before storing them, keeps only the history from the most recent sessions, and retains it only for people who have identified themselves. Open days and application deadlines produce sharp traffic spikes; you get the intelligence without the storage overhead.

Question 8

How is data privacy and consent management handled?

Accepted Answer

LoupeED integrates with consent management platforms such as OneTrust. No personal or behavioural data reaches Salesforce unless the visitor has opted in, and consent state is honoured everywhere the platform operates.

Institutions holding applicant, student, and visa-linked data are right to examine this closely. We can walk your data protection officer through exactly what is captured, where it is stored, who can see it, and what audit evidence LoupeED produces, so your own compliance team can map that to the obligations you work under.

Question 9

How does LoupeED identify website visitors?

Accepted Answer

LoupeED matches website visitors to existing Salesforce records using first-party identifiers such as email address and phone number, captured through forms and other identified interactions. A prospectus request or an open day registration turns months of anonymous browsing into a timeline attached to the right person.

It works without third-party cookies, so identity resolution holds up as browser restrictions and privacy regulation tighten. It is built into the foundation, not a bolt-on.

Question 10

How does LoupeED work alongside our website analytics?

Accepted Answer

Analytics tells you that someone viewed the entry requirements page three times. LoupeED tells you it was an applicant to civil engineering, and updates their Salesforce record with the signal.

It also keeps people apart who analytics treats as one audience. When a student and a parent are both researching, each is their own person in Salesforce with their own engagement history, and those are two different conversations. LoupeED can pass consistent visitor identifiers to providers like Google Analytics as well, so you can stitch together a full student journey rather than a run of disconnected sessions.

Question 11

Does LoupeED replace our marketing automation platform?

Accepted Answer

No. It complements it.

Marketing automation works well for people you already know and need to communicate with. It works best once someone sits in your CRM with a name, a history, and a segment. Where it falls short is before that moment.

LoupeED handles first-party identification and the understanding of people you do not yet know. It resolves anonymous website visitors into real people, builds a picture of what they were weighing up long before they raised their hand, and feeds that into the CRM so your communications tools have something meaningful to act on.

The two work better together. LoupeED fills the gap your existing tools cannot see.

Question 12

Does LoupeED work without Salesforce?

Accepted Answer

Not currently. LoupeED is a Salesforce-native product. Its value comes from putting student intelligence inside the system your enrolment, student success, and alumni teams already use.

Support for other CRMs is something we review regularly.

Question 13

How does LoupeED use AI?

Accepted Answer

LoupeED includes templates for AI agents that work from the engagement signals already flowing into the CRM. The agents reason over what a person actually did and act with human oversight, whether that is drafting a follow-up the enrolment officer reviews before it goes out, suggesting the next piece of content for an offer-holder who has gone quiet, or flagging a student whose engagement is dropping away.

The agents are tailored to your institution and learn from your own context. Because they are grounded in real behaviour, what they surface is evidence rather than assumption.

Question 14

What's the difference between Connect, Understand, Engage, and Guide?

Accepted Answer

Connect to Guide is our capability framework. It organises LoupeED's features into four progressive stages, from foundational data capture through to orchestrated student journeys. Connect, Understand, Engage, and Guide. If you are not sure where these fit the student journeys you are building, talk to us and we will work through it with you.

Question 15

How does pricing work?

Accepted Answer

LoupeED pricing is shaped to the size of your institution, the scale of your student body, and which capabilities you activate across Connect, Understand, Engage, and Guide. What each is worth depends on the journeys you run and the teams that run them.

Tell us what you are trying to change. We will come back with a quote that fits.

Question 16

Is there a minimum contract term?

Accepted Answer

The default minimum term is 12 months, invoiced annually upfront. We also offer trials so you can see LoupeED working with your own data before you commit.

Question 17

Can I switch tier at any time?

Accepted Answer

Yes. You can move between Understand, Engage, and Guide within your contract term. Any change in cost is prorated to the end of the term.

Institutions often start with one team, usually enrolment or alumni relations, then widen out once the signals are proving useful. Our account management team can help you work through the right move.

Question 18

Do we need Salesforce Education Cloud to use LoupeED?

Accepted Answer

No. LoupeED is built on the core Salesforce platform and connects to Salesforce CRM, so it runs alongside Education Cloud and the Education Data Architecture without depending on either of them. It works just as well at institutions where Salesforce is a service desk today and the industry cloud is still a plan.

What LoupeED does require is Salesforce Sales Cloud, Enterprise or Unlimited edition. The reason is API access. Everything LoupeED does runs through the connection between the visitor's browser and your Salesforce org, and that access is included as standard from Enterprise edition upward.

LoupeED is licensed separately from Salesforce, so adopting it doesn't mean buying more Salesforce first, as long as you already hold a supported edition. And if Education Cloud is on your roadmap, LoupeED will already be running and feeding it by the time you arrive.

Question 19

Are additional Salesforce licenses also required?

Accepted Answer

LoupeED requires Salesforce Sales Cloud Enterprise or Unlimited edition, as it includes a managed package and uses Salesforce Web APIs.

During installation you'll also need to allocate one Salesforce user license to act as the integration user between your website and Salesforce. These Salesforce licensing requirements are separate from LoupeED's own licensing.

If you're on a lower edition, or you aren't sure what your institution already holds across faculties and professional services teams, talk to us before implementation.

Question 20

What billing options do you support?

Accepted Answer

LoupeED is licensed annually with invoicing by bank transfer. We currently bill in USD, AUD, GBP, and NZD to support institutions across our markets. Annual invoices are issued around 90 days before renewal, which gives procurement room to work inside the budget cycle.

Contact our account management team if you'd like to discuss currency or payment arrangements for your region.

Question 21

What's involved with implementation?

Accepted Answer

Implementation is handled by FuseIT's in-house team or one of our implementation partners in your region, as part of onboarding. We install the managed package, connect your websites, configure the data mappings and automations to match how your teams actually work, and bring people on board so they are using the signals from day one.

Most institutions are live in days or weeks rather than months, so the work does not have to be scheduled around the next academic year.

Question 22

Can I host the LoupeED JavaScript libraries myself?

Accepted Answer

Yes. The browser libraries LoupeED is built on are provided on a public content delivery network so you can get started quickly, and many institutions choose to host them on their own domain or chosen CDN instead.

Hosting them yourself stops third-party CDNs from seeing your visitors, removes the dependency on someone else's uptime, and lets your IT team audit the library before it goes anywhere near the institution website.

Question 23

Where can I get help?

Accepted Answer

Visit our support centre at /support for assistance.

LoupeED FAQs

Frequently Asked Questions

See it with your own student journey

Consent preferences