should i init the mixpanel sdk when i use GTM?

Hi john, Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋

No, you do not need to manually initialize the Mixpanel SDK in your website code when using Google Tag Manager (GTM). When any Mixpanel GTM tag fires, it automatically tries to initialize a new instance using the Initialization Options you configure in the tag. If an instance with the given name has already been initialized on the page, the initialization process will be skipped. You just need to ensure that your Initialization Options are set consistently across your tags in GTM—there’s no need to add a separate init call in your site’s code when using the GTM template Initialization.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Let me check the knowledge base for you again. One moment! 📚

You are correct that if the Mixpanel initialization tag in GTM does not fire before your first event tag, the SDK may not be properly initialized, which can result in a different device ID ($device_id) for the first event compared to subsequent events. This happens because the Mixpanel SDK generates a new device ID upon initialization, and if an event is sent before initialization, it may use a temporary or different ID.To avoid this issue, it is important to ensure that the Mixpanel initialization tag (with Tag Type set to init) is triggered as early as possible in the GTM lifecycle—ideally using the Initialization - All Pages or Consent Initialization - All Pages trigger. This ensures the SDK is initialized and the device ID is set before any other Mixpanel event tags fire. This approach is explicitly recommended in the documentation for both general initialization and for features like Session Replay: > For the Triggering section, you’ll want to choose something early in the GTM lifecycle; typically this is Initialization - All Pages or Consent Initialization - All Pages to ensure that Session Replay starts recording as soon as the GTM container is initialized. Session Replay with GTM> For the Triggering section, choose an early GTM lifecycle event, such as Initialization - All Pages or Consent Initialization - All Pages. InitializationIf you still see a mismatch in device IDs, double-check your GTM tag firing order and make sure no Mixpanel event tags can fire before the initialization tag. This will ensure consistent device/user identification across all events.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Let me check the knowledge base for you again. One moment! 📚

The knowledge sources do not explicitly mention a "send immediately" option for Mixpanel tags in Google Tag Manager (GTM), nor do they describe any specific issues related to using such an option. However, the documentation does emphasize the importance of proper initialization order—specifically, that the Mixpanel initialization tag should fire before any event tags to ensure consistent device/user identification and correct SDK behavior. If an event is sent before the SDK is initialized, it can result in issues such as inconsistent device IDs between the first and subsequent events Initialization.If "send immediately" causes an event to fire before initialization, you may encounter problems like those described above. To avoid this, always ensure the initialization tag is triggered as early as possible (e.g., using the "Initialization - All Pages" trigger) so the SDK is ready before any events are sent.If you need more details about the "send immediately" option or its implications, the knowledge sources do not provide further information.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Let me check the knowledge base for you again. One moment! 📚

I'm sorry, but the knowledge sources provided do not contain detailed information about the "send_immediately" option for the Track Event tag in Google Tag Manager or its behavior in the Mixpanel JavaScript SDK. The documentation does not mention this option or describe any potential issues related to its use.If you are concerned about initialization order or device ID consistency, the documentation does recommend ensuring that the Mixpanel SDK is initialized before any events are tracked, but it does not address the specific impact of "send_immediately" in this context Initialization.If you need more details about "send_immediately," you may want to consult the full Mixpanel JavaScript SDK API reference or reach out to Mixpanel support, as the current knowledge sources do not provide enough information to answer your question confidently.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.