Education runs on links. Enrolment CTAs in email sequences, QR codes on open-day prospectuses, deep links in SMS reminders that push students to tomorrow's homework, permission-slip URLs in weekly parent bulletins. When the link layer is broken - every campaign with a raw LMS URL, attribution split across a Bitly free tier and a Google Analytics install that fires on 60% of page loads - the question "where do paying students come from?" stays permanently unanswered.
This post covers four EdTech link use-cases (enrolment, parent communications, portal deep links, open-day QR), then what FERPA, COPPA and GDPR actually require, and what Elido can and can't do for a school. I've left out anything I couldn't verify.
For the UTM fundamentals that underpin all of this, tracking UTMs end-to-end is the cornerstone. Come back to this post for the EdTech-specific context.
Use-case 1: course enrolment funnel attribution
A course creator running paid traffic on Meta, Google, and TikTok - plus an email nurture sequence and an organic YouTube channel - needs to know which channel produced each paying student. Without per-channel attribution, budget optimisation is guesswork.
The failure mode is monotonous: one campaign URL (teachable.com/courses/my-course/enroll) gets shared everywhere with the same UTM tag, or no UTM at all. The Teachable dashboard reports total enrolments; the Meta Ads dashboard reports clicks. Nobody can connect the two.
The working pattern is one short link per channel, per campaign, per send. Each link carries a distinct UTM (source, medium, campaign, and content for A/B variants). The short link's click-through data joins to the enrolment confirmation event either via URL parameter passthrough or a conversion webhook from the LMS.
A practical link set for a course launch week:
| Slug | Source | Medium | Notes |
|---|---|---|---|
go.yourcourse.com/e/meta-ig-v1 | meta | paid-social | Instagram feed ad, creative variant 1 |
go.yourcourse.com/e/meta-ig-v2 | meta | paid-social | Instagram feed ad, creative variant 2 |
go.yourcourse.com/e/email-seq3 | nurture | Sequence email 3 of 7 | |
go.yourcourse.com/e/yt-desc | youtube | organic | Channel description link |
go.yourcourse.com/e/partner-{id} | partner | referral | One slug per partner or affiliate |
The e/ prefix scopes all enrolment links in the analytics filter in one click. The short domain (go.yourcourse.com) takes 20 minutes to stand up via CNAME and is a branding signal that the raw teachable.com/courses/...?token=... URL never was.
On UTM discipline: the short-link analytics guide has the full breakdown of which dimensions are load-bearing for funnel attribution.
Use-case 2: K-12 parent communications
A typical primary school newsletter goes out weekly. It contains 8–15 links: the field-trip permission slip, the upcoming school photo order form, the parent-teacher meeting booking, the canteen menu, the term calendar PDF, the three upcoming events, the safeguarding update. The email is sent to 600 parent addresses.
The coordinator has no idea whether parents read any of it. Did 400 of 600 click the permission slip, or 40?
Short links with click tracking answer this directly, as long as the links point at pages with no student-specific data. Each link in the bulletin is a distinct tracked short link. The weekly report shows per-link CTR. The coordinator sees: "permission slip: 87% CTR, canteen menu: 12%, safeguarding update: 6%". The conclusion: safeguarding content needs a different channel (perhaps a banner at collection time); the permission slip format is working.
Operationally, the communications platform (Seesaw, ClassDojo, ParentMail or plain email) swaps raw links for short links before send, either manually, through an integration, or with a spreadsheet that calls the API in batches.
Click records tied to parent emails are personal data under GDPR. EU law doesn't force EU-only storage, but transfers outside the EU need a mechanism, so ask where the data goes. EU data residency for marketing tools explains what "EU storage" claims actually cover.
Use-case 3: student-portal deep linking
An LMS sends an SMS to a student: "You have an assignment due tomorrow in Introduction to Data Science. View it now." The SMS contains a link. That link either:
Option A goes to platform.com/dashboard and the student has to navigate to the right course, the right module, the right assignment from there. Three taps, 45 seconds, high abandonment.
Option B goes to lms.yourschool.edu/a/ds101-wk4-assn which resolves to the deep link platform.com/courses/intro-data-science/modules/week-4/assignment - directly to the assignment - with the session cookie already set from a prior login so the student doesn't authenticate again.
Option B requires that the short link can carry context through the redirect (query parameters passed through to the destination) and optionally trigger an app deep link if the student has the mobile app installed. Deep links without an SDK covers how to handle the mobile routing without requiring the LMS to integrate a native SDK.
The link analytics also show whether the SMS channel works at all: if most students open the message but few click, the problem is the link or the call to action, not the channel.
Use-case 4: university open-day QR campaigns
University admissions teams produce printed prospectuses. The prospectus goes to 40 schools across four open-day roadshow dates in October. Each page has a QR code pointing to the relevant undergraduate programme application page.
Here is the static-QR trap. If the QR codes encode the application URL directly, two things go wrong:
- The form URL changes (it always does - the intake year rolls, the form migrates to a new platform, the university rebrands). All printed prospectuses now point at a dead URL. There is no fix without a reprint.
- There is no per-school attribution. All 40 schools deliver the same QR. The admissions team can't tell whether the roadshow stop at St Joseph's College drove applications or whether those came from the prospectus posted at Sixth Form Centre in another county.
The dynamic-QR pattern fixes both: each prospectus variant gets a distinct short link embedded as the QR destination. apply.youruni.ac.uk/q/st-josephs-oct12, apply.youruni.ac.uk/q/6th-form-centre-oct14. The QR encodes the short link. The short link resolves to the current form URL, which can be updated at any time without reprinting. Per-school click data flows into the admissions dashboard.
The attribution payoff: after the roadshow, the admissions team can answer "which stop drove the most applications?" per programme. If engineering interest skewed heavily toward two schools but law came from a different cluster, the roadshow budget for next year allocates accordingly.
For the full QR production-to-print workflow, the same dynamic-QR architecture is covered in the events post's on-site QR section - the mechanics are identical, the domain is different.
FERPA, COPPA and GDPR: what makes EdTech different
Three regimes show up in education, and none of them is a "link tracking" law. They decide what the people running the links may collect. All sources below were read on 2026-10-25.
FERPA (US, education records). FERPA governs education records held by schools that take US federal funding. The Student Privacy Policy Office explains that an outside party can act as a "school official" if it does a service the school would otherwise use employees for, is under the school's direct control for the use and maintenance of education records, uses the data only for the purpose it was shared, and meets the criteria in the school's annual notice (studentprivacy.ed.gov). A shortener handling a public newsletter link receives no education records. One that stores a student-specific destination or logs student-linked clicks might.
COPPA (US, under 13). The FTC's COPPA FAQ says the Rule protects children under 13, and that personal information includes persistent identifiers such as an IP address or a customer number held in a cookie. It also says passive tracking through a persistent identifier counts as collection (FTC COPPA FAQ). On schools, the FAQ allows a school to consent in place of parents only where the operator collects data for the use and benefit of the school and for no other commercial purpose, with direct notice to the school and the school's ability to review and delete the data. A vendor that logs IPs on links aimed at under-13s needs to meet that, or the links shouldn't be tracked.
GDPR (EU). Article 8 sets 16 as the default age for consent-based processing in online services offered directly to a child, lets member states go lower but not below 13, and requires reasonable efforts to verify parental consent (Art. 8). "GDPR-K" is practitioner shorthand, not a separate law. Most newsletter link tracking relies on a legitimate-interest or contract basis rather than consent, so Article 8 matters mainly when you ask children themselves to consent.
The short version for procurement: when evaluating a URL shortener for school use, ask three questions:
- Where is click data stored, and which sub-processors touch it? Ask for the DPA and the list.
- What does the click log contain? If it keeps full IP addresses, treat it as personal data and set a retention period you can defend.
- Does the redirect set third-party tracking cookies? It shouldn't, for any education use.
Whatever the vendor says, keep student names and IDs out of slugs and destination URLs. A batch label such as class-4b-trip gives you the attribution without a student identity.
GDPR for URL shorteners covers redirect-time data handling and what "EU residency" means at the infrastructure level.
A reference link architecture for a mid-size EdTech operation
This scales from a solo Kajabi creator with an affiliate programme up to a 10,000-student online university.
One short domain, scoped by prefix:
e/- enrolment links (paid ads, email, organic)a/- assignment and LMS deep links (SMS, in-app notifications)q/- print QR codes (prospectuses, flyers, campus signage)r/- affiliate or partner links, one slug eachb/- bulletin links for K-12 parent comms
Three attribution surfaces:
- Enrolment attribution: short-link click-through, then UTM passthrough to the LMS, then the enrolment-confirmed event, then the join in analytics. Answers "which channel produces paying students at what CPA?"
- Engagement metrics: per-bulletin CTR for K-12 comms. Weekly report: which links parents actually clicked. Informs comms format and frequency decisions.
- QR-to-application funnel: per-QR click data from the
q/prefix. Roadshow stop attribution for admissions teams.
Where Elido sits
Elido wasn't built for EdTech, and it has no FERPA or COPPA certification or special school mode. SOC 2 is in preparation and there's no report yet. What it does offer, verified in the product:
- Custom short domains with automatic TLS.
go.yourcourse.comorlinks.yourschool.eduvia a TXT record plus a CNAME toedge.elido.me. Plan limits: Free 0, Pro 1 to 3 depending on size, Business 5 or more custom domains. See custom domains for short links. - Per-link destinations and UTMs. Put the UTM parameters in the destination URL when you create the link, one link per channel or send. Free UTM builder helps with naming.
- Device and OS rules. Smart-link rules on Pro and Business can send iOS, Android and desktop visitors to different destinations, which covers the SMS-to-app case without an SDK. See smart links explained.
- Bulk creation.
POST /v1/links/bulkaccepts up to 100 links per request, enough for a semester's assignment links in a few calls. - Click data: the primary store is in the EU, but redirect nodes in the US and Singapore process visitor requests. The edge truncates the IP (IPv4 /24, IPv6 /48) before the click is stored, while city, coordinates and the full user agent are kept. Clicks expire after the plan window (90 days on Free, one year on Pro, two years on Business). There is no per-workspace region pin. A DPA is available on request, and there are 13 sub-processors on the public list.
- Not available: no COPPA mode and no student-level consent tooling. What does exist is a no-personal-data mode in Settings, Privacy that stops storing IP, user agent, city and the visitor hash for new clicks, and a retention field to shorten how long clicks are kept. If your use case is links aimed at under-13s, ask for the DPA and decide with your data protection officer before enabling tracking.
For the broader analytics picture, the short-link analytics guide linked above covers the metrics hierarchy from raw click volume to revenue attribution - relevant for any EdTech team trying to justify the link infrastructure budget to a finance team.
Related on the blog
- Track UTM campaigns end-to-end without a CDP - the attribution cornerstone this post builds on
- Deep links without an SDK - routing students from SMS notifications to the right LMS page
- GDPR for URL shorteners - the compliance reference for EU schools and EdTech platforms
- Short-link analytics: what to measure - the metrics hierarchy from click volume to enrolment attribution
- EU data residency for marketing tools - what "EU storage" actually requires vs what vendors claim
- URL shorteners for marketers - the broader marketing use-case sibling
Frequently asked questions
Can a school use a URL shortener under FERPA?
Yes, if the vendor never receives student education records, or if it qualifies as a school official: it does a service the school would otherwise staff, works under the school's direct control for use and maintenance of records, uses the data only for the stated purpose, and meets the criteria in the school's annual notice. Links to a public newsletter page carry no records.
Does COPPA apply to click tracking on short links?
It can. The FTC's COPPA FAQ says personal information includes persistent identifiers such as an IP address held in a cookie or logs, and that passive tracking counts as collection. If a link is directed at children under 13, a vendor logging IPs is collecting personal information. Schools can consent for educational use only, not for the vendor's own commercial purposes.
What is the GDPR age of consent for children?
Article 8 sets 16 as the default for consent-based processing in online services offered directly to a child. Member states may lower it, but not below 13. Below the threshold a parent or guardian must authorise consent, and the controller has to make reasonable efforts to verify it.
How do I track which open-day stop drove applications?
Print a different short link in each QR code, one per school or event, and point all of them at the current application page. Click counts per link show which stop produced interest, and you can change the destination later without reprinting.
Should I put student names or IDs in short links?
No. Keep identifiers out of slugs and destination URLs. A batch or campaign label gives you the attribution you need, and click logs then contain no student identity. Elido's click log stores a truncated IP (IPv4 /24, IPv6 /48) plus city and the full user agent, so treat it as personal data under GDPR.
Where does Elido store click data for EU schools?
The primary data store is in the EU. Redirect nodes in the US and Singapore process visitor requests on the way. There's no per-workspace region pin today, so a school with a strict no-transfer policy should read the DPA and sub-processor list first.
Try Elido
Paste a URL, get a working short link
No signup. Link lives for 30 days. Sign up to keep it forever.
Free account required. The free plan includes 25 links in total. Already have an account? Log in