Skip to main content

Troubleshooting

This page focuses on the most common reasons a technically valid setup still produces weak attribution.

Credentials save but integration behaves inconsistently​

Check that the encryption constant exists in wp-config.php before credentials were stored. If the key was added later or changed, saved secrets may no longer decrypt reliably.

UTMs appear on landing pages but not in final reporting​

This usually indicates a stop-point problem, not a capture problem.

Check:

  • whether the user path crossed the expected WordPress-to-Thinkific handoff
  • whether the checkout path changed
  • whether the test session used a clean browser state

Initial sync works but attribution coverage is low​

Sync confirms connectivity. It does not confirm attribution continuity.

Run a controlled UTM test and verify the full path from first landing to final outcome.

Demo or debug tooling is confusing the result​

If demo mode, trace tools, or debug utilities are enabled, verify that you understand which data set you are viewing before drawing conclusions from reports.

Support checklist​

Before escalating an issue, collect:

  • the exact landing URL used for testing
  • the UTM values you expected
  • the WordPress page where the visit started
  • the Thinkific outcome you expected to match
  • screenshots or logs from any trace or debug view available in your build