BDOW! can use discount codes that have been generated in your WooCommerce store, so you can easily distribute offers to new subscribers. While a store integration is not required to run a Discount Code campaign, it does make it simpler because the codes will automatically be synchronized. Plus, you gain access to insightful analytics through shared usage data!
Connecting BDOW! to WooCommerce
The first thing to do is connect BDOW! to your WooCommerce store. In your site manager, go to Monetize > Discounts. Next, hover over Connect and select WooCommerce from the dropdown.
Now just enter the name of your WooCommerce store and click Integrate. You will authenticate with your store to establish the connection.
Note that you should log into the store with your store owner's credentials. Signing in with another user will not grant sufficient permissions.
WARNING
If you manually disconnect the WooCommerce integration from BDOW!:
Any discount campaigns you create in BDOW! will be lost (along with their stats)
Any Forms you created with Discount Codes will no longer offer codes. If you reconnect WooCommerce, you will need to re-assign a discount campaign to these Forms.
Creating a Discount Campaign
Now that the integration is established and your codes will be synchronized, the next step is creating a Discount Campaign. A Discount Campaign determines how BDOW! issues offers to new subscribers.
Campaign management on the BDOW! side is pretty much the same regardless of your store platform. See Creating a Discount Code Campaign for the full walkthrough.
Troubleshooting integrations with WooCommerce
If a problem arises with the connection to WooCommerce, BDOW! will display an error message on the Discounts page. See the list below for a guide on how to navigate our most common error codes:
401 (Unauthorized). When prompted with this error, it is likely that BDOW! was disconnected manually on WooCommerce's end. Another possibility is the user that connected to WooCommerce within BDOW! doesn't have access to Coupons or Webhooks on the WooCommerce side. Make sure to connect with the store owner's credentials.
403 (Forbidden). In the event that you see a 403 error, it is likely that WordPress has been setup incorrectly. Some tips on how to resolve this issue can be found here: https://www.elegantthemes.com/blog/wordpress/fix-the-403-forbidden-error.
This error message could also be displayed when a user without access to the site is trying to create Webhooks or Discount Codes. Make sure to connect with the store owner's credentials.404 (Not Found). If you see this error, it is likely that the wrong URL was used to connect to WooCommerce, or the site no longer exists.
520 (Unknown Error). The 520 error is a catch-all response for when the server returns something unexpected. In the event you see this error after waiting a minute and refreshing the page, please write in to our awesome support team. They would be happy to look into this further for you.
301 (Moved Permanently).This error is generally displayed when BDOW! is using the incorrect protocol when attempting to connect to WooCommerce (http vs https). If you see this message, contact our support team and they will investigate.
Some general notes about our WooCommerce integration
If the error message returned from WooCommerce contains "Consumer key is invalid" (401) then the connection to WooCommerce from BDOW! is broken, and you will need to re-connect with WooCommerce.
In the event that BDOW! is disconnected due to an error and you are prompted to connect, Discount campaigns will not be deleted. Discount Code campaigns are only deleted when BDOW! is manually disconnected and reconnected.
Generally, if you are receiving an error besides a 401 error, Discount Code functionality will continue to work properly. It is also possible that multiple 520 errors could indicate a larger issue, such as the site crashing, which would prevent Discount Codes from being created. When you see an error, we recommend refreshing the page to see if the error message is temporary. If the error persists after refreshing, write in to our support team.