Implementing the script

Can we implement the checkout script through a Flowbox plugin?

Yes, the Flowbox plugins include checkout script functionality.

Read more about the WordPress plugin

Can I include product titles in the checkout script?

No, the Flowbox Checkout script function takes the following parameters:

apiKey – Your Checkout Script API Key

products – An array of products. The products are represented as Javascript object with the properties:
- id (a string or number ). Must match the ID of the product in the Flowbox catalog.
- quantity (a number).
- price (a number).
- currency (a string, the 3 letter currency code)

E.g. { id: '001', quantity: 2, price: 44.95 currency: 'EUR' }

orderId – A number or string indicating the ID of the order.
locale – Requires the language-region code, in ISO format, of the site where your visitor has placed the order so the reminder email is sent in the same language.
customerData – An object containing the buyer's contact information for the reminder email

Can we receive the checkout script data in Google Analytics?

Unfortunately, Flowbox does not support a Google Analytics integration for the Checkout script yet, although we support it for Flow related metrics. However, there is a workaround: you can add UTM parameters in the product URL links (sent to us through the <link> attribute in your feed), and see the stats in Google this way.

Verifying & test orders

I've embedded the Checkout script, but my Insights has not been updated. Why is this?

There is a 24 hour delay between script implementation and the data being loaded in Flowbox Insights. Check back in 24 hours and the data should have been captured. If you are still experiencing issues, contact your CSM.

It’s been 24 hours, and we still can’t see any checkout data. What could be wrong?

We recommend going through the verify your checkout script article, to make sure your script is implemented correctly.

It’s also a good idea to carry out a test order, and ask your CSM to verify that it has gone through in the backend.

A proper test order should be carried out in these steps:

Go to your e-commerce site.
Click on one of Flowbox images (to open the Flow Gate).
Click on a product displayed in the Flow Gate, then you’ll get directed to the product page.
Add product to basket.
Finish order.
Inform your CSM about the test order (we need the time and date of the purchase).

I have correctly implemented the checkout script, why can’t I see any conversion rates showing up in my ‘commerce’ insights?

When opening your ‘commerce’ insights you should be able to see the metrics for your conversion rates. However, keep in mind that those conversions represent the total orders that resulted from an interaction with any Flow, it does not represent the total of orders checked out of your ecommerce. If you see a low conversion rate, it could be an indication that you need to work on the moderation of your Flows, tag more products, and make sure you have strategically placed Flows on your website. Check out the Flowbox Toolbox for inspiration on how to get the most out of your Flows.

Data collection

Does the Flowbox checkout script conform to GDPR? Can we implement it without informing our customers?

Yes. Since 25 May 2018, our platform is entirely compliant with GDPR requirements. As a client, you can trust that your customers’ data privacy is protected and that their data is handled and processed with high standards according to the GDPR. We have procedures for how to handle the data and have functions in the platform that make it possible to find all data that can be traced to a physical person.

What data do you collect from our customers in the checkout script cookies?

Detailed information on the processing we carry out on behalf of our clients is set out in the data processing agreements executed with our clients.

We process personal data made publicly available on social media by users who have interacted with your brand, and visitors of your website. Such data often includes:

Name
Username
Images
Captions
Transaction identifiers, device type, operating system, browser, location (area) and other technical data