Skip to content
Get Bricks

Map Connector

The Map Connector works with the Google Map element when Sync with query is enabled. Place one Map Connector inside each item of the query loop that should produce a marker.

It renders an invisible <template> node that stores latitude, longitude, and/or address plus optional Info Box popup template data and per-item marker overrides. The Map reads these nodes to build markers when the query updates (pagination, filters, load more, etc.).

See Map → Sync with query for the full workflow.

  • Latitude (text) — Use dynamic data from the looped post (placeholder shows Berlin-area example).

  • Longitude (text).

  • Address (text) — Alternative to coordinates; may geocode via Google when coordinates are not set.

An error info appears when all three are empty—Bricks expects at least one source of location via dynamic tags.

  • Info Box: Template (Popup) (select) — Popup template with Template Settings → Popup → Info Box (Map) enabled.

  • Info — Reminds you to enable the Info Box option on the popup template.

An info control notes that Marker: Type (text vs image) is configured on the Map element, while fields here override that map’s defaults for this loop item.

On the connector, Bricks only exposes marker fields that are not flagged mainOnly in the shared map-marker control set—so you set per-loop values, not the global marker typography or image dimensions (those stay on the Map element):

  • Label (text) — Screen reader label (aria-label) for the marker.

  • Marker: TextText field for the default text marker.

  • Marker: Text (Active)Text field for the active text marker.

  • Marker: ImageIcon (image) for the default image marker.

  • Marker: Image (Active)Icon (image) for the active image marker.