Skip to content

Commit

Permalink
Update analytics.md
Browse files Browse the repository at this point in the history
  • Loading branch information
vincanger committed Sep 16, 2024
1 parent 64356e9 commit c43dd49
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion opensaas-sh/blog/src/content/docs/guides/analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ Then, set up the Google Analytics API access by following these steps:
6. **Encode and add the Credentials:** Add the `client_email` and the `private_key` from your JSON Key file into your `.env.server` file. But be careful! Because Google uses a special PEM private key, you need to first convert the key to base64, otherwise you will run into errors parsing the key. To do this, in a terminal window, run the command below and paste the output into your `.env.server` file under the `GOOGLE_ANALYTICS_PRIVATE_KEY` variable:
```sh
echo -n "PRIVATE_KEY" | base64
echo -n "-----BEGIN PRIVATE KEY-----\nMI...A++eK\n-----END PRIVATE KEY-----\n" | base64
```
7. **Add your Google Analytics Property ID:** You will find the Property ID in your Google Analytics dashboard in the `Admin > Property > Property Settings > Property Details` section of your Google Analytics property (**not** your Google Cloud console). Add this 9-digit number to your `.env.server` file under the `GOOGLE_ANALYTICS_PROPERTY_ID` variable.
Expand Down

0 comments on commit c43dd49

Please sign in to comment.