cb4eaaab6d
Script component manages the cache as src or id. But in this example, id is missed. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `yarn lint` |
||
---|---|---|
.. | ||
lib | ||
pages | ||
public | ||
.env.local.example | ||
.gitignore | ||
package.json | ||
README.md |
Example app using Google Tag Manager
This example shows how to use Next.js along with Google Tag Manager. pages/_document.js
is used to inject base code. pages/_app.js
is used to track route changes and send page views to Google Tag Manager.
Deploy your own
Deploy the example using Vercel:
How to use
Execute create-next-app
with npm or Yarn to bootstrap the example:
npx create-next-app --example with-google-tag-manager with-google-tag-manager-app
# or
yarn create next-app --example with-google-tag-manager with-google-tag-manager-app
# or
pnpm create next-app -- --example with-google-tag-manager with-google-tag-manager-app
Next, copy the .env.local.example
file in this directory to .env.local
(which will be ignored by Git):
cp .env.local.example .env.local
Set the NEXT_PUBLIC_GOOGLE_TAG_MANAGER_ID
variable in .env.local
to match your Google Tag Manager ID.
Deploy it to the cloud with Vercel (Documentation).