To speak about web monetization is to speak about web advertising and user data. When accessing free content you are handing your personal data or getting bombarded with ads. Most likely both. There are a few ways to monetize your content. Let's recap them:- codeburst.io 
- Web Monetization API: A New Web Monetization Alternative- codeburst.io
Web Monetization (WM) is a proposed API standard that allows websites to request a stream of very small payments (e.g. fractions of a cent) from a user. The API's framework provides new revenue models for websites and web-based services and is an alternative to subscription services and advertising, all while preserving the user's privacy. In exchange for payments from the user, websites can provide the user with a "premium" experience, such as allowing access to exclusive content, removing advertising, or even removing the need to log in to access content or services.
# Web Monetization Receivers
This page describes the functions of the Web Monetization (WM) receiver and how existing payment services might become a WM receiver.
A WM receiver is a digital entity that accepts payments over Interledger on behalf of a website and is capable of receiving micropayments.
When a user has Web Monetization enabled in their browser and they visit a monetized website, the browser resolves a unique receiving address for sending payments to the website's WM receiver. The browser then begins sending payments through the user's WM sender.
# Payment pointers
A payment pointer is a unique URL assigned to your payment account by your WM receiver.
The expectation is that a WM receiver will issue one or more payment pointers to its customers and these customers will embed the pointer into the websites they want to monetize. The user's browser then fetches connection details from the pointer to open a payment stream with the WM receiver.
Payment pointers resolve to secure URLs, making it possible for WM receivers to redirect browsers to alternate addresses using standard HTTP redirects.
One benefit of payment pointers is that they provide a level of indirection that allows browsers to protect the privacy of users from their WM senders. Specifically, a browser uses a pointer to request a unique destination address and shared secret from the website's WM receiver. Only the unique destination address for the session is given to the WM sender. This prevents the WM sender from correlating a payment pointer with a website.
# Receiving payments Any entity that is able to accept payments on behalf of websites can be a WM receiver if it supports the necessary protocols. To accept a stream of payments on behalf of its users, a WM receiver MUST support the following protocols from the Interledger stack: