engineer-locations

Configure Braze location tracking and geofence registration for iOS and Android.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-locations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineer-locations
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/engineer-locations
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill engineer-locations

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Engineers integrating Braze face fragmented guidance across SDK flags, OS permission models, and platform geofence limits, which leads to missing location data or non-firing geofence campaigns. This Skill consolidates the technical steps and troubleshooting checks needed to reliably collect location data and register geofences so campaigns trigger as expected.

Core Features & Use Cases

  • SDK Initialization & Flags: Details which SDK switches and configuration entries enable location collection on iOS, Android, and web.
  • Permission Management: Explains foreground vs background permission requirements, precise location considerations, and how to build a permission primer to increase opt-in.
  • Geofence Registration & Limits: Covers defining geofence coordinates and radius, OS monitoring limits, Braze rotation strategies, and cooldown considerations for real-time triggers.
  • Troubleshooting: Common failure modes and checks for missing location data, non-registered geofences, and platform-specific quirks.

Quick Start

Configure SDK location collection and background permissions, register geofence zones with latitude/longitude and radius, and validate entry/exit events on iOS and Android.

Frequently Asked Questions about engineer-locations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable location tracking and geofence triggers in Braze for iOS and Android?

To enable Braze geofences, configure SDK location collection flags during initialization, request background location permissions, and register geofence coordinates with radius to trigger real-time campaigns on iOS and Android.

What is the difference between foreground and background location permissions for mobile geofencing?

Foreground permissions allow basic location collection during active app use, while background location permissions and precise location considerations are required for monitoring geofence entry and exit events when the app is closed.

How do I fix Braze geofence campaigns not firing on mobile devices?

Troubleshoot non-firing Braze geofence campaigns by verifying SDK location flags, checking OS geofence monitoring limits, confirming background execution entitlements, and validating that geofence coordinates and radius are registered correctly.

Are there OS geofence limits I need to consider when configuring Braze location campaigns?

Yes, iOS and Android enforce platform-specific geofence monitoring limits, so Braze uses rotation strategies and cooldown considerations to manage registered geofence zones and ensure reliable real-time trigger execution.

Do I need a permission primer to increase location opt-in rates for mobile apps?

Building a permission primer before requesting foreground or background location permissions helps explain precise location requirements to users, which increases the opt-in rate for Braze location tracking and geofencing.