Troubleshooting

Double-check your settings

  • Are your computer and mobile device connected to the same network?
  • Is your mobile device’s proxy enabled?
  • Do the proxy IP and port on your mobile device match what’s displayed on your computer?
  • Have you installed the SSL certificate?

Batching

Certain issues can arise with mobile app tracking that don’t apply (as much) to web tracking, e.g.:

  • users may be on slow or expensive connections where opening a new tracking connection for each tag increases overhead
  • a mobile device may not be connected to the internet at the time an action takes place

To work around these potential issues, some mobile analytics platforms (most notably Google Analytics) don’t send tags as soon as the tag is triggered, sending them instead as a batch. A batch collects tags that fired earlier in the session, or even in a previous session, and sends them all together in a single request rather than individually. Often this occurs at a regular interval-- for Google Analytics on mobile, the default interval is 2 minutes.

dataslayer mobile identifies batch requests and splits them out into individual tags for display purposes, but can’t change how frequently a batch request is sent on the app side.

Depending on the platform and analytics solution in place, you may be able to understand more about and change your batching settings; e.g. the Google Analytics for iOS documentation.

While minimizing batching may be helpful for testing and debugging, it’s recommended to leave batching in place for production builds.

Other issues

Please reach out to [email protected] for support on any issues that are not covered in the documentation.

Topics:

Troubleshooting

Double-check your settings

  • Are your computer and mobile device connected to the same network?
  • Is your mobile device’s proxy enabled?
  • Do the proxy IP and port on your mobile device match what’s displayed on your computer?
  • Have you installed the SSL certificate?

Batching

Certain issues can arise with mobile app tracking that don’t apply (as much) to web tracking, e.g.:

  • users may be on slow or expensive connections where opening a new tracking connection for each tag increases overhead
  • a mobile device may not be connected to the internet at the time an action takes place

To work around these potential issues, some mobile analytics platforms (most notably Google Analytics) don’t send tags as soon as the tag is triggered, sending them instead as a batch. A batch collects tags that fired earlier in the session, or even in a previous session, and sends them all together in a single request rather than individually. Often this occurs at a regular interval-- for Google Analytics on mobile, the default interval is 2 minutes.

dataslayer mobile identifies batch requests and splits them out into individual tags for display purposes, but can’t change how frequently a batch request is sent on the app side.

Depending on the platform and analytics solution in place, you may be able to understand more about and change your batching settings; e.g. the Google Analytics for iOS documentation.

While minimizing batching may be helpful for testing and debugging, it’s recommended to leave batching in place for production builds.

Other issues

Please reach out to [email protected] for support on any issues that are not covered in the documentation.