Fix the common gaps between installing and seeing data

1. 1

   Check the exact snippet

   Copy it again from the current project’s Integrations page. Confirm the project key and the app.clarvivo.com host are intact.
2. 2

   Check placement

   The script must load on the published page, usually through the shared document head or root layout.
3. 3

   Check the project boundary

   Confirm the domain, allowed hosts, and included/excluded paths match the page you visited.
4. 4

   Use the test event

   Send the Integrations test event and open Real-time. If it appears, Clarvivo can record the project and the remaining issue is the site installation or boundary.

Search Console data normally arrives with a reporting delay, and the first connection starts with a limited initial backfill. Confirm the selected Google property belongs to the same site, then allow time for Google’s reporting and the next Clarvivo sync before treating a recent day as final.

First confirm the signed webhook is arriving. Then confirm the checkout integration carries clv_vid from the customer’s browser through the provider metadata or custom data. Payments without campaign context remain Direct or unattributed by design.

Copy the exact project-specific URL again from Integrations, confirm the event is enabled in the provider dashboard, and paste that provider’s signing secret into Clarvivo. Send the provider’s test delivery, then inspect its delivery status before changing checkout code. The complete URL and event matrix is in Manual integrations.

Check that CLARVIVO_API_TOKEN is present in the client’s environment, that the token has the scope named by the error, and that the account has access to the relevant capability. Create a new scoped token if the original plaintext was not saved—it cannot be displayed again.