# Edtech deep linking for Indian learning apps: class, test and course links that open the right screen

> Edtech deep linking for Indian apps: class, homework and test links in WhatsApp groups and parent SMS, shared family phones, course offers and children's data.

Source: https://straitlink.in/blog/edtech-deep-linking-india-apps/

A learning app sends more links than almost any other kind of app. There's the live class at 7 pm, the homework due tomorrow, the weekly test, the recorded lecture a student missed, the batch that opens next month, and the course offer that ends on Sunday. Most of them travel through WhatsApp groups run by teachers and coaching centres, or through SMS to a parent's number. **Edtech deep linking** is what decides whether a tap on one of those links lands on the class itself, or on a home screen where a fourteen-year-old has to hunt for it while the class has already started.

This post is for product and engineering teams at Indian edtech and coaching apps.

## The links a learning app actually sends

Write down every moment you send a learner somewhere. For most apps the list looks like this:

| Link | Opens in the app | Without the app |
|---|---|---|
| Live class | The class room, ready to join | The class page on your website, or the store |
| Homework or assignment | The assignment screen | The assignment page after login |
| Test or quiz | The test start screen, with its rules | The store, so the student can install first |
| Recorded lecture | The video at its chapter | The lecture page on your site |
| Result or report card | The result screen after login | The results page after login |
| Batch or course offer | The course page, offer applied | The course page on your site, or the store |
| Invite | The invite screen with the code | The store, with the code kept through the install |

