Next.js Tracking Platform

A Next.js component that allows easy integration of multiple tracking tools such as Google Tag Manager, Google Ads, Facebook Pixel, Hotjar, and LinkedIn.

Compatible with both JavaScript and TypeScript, it enables developers to implement tracking in their web applications quickly and efficiently.

Compatible with Next.js 9.5.0+.

💻 Installation

npm install next-tracking-platform

⌨️ Usage

• JavaScript

import Tracking from 'next-tracking-platform';

const App = () => (
  <Tracking id="GTM-XXXXXXX" platform="googleTagManager" />
  <Tracking id="FB-XXXXXXX" platform="facebookPixel" />
);

• TypeScript

import React from 'react';
import Tracking from 'next-tracking-platform';

const App: React.FC = () => (
  <Tracking id="GTM-XXXXXXX" platform="googleTagManager" />
  <Tracking id="FB-XXXXXXX" platform="facebookPixel" />
);

📱 Supported Platforms

• Google Tag Manager
• Google Ads
• Facebook Pixel
• Hotjar
• LinkedIn

⚡ Compatibility

• Next.js: Version 9.5.0 or higher

🫰 How to Contribute

1. Fork the Repository: Click the "Fork" button at the top right of the repository page to create your own copy of the project.

2. Clone Your Fork: Clone your forked repository to your local machine:

git clone https://github.com/your-username/next-tracking-platform.git

3. Create a Branch: Before making any changes, create a new branch:

git checkout -b feature/your-feature-name

4. Make Your Changes: Implement your feature or fix the issue you are addressing. Be sure to adhere to the coding standards used in the project.

5. Write Tests: If applicable, write tests for your new feature or bug fix to ensure that it works correctly and does not introduce regressions.

6. Update Documentation: If your changes affect the usage or functionality of the component, update the documentation accordingly.

7. Commit Your Changes: Use clear and descriptive commit messages. Follow this format:

git commit -m "Add feature: description of your feature"

8. Push Your Changes: Push your changes to your forked repository:

git push origin feature/your-feature-name

9. Open a Pull Request: Go to the original repository and create a pull request. Provide a clear description of the changes you made and why they should be merged.

👌 Best Practices

• Follow Coding Standards: Adhere to the coding standards used in the project, including naming conventions and file organization.
• Keep Changes Focused: Ensure that your changes are focused on a single issue or feature to make it easier to review.
• Communicate Clearly: If you are working on a larger feature, consider discussing it with the maintainers or community before starting to ensure alignment with the project goals.

Thank you for your interest in contributing to the Next Tracking Platform!

Your contributions help improve the project for everyone.

🫂 Contribuidores

Contributions are welcome!

Feel free to submit a pull request or open an issue to discuss improvements.

🧾 License

MIT