You can now copy this key and paste it into the appropriate field in the CartFlows settings to enable address autocomplete.
]]>Below are the cookies used by CartFlows:
cartflows_session_
wcf_active_checkout
wcf-visited-flow-
wcf-step-visited-
cartflows-ab-test-
If your server requires cookies to use a specific prefix (e.g., for caching compliance), you can define a custom prefix by adding the following line to your wp-config.php
file:
define( 'CARTFLOWS_COOKIE_PREFIX', 'your_prefix_' );
Note: Add this line just above the “That’s all, stop editing! Happy publishing.” line in the wp-config.php
file, located in your website’s root directory.
Language Name | Language Code | WordPress Locale Code |
Afrikaans | af | af |
Akan | ak | ak |
Albanian | sq | sq |
Amharic | am | am |
Arabic | ar | ar |
Armenian | hy | hy |
Aromanian | rup | rup_MK |
Assamese | as | as |
Azerbaijani | az | az |
Azerbaijani (Turkey) | az-tr | az_TR |
Bashkir | ba | ba |
Basque | eu | eu |
Belarusian | bel | bel |
Bengali | bn | bn_BD |
Bosnian | bs | bs_BA |
Bulgarian | bg | bg_BG |
Burmese | mya | my_MM |
Catalan | ca | ca |
Catalan (Balear) | bal | bal |
Chinese (China) | zh-cn | zh_CN |
Chinese (Hong Kong) | zh-hk | zh_HK |
Chinese (Taiwan) | zh-tw | zh_TW |
Corsican | co | co |
Croatian | hr | hr |
Czech | cs | cs_CZ |
Danish | da | da_DK |
Dhivehi | dv | dv |
Dutch | nl | nl_NL |
Dutch (Belgium) | nl-be | nl_BE |
English | en | en_US |
English (Australia) | en-au | en_AU |
English (Canada) | en-ca | en_CA |
English (UK) | en-gb | en_GB |
Esperanto | eo | eo |
Estonian | et | et |
Faroese | fo | fo |
Finnish | fi | fi |
French (Belgium) | fr-be | fr_BE |
French (France) | fr | fr_FR |
Frisian | fy | fy |
Fulah | fuc | fuc |
Galician | gl | gl_ES |
Georgian | ka | ka_GE |
German | de | de_DE |
German (Switzerland) | de-ch | de_CH |
Greek | el | el |
Guaraní | gn | gn |
Gujarati | gu | gu_IN |
Hawaiian | haw | haw_US |
Hazaragi | haz | haz |
Hebrew | he | he_IL |
Hindi | hi | hi_IN |
Hungarian | hu | hu_HU |
Icelandic | is | is_IS |
Ido | ido | ido |
Indonesian | id | id_ID |
Irish | ga | ga |
Italian | it | it_IT |
Japanese | ja | ja |
Javanese | jv | jv_ID |
Kannada | kn | kn |
Kazakh | kk | kk |
Khmer | km | km |
Kinyarwanda | kin | kin |
Kirghiz | ky | ky_KY |
Korean | ko | ko_KR |
Kurdish (Sorani) | ckb | ckb |
Lao | lo | lo |
Latvian | lv | lv |
Limburgish | li | li |
Lingala | lin | lin |
Lithuanian | lt | lt_LT |
Luxembourgish | lb | lb_LU |
Macedonian | mk | mk_MK |
Malagasy | mg | mg_MG |
Malay | ms | ms_MY |
Malayalam | ml | ml_IN |
Marathi | mr | mr |
Mingrelian | xmf | xmf |
Mongolian | mn | mn |
Montenegrin | me | me_ME |
Nepali | ne | ne_NP |
Norwegian (Bokmål) | nb | nb_NO |
Norwegian (Nynorsk) | nn | nn_NO |
Oriya | ory | ory |
Ossetic | os | os |
Pashto | ps | ps |
Persian | fa | fa_IR |
Persian (Afghanistan) | fa-af | fa_AF |
Polish | pl | pl_PL |
Portuguese (Brazil) | pt-br | pt_BR |
Portuguese (Portugal) | pt | pt_PT |
Punjabi | pa | pa_IN |
Rohingya | rhg | rhg |
Romanian | ro | ro_RO |
Russian | ru | ru_RU |
Russian (Ukraine) | ru-ua | ru_UA |
Rusyn | rue | rue |
Sakha | sah | sah |
Sanskrit | sa-in | sa_IN |
Sardinian | srd | srd |
Scottish Gaelic | gd | gd |
Serbian | sr | sr_RS |
Sindhi | sd | sd_PK |
Sinhala | si | si_LK |
Slovak | sk | sk_SK |
Slovenian | sl | sl_SI |
Somali | so | so_SO |
South Azerbaijani | azb | azb |
Spanish (Argentina) | es-ar | es_AR |
Spanish (Chile) | es-cl | es_CL |
Spanish (Colombia) | es-co | es_CO |
Spanish (Mexico) | es-mx | es_MX |
Spanish (Peru) | es-pe | es_PE |
Spanish (Puerto Rico) | es-pr | es_PR |
Spanish (Spain) | es | es_ES |
Spanish (Venezuela) | es-ve | es_VE |
Sundanese | su | su_ID |
Swahili | sw | sw |
Swedish | sv | sv_SE |
Swiss German | gsw | gsw |
Tagalog | tl | tl |
Tajik | tg | tg |
Tamazight (Central Atlas) | tzm | tzm |
Tamil | ta | ta_IN |
Tamil (Sri Lanka) | ta-lk | ta_LK |
Tatar | tt | tt_RU |
Telugu | te | te |
Thai | th | th |
Tibetan | bo | bo |
Tigrinya | tir | tir |
Turkish | tr | tr_TR |
Turkmen | tuk | tuk |
Uighur | ug | ug_CN |
Ukrainian | uk | uk |
Urdu | ur | ur |
Uzbek | uz | uz_UZ |
Vietnamese | vi | vi |
Walloon | wa | wa |
Welsh | cy | cy |
Yoruba | yor | yor |
For simplicity and safety, you can use a plugin that allows adding custom code without touching theme files. This works for JavaScript, CSS, and PHP.
We recommend:
These plugins let you manage your code snippets in a user-friendly way, and they remain active even after theme updates.
Use the Custom Script tab inside each funnel or step setting. The script will only apply to that specific funnel or step.
Go to Appearance > Customize > Additional CSS and paste your CSS code.
Add your PHP code inside the functions.php
file of your child theme.
Using a child theme ensures your custom code won’t be lost when updating the theme. If you’re not familiar with what a child theme is, refer to this article.
]]>Now, you can fully customize your upsell and downsell pages — show product info, update layouts, and craft compelling offers that match your design needs.
You can now add and display the following product details dynamically on your Upsell and Downsell pages:
These shortcodes ensure your customers know exactly what they’re buying and help boost conversions by presenting clear product information.
Note: These shortcodes only work on Upsell and Downsell pages within CartFlows. Using them on other pages (e.g., regular WordPress or WooCommerce pages) can result in errors or unexpected content display.
You can find these shortcodes by navigating to:
Upsell / Downsell Settings → Shortcodes section
Use this link to allow users to accept the offer. When clicked, the funnel moves to the next step with the offer accepted.
<a>
tag, or image.A link to decline the offer and continue to the next step in the funnel without accepting it.
<a>
tag, or image.[cartflows_offer_product_variation]
Displays variation options (dropdown style) for variable products.
[cartflows_offer_product_quantity]
Allows customers to select product quantity.
[cartflows_offer_product_title]
Shows the product title.
[cartflows_offer_product_desc]
Displays the full (long) description of the selected product.
[cartflows_offer_product_short_desc]
Displays the excerpt or short description of the selected product.
[cartflows_offer_product_price]
Shows the product price. If a discount is applied, the discounted price is shown.
[cartflows_offer_product_image]
Displays product images. For variable products, the image updates based on selected variation.
In this article, we will see the overview of the Personalization Shortcodes so that you can better utilize them on CartFlows pages –
We have provided these Personalization Shortcodes in the CartFlows so that you can personalize the display and the messages on the Upsell / Downsell or on the Thank You pages.
Personalization helps build trust with users by engaging with them during the checkout process. When you display the user’s name by personalizing the headline or message while they are completing their order, people are more likely to complete the order.
For example, you have placed an order from the checkout page of the CartFlows using the email [email protected] and now on the upsell & thank you page you want to display personalized messages such as “Hello [email protected], here is the 50% OFF on this product” OR “Thank you [email protected] for your order” Or any other as per your requirements.
These shortcodes will display the user’s email ID or the email or any other field that you have added in the shortcode for the current order.
Currently, we have two types of Personalization shortcodes available for use. They are divided into two sections and they are
Let’s see the personalization shortcodes type and how exactly it can be used –
This shortcode can be used on the upsell & downsell & thank you page to display the user’s billing information which is filled on the checkout fields on the checkout page of the CartFlows.
The proper format of the shortcode is as follows:
[cartflows_order_fields field="first_name" default="Dear"]
In the above shortcode, there are two parameters as
1. field: This represents, which field’s value you want to display on the page.
2. default: Default value to display if the checkout field is not filled.
You can use any field to display its value on the desired page.
For example:
– To display the user’s first name you can use
[cartflows_order_fields field="first_name" default="My Name"]
– To display the user’s last name you can use
[cartflows_order_fields field="last_name" default="My Surname"]
In the same way, you can use the rest of the fields.
This is the second shortcode which you can also use to display the user’s billing info on the upsell/downsell/thank you pages such as first name, last name, email, etc.
But, this shortcode will take the values of the parameters which are sent via URL. That is if there is first name of the user is sent from the URL as www.mydomain.com/thank-you/?first_name=myname&[email protected]
In this case, this shortcode will get the value of the first_name parameter and display it on the page where you have added this shortcode.
The proper format of this shortcode is as follows:
[cartflows_url_fields field="first_name" default="Dear"]
In the above shortcode, there are two parameters as
1. field: This represents, which field’s value you want to display on the page.
2. default: Default value to display if the checkout field is not filled.
You can use any field to display its value on the desired page.
For example:
– To display the user’s first name you can use
[cartflows_url_fields field="first_name" default="My Name"]
– To display the user’s last name you can use
[cartflows_url_fields field="last_name" default="My Surname"]
In the same way, you can use the rest of the fields.
Note: In WooCommerce all the field’s name starts with the “billing_” key for the billing fields and “shipping_” for shipping fields. Such as billing_first_name, billing_last_name, shipping_first_name, shipping_last_name. So, you have to add the field name without the “billing_” or “shipping_” prefix.
]]>