Ensure that no resources are required from external domains

[cbunicef]

As a USER that doesn't have a data package, when I access IoGT for free through my MNO I don't want my experience to be disrupted when external resources don't load.

As a USER I want to be sure that I am not using up my data package if I've been told IoGT is free through my MNO.

Implications on external dependencies (as I understand them, please add)

Critical to address:

• https://fonts.googleapis.com/icon?family=Material+Icons (I assume this is layout-breaking if it doesn't load)

Important to address:

• Google Analytics (replace with server-side tagging https://developers.google.com/tag-platform/tag-manager/server-side/intro)

Unknown:

• http://www.w3.org/2000/svg (unsure whether this xmlns tag actually calls the destination URL)

Urgent tag only applies to Critical items.

[sheralim012]

for google analytics to honor facebook free basics we will have to deploy google tagging server ourself, here are the steps to deploy it manually. After that we have to configure our django app to use it which can be found here and here.

[geoo89]

Reopening and removing the urgent tag to keep track of the less urgent items.

[cbunicef]

There are still fonts being pulled from Google domains:

Adding urgent tag until that is sorted out.

Locally-served fonts is a must-have for Go Live.

[cbunicef]

Re-opening issue to track Google Analytics server-side - this is actually important to get in the next major release.

[cbunicef]

I was taking a look at #1186 and I just want to make sure that this PR works without Javascript and doesn't require calls from a user device to external servers. We need this for tracking to work on feature phones and Free Basics. For reference, the V1 GA solution doesn't have any GA-related code on the user-facing site from what I can see. Maybe this is an intermediary step?

However, good to note that we will need Javascript on the user-facing site in order to eventually accomplish #1196.

@ChrisMarsh82 maybe we can catch up on this during our Monday meeting

[istride]

One of the problems with the server-side GTM container approach is that it still relies on javascript or iframe elements, both of which are not allowed under Free Basics.

In V1, analytics is implemented via a combination of django-google-analytics-app and some custom middleware (MoloGoogleAnalyticsMiddleware, IogtMoloGoogleAnalyticsMiddleware). I suggest we follow a similar approach.

@ChrisMarsh82 @sheralim012

[cbunicef]

This is long resolved