Each destination pairs a linked Google Ads account with a specific conversion action.

Create named routes and assign one or more destinations to each route. A converted call can be delivered independently to every destination selected by its route.

Choose one active fallback destination for calls that do not match a named route. If no active fallback is configured, uploads pause rather than being sent to an ambiguous account or action.

Routes can be selected by assigning a snippet or by using the route’s copyable moja_ga_route URL parameter. An unknown or disabled route key fails closed and does not silently fall back.

Routing is frozen when the conversion becomes eligible. Later destination or route edits apply to future conversions and do not retarget already queued deliveries.

Delivery health shows results by route and destination, including delivered, validated, failed, pending, retrying, and unroutable totals plus the latest provider error when available.

Open Integrations → Google Ads, select an installed integration, and find Destination routing above the available conversion actions.

Add or activate a destination by selecting the linked account and conversion action. Moja validates the pairing before it can be used.

Mark one active destination as the fallback. Linking an account or discovering an action alone does not send conversions there.

Create a named route, select one or more active destinations, and optionally assign a snippet.

For URL-based routing, copy the generated moja_ga_route parameter and add it to the appropriate landing-page or ad URL. Calls without a valid explicit route use the configured fallback.

Use delivery health to review destination-level outcomes and identify paused, unroutable, or failed uploads.

Teams can intentionally send different call conversions to different Google Ads accounts and conversion actions—or fan one conversion out to several selected destinations—without relying on an ambiguous default.

Independent delivery state prevents a failed destination from causing a successful destination to be resent.

Validation and fail-closed routing reduce wrong-account uploads while making configuration and provider failures visible.