Fredrik JohanssonGoogle Ads Search
Menu+
Journey Inspector

Offline conversions readiness

Prove your join‑key capture, validate Ads diagnostics, and measure how much offline revenue is matchable today.

Need the full walkthrough? Read the offline conversions guide.

Best fit for lead‑gen teams using Smart Bidding and a CRM pipeline.

Tool input

Revenue Signal Baseline

Connect Google Ads to pull Offline Data Diagnostics and confirm matchable revenue signals.

Extension trace

No trace attached yet. Run a Journey Inspector trace first.

Connect Google Ads (read-only)

Diagnostics help confirm pending vs failed uploads.

Use the 10-digit ID where offline imports are uploaded (format 123-456-7890).

If imports run under an MCC, enter the manager ID here.

Diagnostics require a connected Google Ads account.

What you’ll get

Capture proof

  • Join‑key presence at lead creation
  • Consent timeline snapshot
  • “First break” step in the funnel

Ads diagnostics

  • Attempted vs processed vs failed
  • Pending vs failed by action
  • Diagnostics-backed next steps

How to use it

  1. Run the extension trace on a live journey.
  2. Connect Google Ads diagnostics.
  3. Review the baseline report.

What this does not do

  • It does not increase volume by itself.
  • It does not replace CRM discipline.
  • It does not guess missing data.

What to prepare

  • Google Ads customer ID.
  • Knowledge of the lead creation step.
  • Consent banner behavior (if any).

FAQ

Do I need OAuth?

Yes. This version requires a read-only Google Ads connection.

Is the report stored?

Not by default. Share links are optional and will store a minimal summary.

Can I run this without the extension?

Yes, but capture proof will be limited without a trace.

Do you store click IDs?

No. We only detect presence unless you explicitly opt in later.