Skip to main content
All CollectionsUGC - Developer GuidesGeneric Javascript integrationCheckout Script
Verify the Checkout script
Verify the Checkout script

Are you not receiving any sales numbers Analytics? Go through these steps to make sure that the Checkout script is correctly implemented.

Updated over 6 months ago

1. Check for errors when running the script on-site

  1. Perform a test purchase or execute the script in your testing environment. Keep your browser console open and check for possible errors coming from bzfy-checkout.js:1 

  2. If you get an error message, its content should be enough to find out what might be causing it. Here is an example of what it could look like:

2. Verify request payload data

Perform a test purchase and verify that you have made the POST request with response code 200.

  1. In your browser inspector, go to the Network tab. Keep this tab open.

  2. Finish a test purchase.

  3. Check that the "bzfy-checkout.js" request has been processed in the Network tab

  4. Check that an "events" request has been processed in the Network tab. In case you don't find it you can also use the filter functionality to search for anything related to "Getflowbox" or "Flowbox". Validate request method and status code.

  5. Open the "events" request's Payload data and check that its "data > action" parameter is equal to "checkout" in order to ensure that it matches the Checkout script. If not, it could have been generated by a different Flowbox event (such as "embed_viewed").

  6. Open the Payload's "data" element and check that the data under "items" matches each of the products that have been purchased. Take screenshot to display this information.

Verify that the Payload contains the following:

  1. apiKey - Your Checkout Script API Key.

  2. products - An array of products. Each product is represented as Javascript object with the following properties:
    - id (string or number)
    - quantity (number)
    - price (number)
    - currency (string)
    For example: { id: 1, quantity: 5, price: 49.95, currency: 'EUR' }

  3. orderId - A number indicating the ID of the order.

3. Verify product ID

Perform a test purchase and verify that the product ID passed to the script matches the product ID used to identify the product in Flowbox.

Your shopping feed should've been imported to a Catalog in your Flowbox account by now. In the feed, there usually are a few different ID-attributes used to identify products, out of which one needs to be selected when importing the shopping feed.

The Checkout script needs to be configured with the same product identifier as is used to identify the products in your Catalog. To check what ID is being used follow these steps:

  1. Go to the "Visual Marketing" tab in Flowbox.

  2. Click on "Products" (under "Commerce") in the menu to access the product list.

  3. Search for the product, either by its name or its ID.

  4. Validate that the ID is the same as the one in the Checkout script.

  5. If the product id that is being retrieved in the Checkout script doesn't match the product data you have available in your Flowbox Catalog, you'll need to edit your Checkout script so they match.
    ​

4. Content Security Policy (CSP) Error

Content Security Policy (CSP) is a W3C standard providing a layer of protection against Cross-Site Scripting (XSS). CSP policy allows blocking/allowing content from specified domains and avoiding the content coming from unapproved origin.

If you see an error message that states that the checkout script could not load due to Content Security Policy, you will need to add Flowbox to your CDN whitelist.

If after following these guidelines it's not possible to get the Checkout script working, please contact Flowbox Tech Support providing screenshots (console errors, etc.) and feedback on the issue.

Did this answer your question?