The last column matters as much as the middle one. A parent tapping a result link on a laptop should see your website, not a Play Store page. A student who doesn't have the app yet and taps a test link probably needs the store. In Strait you choose what Android does when the app isn't installed (the store or your website) for the whole workspace, and each link can carry its own `androidFallbackUrl`, `iosFallbackUrl` and `desktopUrl` ([extra link fields](https://straitlink.in/docs/api/)).

## Paths: name the class, never the child

Put the thing in the path, not the person. `/class/phy-11-batch-a/2026-10-07` and `/test/weekly-14` are good paths. `/student/rahul-sharma/test/14` is not, and neither is a path with a roll number, a phone number or an email address.

Two reasons. First, class links get forwarded: a teacher posts one in a group of sixty families, and it ends up in other groups too. Anything in the path is readable by everyone who sees the message. Second, India's Digital Personal Data Protection Act, 2023 treats children's data carefully. Section 9 says a data fiduciary must get verifiable consent from a parent before processing a child's personal data, must not process it in a way likely to harm the child's well-being, and must not track, behaviourally monitor or target advertising at children. We aren't lawyers, and how your app meets Section 9 is a question for your counsel. But a link that carries only a class or test reference keeps the link itself out of that question. Your app works out who the student is after it opens, from the signed-in account.

On the Strait side, a tap keeps the network prefix of the IP address (the first three parts, never the full address), the platform, device class and OS version. When your app reports an open, it stores the host and path of the URL, never the query string ([how we count and what we store](https://straitlink.in/docs/analytics/#what-we-store)). That's one more reason to keep anything personal out of the path. Even so, link analytics on a student's phone is data processing, so include it when you review your consent flow.

## WhatsApp groups: where class links really live

Teachers and coaching centres run their batches on WhatsApp. That shapes three things.

**The preview.** When a link is posted, WhatsApp fetches it to build a card. Give each class or course link a title, description and image, so the card reads "Physics, Class 11, Batch A: today 7 pm" rather than a bare URL. Preview fetches are answered with that card and never counted as taps. Check how a link will look with the [link preview checker](https://straitlink.in/tools/social-preview/).

**The tap.** A tap from WhatsApp either opens your app directly, when the link is verified for your app, or loads inside a browser first. Our [WhatsApp guide](https://straitlink.in/blog/how-to-open-your-app-from-whatsapp-links/) walks through each case and the one-tap "Open in app" page Strait shows when a link opens inside an in-app browser. Before your first batch goes out, run your link domain through the [App Links checker](https://straitlink.in/tools/app-links-checker/): an unverified domain is the usual reason a link opens a web page instead of the app.

**The count.** Without UTM tags, a tap is credited to the in-app browser it came from or the app that referred it, so WhatsApp taps show as `whatsapp`. If you want to tell your own broadcast apart from a teacher's group post, add `utm_source` to the link you hand each teacher. The tap URL's `utm_source` wins over everything else ([how channels are labelled](https://straitlink.in/docs/api/)).

## Parent SMS and DLT

Many schools and coaching centres reach families through SMS to the parent's number: fee reminders, results, the test timetable. In India, business SMS carrying a link only gets through when the link is whitelisted on DLT. Every Strait workspace gets its own subdomain, `<handle>.strait.link`, that carries only your links, so you whitelist one host for all of them. Our [DLT SMS links](https://straitlink.in/blog/dlt-sms-links-india-trai-url-whitelisting/) post has the rules and a setup.

## Parent phone, student phone, shared phone

Edtech is the vertical where "the person who tapped" and "the person who uses the app" are most often different people. Plan for three cases.

1. **The parent's phone has the app, logged in as the parent.** The link should open a parent view of the same thing (the result, the fee, the timetable) or a screen that says "switch to your child's profile to start this test". Decide this in your app's routing, since the link only says what to open.
2. **A shared family phone, with two siblings on one account or two profiles.** Route the link to the class, then check which profile is active. If the class belongs to a different profile, ask before switching. Never let a link silently swap the signed-in child.
3. **The student's own phone, without the app.** This is the deferred case. On Android, Strait sends the tap to Google Play with the link attached, and the Play Install Referrer hands it back to your app on its first open, so the student lands on the test after installing. On iPhone the match after an App Store install is opt-in. See [how deferred deep linking works](https://straitlink.in/docs/deferred-deep-linking/).

One detail that trips up learning apps: after an install, the student has to sign in before the class screen makes sense. Hold the link's destination while sign-in or the OTP screen runs, then open it. Losing it at the login step is the most common way a deferred link "doesn't work" even though it arrived.

## Live-class reminders and links that expire

A live-class link is only useful for a short window. Set `expiresAt` on it and choose what happens after: an "expired" page, the app store, or a web page such as the recording or your class schedule ([when a link expires](https://straitlink.in/docs/short-links/#when-a-link-expires)). Taps on an expired link are recorded with **Sent to: expired** and never billed.

The same goes for course offers. An "admission open till Sunday" link should send people to the current offers page on Monday, not to a price you no longer honour. If the date moves, `PATCH /v1/links/{slug}` changes `expiresAt` without changing the link people already have.

## Invites between students

Students recommend apps to classmates, and parents recommend coaching to other parents. The invite pattern that works today: put the inviter's code in the link's destination query, and read it in `onLink` when the link opens the app. On Android it survives a Play install along with the rest of the destination. Grant any reward on your server, after checking it, not in the app. Strait's referrals feature, which adds a code per tap and a `referral.converted` webhook, is built but in preview and not switched on yet ([referrals docs](https://straitlink.in/docs/referrals/)). Our [referral links post](https://straitlink.in/blog/referral-deep-links-invite-links-survive-install/) covers the details.

## Measuring enrolments, not just taps

Taps tell you a link was used. What you want to know is whether a batch filled. Record the enrolment in the app:

```ts
links.trackEvent('enrolment', { value: 4999, currency: 'INR' });
```

The SDK attaches the tap id of the most recent link open within the last 7 days, so the enrolment lands on that tap's channel, campaign and link ([events and revenue](https://straitlink.in/docs/sdks/react-native/events/)). Use any event name you like: `trial_started`, `test_submitted`, `enrolment`. Each app open also says whether it was the first launch after an install or an existing user, which answers a useful question about a course campaign: new students, or the same ones again?

## A checklist before a new batch launches

- [ ] App Links verified for your link domain ([App Links checker](https://straitlink.in/tools/app-links-checker/)), and Universal Links if you ship on iPhone
- [ ] Paths carry class, test or course references, never student names, roll numbers or phone numbers
- [ ] Title, description and image set on class and course links, and the WhatsApp card checked
- [ ] The app holds the link's destination through sign-in and OTP after an install
- [ ] Live-class and offer links set to expire, with a sensible page afterwards
- [ ] `trackEvent` firing once per enrolment, with value and currency
- [ ] Tapped on a real phone from a WhatsApp group, with the app installed and without it

## What we haven't tested

We haven't recorded an edtech flow end to end on a real phone: a class link from a WhatsApp group, through a Play install, sign-in and a profile switch. The pieces underneath (the Play install referrer hand-off and the open report) were tested on a real Android phone with a Google Play internal testing build. The sign-in and profile logic is your app's code, so test it on a real phone before a batch launches. On iPhone, Universal Links were tested on a real iPhone (iOS 26) in October 2026; install matching is opt-in (off until you turn it on in **Settings → iPhone installs**) and proven on iPhone simulators; the real-iPhone run waits on our App Store listing.

## Sources and how we checked

- Digital Personal Data Protection Act, 2023, [Section 9: processing of personal data of children](https://indiankanoon.org/doc/98869575/): verifiable parental consent, no processing likely to harm a child's well-being, and no tracking, behavioural monitoring or targeted advertising directed at children. Read on 5 October 2026. This is a summary, not legal advice.
- Link fields (platform fallbacks, title, description and image, expiry and expired-link actions, `PATCH` of `expiresAt`), the channel order, the workspace subdomain and what taps and opens store come from Strait's engine code and its [REST API](https://straitlink.in/docs/api/), [short links](https://straitlink.in/docs/short-links/) and [analytics](https://straitlink.in/docs/analytics/) docs.
- The 7-day rule for attaching a tap to an event is from the SDK code and the [events and revenue](https://straitlink.in/docs/sdks/react-native/events/) docs. Referrals being in preview is from the [referrals docs](https://straitlink.in/docs/referrals/).
- Deferred links after a Play install were tested on a real Android phone with a Google Play internal testing build (October 2026).
