Purpose: Understand how visitors use your marketing pages (traffic, campaigns) when you use Google Analytics.

Before you enable it

• Your institute should have a Google Analytics property and a measurement ID configured on the server by your technical team.
• Your privacy policy should state that you use analytics cookies and link to Google’s policies where required.

How to enable (admin steps)

1. Open Site content → Site header.
2. Turn on Google Analytics.
3. Save and publish changes.
4. Ask your technical team to confirm the measurement ID is set in the server environment and that the site has been redeployed if needed.

Analytics scripts load only after a visitor accepts analytics cookies (or accepts all). If a visitor rejects analytics, learning features still work; only measurement is skipped.

Purpose: Let students register and log in with an existing Google or Facebook account instead of remembering another password.

Before you enable it

• Your technical team must register OAuth applications with Google and Facebook and store the credentials on the server.
• Update your privacy policy to list these providers.
• Visitors need functional cookies (or accept all) for sign-in buttons to behave as expected.

How to enable (admin steps)

1. Open Site content → Site header.
2. Enable Google sign-in and/or Facebook sign-in as required.
3. Save and publish.
4. Test from a private browser window: open Login, accept cookies if prompted, and confirm the buttons appear and complete sign-in.

LinkedIn sign-in is not available in eMedhaa; plan communication accordingly.

When enabled on the site header, students may sign in with a one-time code sent to their mobile number, subject to SMS configuration on the server.

What you gain: Faster registration, fewer password resets, and analytics only when visitors consent: without exposing complex technical setup to teachers or students.