This service sits between Firefox and AdZerk. Its purpose is to preserve the privacy of Firefox clients when they request sponsored content (spocs) for the Firefox New Tab. See Sponsored Stories FAQ for more information.

See OpenAPI documentation.

The following steps create a Docker development environment to run this service locally.

1. Install Docker and Docker Compose.
2. In the project root run: docker compose build.
3. Start a mock s3 service: docker compose up s3.
4. Sign up for an account on the MaxMind website.
5. Navigate to the "Download Files" page in your account, download the GeoLite2 City database and copy it to pocket-geoip/GeoLite2-City.mmdb on the mock s3 container.
   1. If the database is stored on s3:

      images/s3/download.sh -b <s3 bucket>
      

   2. If it's stored on disk in a file called GeoLite2-City.mmdb:

      aws --endpoint-url https://localhost:4569 s3 cp GeoLite2-City.mmdb s3://pocket-geoip/GeoLite2-City.mmdb
      

6. Verify that GeoIP2 is available at localhost:4569/pocket-geoip/GeoLite2-City.mmdb.
7. Create a .env file in the project root directory with the following content, replacing <secret> with the respective secret values:

   ADZERK_API_KEY=<secret>
   

8. Start the application containers: docker compose up.
9. Test that the application is running: https://localhost/pulse. It should return {"pulse":"ok"}.

See the Test README.

The first time the service is deployed, follow the steps in the CloudFormation README.

For subsequent deployments:

1. Merge a PR into the main branch.
2. Wait for the new Docker image to be built and uploaded to ECR.
3. Open Fargate in the AWS console and update the service, forcing a new deployment Or, you can increase the number of tasks. Since the task is using the latest tag they should pull in your changes without forcing an update to the task.

The Telemetry Handler is triggered by telemetry from the Firefox discovery stream. It anonymously pings AdZerk to keep track of events related to sponsored content, such as clicks and impressions, in a privacy-preserving way. The event code (or "shim") does not contain any personally identifiable data; we never share personal data with AdZerk.

1. Open telemetry-proxy in the Google Cloud Console
2. Click Edit and paste the new code into the main.py file (do not be confused by the fact the contents of the function are stored in a file named handler.py in this repository and do not rename the file name on Google Cloud).
3. Click Deploy