We recommend testing the Web SDK integration to ensure it's loading correctly and loading data attributes as expected.
Open a new window in your browser.
Open your browser developer tools panel. For most browsers, you can do this by right-clicking on your screen and clicking Inspect.
From the developer tools panel, go to the Network tab and type
placementsinto the filter bar.
Navigate to the site and page where the Web SDK has been placed.
Note: Make sure you have the developer tools open before navigating to your site to ensure the
/placementscall is recorded by the browser.
In the Network tab of the developer tools panel, you should see at least one
/placementsrequest. This indicates that the Web SDK loaded successfully.
/placementsrequest (it should have a status of 200). Check the Payload/Request tab to verify the data being shared with Rokt.
Note: During testing, you might see another
/placementscall with a 204 status. Make sure you are performing the check on the call with a 200 status.
The Rokt Web SDK provides contextual error reporting. If you are having trouble validating your integration, the best way to debug the issue is to check Console tab in the browser developer tools.
There may be other errors outside the Web SDK code. You may be experiencing one of the following common errors:
Make sure you are not missing any commas in your integration code.
To check for syntax errors:
Go to the browser developer tools Console tab.
If the file where you placed the Web SDK has an error, it appears in the console. Click the file to see the code and error from the browser.
Any error is indicated in the file. In particular, check that all attributes are separated by commas as shown below.
Other common errors
- Make sure the script has been placed on the correct page.
- If you’re using a tag manager, make sure the triggers are set up correctly so the script loads on the right page.