Troubleshooting

Start with Saúde do rastreamento (Tracking Health) on the account page. It monitors CRM freshness, actionable configuration blocks, and permanent Google or Meta rejections. Envios e qualidade (Delivery & Quality) is for aggregate metrics, not for diagnosing one event. See also Monitoring and Tracking Health.

Nothing appears in Recent Events

Likely cause What to do
The CRM did not call the URL In Passo 1 — CRM (Step 1 — CRM), click Gerenciar CRM → Tentativas de webhook recentes (Manage CRM → Recent webhook attempts). With no attempts, review the CRM webhook and the URL/token.
No platform is connected or configured Connect Google Ads or Meta Ads in Passo 2 — Conectar Google Ads e Meta Ads (Step 2 — Connect Google Ads and Meta Ads). See Connecting Google Ads and Connecting Meta Ads.
The Journey skipped the stage for safety Check the stage, deal_id, platform destination, and email/phone or click ID. See below.
The row shows A autorização precisa ser renovada. (Authorization needs to be renewed) Click Reconectar (Reconnect) in Step 2 (Google or Meta). For Google, pick the account again in Conta encontrada (Account found).

Journey: skipped stage

The Journey prefers not sending to sending the wrong milestone. It skips the stage when one of these happens:

  • the stage could not be resolved, is not configured, is inactive, or is set to Não enviar (Do not send);
  • deal_id is missing;
  • the stage has no destination: Conversão (Conversion, Google Ads), Evento (Event, Meta Ads), or both;
  • no identity is available for the platform to match, such as email, phone, or click ID.

Open Saúde do rastreamento for the available diagnosis and review Passo 3 — Jornada (Step 3 — Journey). For a manual webhook, expand an event's Dados recebidos (Received data) and confirm the mapped paths in Field Mapping.

A skipped stage does not become a plain conversion and does not get an average value instead. Fix the cause before the next milestone is sent.

An empty value sent is not a Journey error. By default, the Journey sends no value. There is a value only with Valor fixo (Fixed value) on the event, or with Enviar valor da venda (Send sale value) on the Venda realizada (Sale won) card, when the CRM provides positive revenue.

Automatic retry or permanent delivery failure

In the Journey, a temporary failure, such as a timeout, instability, or a temporary platform limit, is retried automatically. While it is retrying, it does not appear in Tracking Health as a customer incident.

A permanent failure is a Google or Meta rejection that will not change by waiting, such as an invalid Google action, a permission problem, or rejected data. It shows as a delivery failure and can create a Tracking Health diagnosis. Internal TC failures, opaque platform failures, and receipt percentages alone are not shown there as customer incidents.

Google Ads delivery failure

Check in this order:

  1. In Google Ads, enable Enhanced conversions for leads and accept the data terms.
  2. Confirm the account on the Google Ads row in Step 2. To change it: Trocar (Change), then pick the right account in Conta encontrada.
  3. Confirm the conversion action is exclusive to True Conversions and is not also fired by a tag/GTM or another integration.
  4. Check the Conversão of each event in the Google Ads block: any event accepts Secondary or Primary (Primary for bidding). An event sent only to Meta Ads does not need a Google conversion.
  5. Check email/phone and, when available, gclid in Field Mapping.

If Google reports that the conversion already exists, you normally do not need to act: the same milestone is not sent twice.

Meta Ads does not connect or send

  • In Step 2, on the Meta Ads row, click Conectar (Connect) or Reconectar (Reconnect) and approve the business, ad account, and pixel.
  • The row should show Pixel …. If there are several, pick one in Conjunto de dados (Pixel) (Dataset, Pixel).
  • In the Journey, confirm the Evento in the event's Meta Ads block. For click-to-WhatsApp leads, also confirm the Evento de WhatsApp (WhatsApp event) when that field is available.

Details: Connecting Meta Ads.

RD Station CRM does not connect or shows "Expirada" (Expired)

  • "Esta conta do RD Station CRM não tem API." (This RD Station CRM account has no API.): the account is on the Free plan. Use the RD Station CRM Basic plan or higher.
  • "A autorização foi negada." (Authorization was denied.) or "Falha ao conectar o RD Station CRM." (Failed to connect RD Station CRM.): click Conectar RD Station CRM in Step 1 and authorize again on the RD Station screen.
  • Expirada (Expired): RD did not renew the access. Click Reconectar (Reconnect) in Step 1 and authorize again.
  • Connected earlier with a token: Reconectar uses the saved token. If the token was changed in RD, disconnect and connect again.

Details: Connecting RD Station CRM.

The same deal appears twice (RD Station)

This can happen when RD Station Marketing and RD Station CRM are both connected for the same funnel. Choose one source of truth for the funnel and disable or ignore the matching stages in the other. For the full funnel, use RD Station CRM or a manual webhook: Connecting RD Station CRM.