old_contents: """
  ==============================
  Mixpanel -- event tracking
  ==========================
  
  Mixpanel_ tracks events and actions to see what features users are using
  the most and how they are trending.  You could use it for real-time
  analysis of visitor retention or funnels.
  
  .. _Mixpanel: http://www.mixpanel.com/
  
  
  .. mixpanel-installation:
  
  Installation
  ============
  
  You only need to do perform these steps if you are not using the
  generic :ttag:`analytical.*` tags.  If you are, skip to
  :ref:`mixpanel-configuration`.
  
  In order to use the template tag, you need to add
  :mod:`analytical.mixpanel` to the installed applications list in the
  project :file:`settings.py` file::
  
      INSTALLED_APPS = [
          ...
          'analytical.mixpanel',
          ...
      ]
  
  The Mixpanel Javascript code is inserted into templates using a
  template tag.  Load the :mod:`mixpanel` template tag library and
  insert the :ttag:`mixpanel` tag.  Because every page that you want
  to track must have the tag, it is useful to add it to your base
  template.  Insert the tag at the bottom of the HTML head::
  
      {% load mixpanel %}
      ...
      {% mixpanel %}
      </head>
      <body>
      ...
  
  
  .. _mixpanel-configuration:
  
  Configuration
  =============
  
  Before you can use the Mixpanel integration, you must first set your
  token.
  
  
  .. _mixpanel-api-key:
  
  Setting the token
  -----------------
  
  Every website you track events for with Mixpanel gets its own token,
  and the :ttag:`mixpanel` tag will include it in the rendered Javascript
  code.  You can find the project token on the Mixpanel *projects* page.
  Set :const:`MIXPANEL_TOKEN` in the project :file:`settings.py` file::
  
      MIXPANEL_TOKEN = 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
  
  If you do not set a token, the tracking code will not be rendered.
  
  
  .. _mixpanel-internal-ips:
  
  Internal IP addresses
  ---------------------
  
  Usually you do not want to track clicks from your development or
  internal IP addresses.  By default, if the tags detect that the client
  comes from any address in the :const:`INTERNAL_IPS` setting, the
  tracking code is commented out.  See :const:`ANALYTICAL_INTERNAL_IPS`
  for important information about detecting the visitor IP address.
  
  
  .. _mixpanel-identify-user:
  
  Identifying users
  -----------------
  
  If your websites identifies visitors, you can pass this information on
  to Mixpanel so that you can tie events to users.  By default, the
  username of an authenticated user is passed to Mixpanel automatically.
  See :data:`ANALYTICAL_AUTO_IDENTIFY` for important information about
  detecting authenticated visitors.
  
  You can also send the visitor identity yourself by adding the
  ``analytical_identity`` variable to the template context::
  
      context = RequestContext({'analytical_identity': identity})
      return some_template.render(context)
  
  If you can derive the identity from the HTTP request, you can also use
  a context processor that you add to the
  :data:`TEMPLATE_CONTEXT_PROCESSORS` list in :file:`settings.py`::
  
      def identify(request):
          try:
              return {'analytical_identity': request.user.email}
          except AttributeError:
              return {}
  
  Just remember that if you set the same context variable in the
  :class:`~django.template.context.RequestContext` constructor and in a
  context processor, the latter clobbers the former.
  """
  
  mixpanel_service = {
      'head_bottom': 'analytical.mixpanel.templatetags.mixpanel.MixpanelNode',
  }
  
new_contents: """
  ==========================
  Mixpanel -- event tracking
  ==========================
  
  Mixpanel_ tracks events and actions to see what features users are using
  the most and how they are trending.  You could use it for real-time
  analysis of visitor retention or funnels.
  
  .. _Mixpanel: http://www.mixpanel.com/
  
  
  .. mixpanel-installation:
  
  Installation
  ============
  
  You only need to do perform these steps if you are not using the
  generic :ttag:`analytical.*` tags.  If you are, skip to
  :ref:`mixpanel-configuration`.
  
  In order to use the template tag, you need to add
  :mod:`analytical.mixpanel` to the installed applications list in the
  project :file:`settings.py` file::
  
      INSTALLED_APPS = [
          ...
          'analytical.mixpanel',
          ...
      ]
  
  The Mixpanel Javascript code is inserted into templates using a
  template tag.  Load the :mod:`mixpanel` template tag library and
  insert the :ttag:`mixpanel` tag.  Because every page that you want
  to track must have the tag, it is useful to add it to your base
  template.  Insert the tag at the bottom of the HTML head::
  
      {% load mixpanel %}
      ...
      {% mixpanel %}
      </head>
      <body>
      ...
  
  
  .. _mixpanel-configuration:
  
  Configuration
  =============
  
  Before you can use the Mixpanel integration, you must first set your
  token.
  
  
  .. _mixpanel-api-key:
  
  Setting the token
  -----------------
  
  Every website you track events for with Mixpanel gets its own token,
  and the :ttag:`mixpanel` tag will include it in the rendered Javascript
  code.  You can find the project token on the Mixpanel *projects* page.
  Set :const:`MIXPANEL_TOKEN` in the project :file:`settings.py` file::
  
      MIXPANEL_TOKEN = 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
  
  If you do not set a token, the tracking code will not be rendered.
  
  
  .. _mixpanel-internal-ips:
  
  Internal IP addresses
  ---------------------
  
  Usually you do not want to track clicks from your development or
  internal IP addresses.  By default, if the tags detect that the client
  comes from any address in the :const:`INTERNAL_IPS` setting, the
  tracking code is commented out.  See :const:`ANALYTICAL_INTERNAL_IPS`
  for important information about detecting the visitor IP address.
  
  
  .. _mixpanel-identify-user:
  
  Identifying users
  -----------------
  
  If your websites identifies visitors, you can pass this information on
  to Mixpanel so that you can tie events to users.  By default, the
  username of an authenticated user is passed to Mixpanel automatically.
  See :data:`ANALYTICAL_AUTO_IDENTIFY` for important information about
  detecting authenticated visitors.
  
  You can also send the visitor identity yourself by adding the
  ``analytical_identity`` variable to the template context::
  
      context = RequestContext({'analytical_identity': identity})
      return some_template.render(context)
  
  If you can derive the identity from the HTTP request, you can also use
  a context processor that you add to the
  :data:`TEMPLATE_CONTEXT_PROCESSORS` list in :file:`settings.py`::
  
      def identify(request):
          try:
              return {'analytical_identity': request.user.email}
          except AttributeError:
              return {}
  
  Just remember that if you set the same context variable in the
  :class:`~django.template.context.RequestContext` constructor and in a
  context processor, the latter clobbers the former.
  """
  
  mixpanel_service = {
      'head_bottom': 'analytical.mixpanel.templatetags.mixpanel.MixpanelNode',
  }
  
subject: Fix Mixpanel docs typo