Your first useful check
Start here.
Open Marketing > Ads and inspect the connected account's status and tracking errors. Capture the exact error and affected campaign before rewriting source properties or tracking templates.
Is this the right guide?
Use this when contacts arrive but you cannot associate the expected ad interaction. This guide does not guarantee attribution for visitors whose consent or browser conditions prevent supported tracking.
What you can check and who can help.
- You can start here
- You can inspect account-health errors, compare landing URLs and review a contact's history if your permissions allow it.
- Bring in the responsible specialist
- Ask the ads or website owner to repair tracking settings, redirects or an external form connection. A redirect is the automatic move from one URL to another.
Tools and access you need
HubSpot Ads settings and contact history, ad destination URLs, website tracking configuration and approved access to the connected ad account.
Before changing settings, keep a copy of the current configuration so you can restore it. Use approved test records and remove customer details from shared evidence.
Follow the steps.
Start at step 1. Each result tells you what to check next; you do not need to change every setting mentioned.
Read the account's tracking error
Start yourself with Ads access.
- Look here
- In HubSpot, open Marketing > Ads and inspect the connected account's status and tracking errors. Use the platform's current help link below if the menu differs.
- Check this
- Note the exact error, affected campaign, connection permissions and auto-tracking setting.
- What it means
- Connecting an ad account does not guarantee that every ad can be tracked. One campaign can fail while others work.
- Next move
- Follow the named error's official resolution. Do not rewrite contact source values before finding the cause.
Follow the landing URL
You inspect URLs; the website owner repairs them.
- Look here
- Compare the ad's destination URL with the final landing URL after any redirects. Use an approved test URL rather than repeatedly clicking your own paid ads.
- Check this
- Do the source and campaign values remain in the URL? These tracking parameters are short labels such as utm_source. Check each move between pages or domains.
- What it means
- If required values disappear at a redirect, the destination may lose information needed to identify the interaction.
- Next move
- Ask the website owner to repair the specific redirect or URL setting. Do not invent a Google click ID; it would not represent a genuine ad interaction.
Check the supported tracking journey
Specialist check: website or integration owner.
- Look here
- Inspect the landing page, form and booking tool. Confirm the intended HubSpot tracking installation is present with the website owner.
- Check this
- Test the journey under a documented consent choice. Check whether the form or external scheduler associates the submission with the intended contact.
- What it means
- A form can create a CRM record without linking the visitor's earlier website activity. Consent and browser restrictions can also limit that link.
- Next move
- Repair a demonstrated installation or connection fault. Respect consent; do not bypass it to increase the attributed total.
Separate first discovery from the later visit
Start yourself with contact-history access.
- Look here
- Open the contact's history, source information and relevant ads report. Search existing contacts as well as newly created contacts.
- Check this
- Was the person first acquired through another channel? Is the later paid interaction recorded separately? If custom source fields exist, ask when they are updated.
- What it means
- Original source describes first discovery. A later paid visit does not automatically replace it. An unchanged original source is not proof that ads tracking failed.
- Next move
- Compare the field and report that answer your actual question. Preserve original information while investigating the latest interaction.
Repair only the demonstrated gap
Ads, CRM and website owners agree changes.
- Look here
- Return to the specific account error, disappearing URL value or failed form association you found.
- Check this
- Does the proposed change address that gap? Will it overwrite older contact information or interfere with another tool's tracking? A tracking template controls how the ad's tracking URL is built.
- What it means
- Deleting another tool's tracking or overwriting source history can create a new problem while masking the first one.
- Next move
- Agree the correction with the responsible owner and test fresh and returning contacts. Keep historical recovery separate from fixing future collection.
Keep the useful evidence.
Use this table as a reference while following the steps. Keep the information that identifies where the journey failed; remove names and email addresses before sharing it.
| Where to look | Capture | What it tells you |
|---|---|---|
| Ad account health | Connection, auto-tracking state, permissions and named errors | Follow the platform-specific error rather than treating every missing label as the same fault. |
| Destination chain | Ad destination and final URL after each redirect | Locate the exact redirect that strips required tracking values. |
| Contact timeline | Original acquisition information and subsequent interactions | A returning contact's original source may correctly remain unchanged. |
| Conversion integration | Form or booking result and contact association | A created CRM record is not proof that the website visit was associated with it. |
Platform behaviour and current access requirements: HubSpot: Troubleshoot ad tracking issues ↗ · HubSpot: Ad tracking ↗
See how the problem happens
Original source is not the most recent campaign
A prospect first discovers the company through organic search, then returns through an ad to request a demo. Seeing organic search as the original source does not establish an ad-tracking failure. Inspect the later interaction and the relevant ads report. If the paid interaction cannot be associated, investigate tracking health and the actual journey; do not rewrite original source to paid search merely because the demo followed an ad. This example explains source definitions, not a verified customer journey.
What did you find?
Use the observed behaviour to choose your next check.
HubSpot reports a tracking error
Follow the named error first; retain the affected campaign and test URL for validation.
Campaign parameters disappear before the landing page
Inspect the redirect or URL-cleaning layer responsible.
Original source differs from a recent paid visit
Review the contact history and report definition before treating the source as incorrect.
The tempting fix to avoid
Do not use a CRM source label as proof that every paid interaction is missing. Do not overwrite source history simply to reconcile one report.
Test success and the cases that should fail.
One successful test is not enough. Run the applicable cases below with approved test records. Write what happened beside the expected result, so a difference is visible before you release the change.
| Try this | This should happen |
|---|---|
| Fresh approved test contact | The supported, consented journey associates the visit and form with the intended contact. |
| Returning test contact | Original acquisition information is preserved while supported later interactions are recorded. |
| Redirected landing URL | Required parameters remain available at the final destination. |
| External booking flow | The booking arrives and the expected association works under the chosen integration. |
| Consent declined | The form remains functional and tracking respects the visitor's choice. |
Prove the fix
Tick a check only after you have tested it. Your ticks last while this page stays open; they are your own record of checks, not an automatic account test.
0 of 4 checks completed
When you can stop investigating.
Stop rewriting source fields when the original source is correct and the supported later ad interaction is recorded. If consent or browser restrictions limit the association, document that limitation rather than promising complete tracking.
Keep the problem from returning.
Document which fields represent original acquisition, the latest interaction and explicit campaign responses. Keep custom source fields separate from platform-managed fields unless you have a supported reason to update them. Test attribution whenever a landing page, redirect, tracking template or scheduling tool changes. If multiple tools require tracking templates, review compatibility rather than deleting existing tracking indiscriminately.
Questions that change the diagnosis.
Will switching on auto-tracking repair all old contacts?
Do not promise retroactive recovery. Verify the supported behaviour and retained evidence for the affected campaign. Correcting future collection and recovering historical associations are separate tasks.
Why is only one campaign affected?
Compare its destination, ad type, tracking settings and error state with a working campaign. A localized failure is a reason to investigate that route before rebuilding account-wide tracking.
When you need help
Give the ads or website owner the campaign reference, sequence of landing URLs, exact tracking error and contact-history times. Remove personal details and identifiers from shared URLs. Include browser and consent conditions so they can reproduce the gap.
Documentation to keep beside you
Official references checked on 12 October 2026. Menus, permissions and feature availability can change; confirm the details for your account.
Need another pair of eyes?
Show me the step that fails and what you have checked so far. We can trace where the record, event or workflow first goes off course.
Explore the relevant capability ↗ · Read the broader strategy ↗