You can now copy this key and paste it into the appropriate field in the CartFlows settings to enable address autocomplete.
]]>When a page request is made from one device via the browser, the same cookie is gets sent in the same page request too.
There are some cookies that are used by the CartFlows for the smooth working of some of the CartFlows features.
There is a total of 5 cookies used in the CartFlows and below are the names of those cookies:
For tracking the flow analytics in the CartFlows, there are certain cookies are used. These cookies are as follows:
If your server has specific requirements which require the cookie name should be started with the specific prefix then you can either exclude these cookies from the Server cache or use the following small piece of code to add the prefix to the cookie name.
define( 'CARTFLOWS_COOKIE_PREFIX', 'your_prefix_' );
Note: You need to add this code inside the wp-config.php file and just about the “That’s all, stop editing! Happy publishing” line/statement. This file is available in the root directory of the website/server.
]]>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 |
Note: We recommend to add the Custom PHP code or any JavaScript related code to the child theme’s functions.php file.
If you have a question about What is Child Theme and how to create it and where to add it. Then the following article will help you on How to Create a WordPress Child theme.
Next, in order to add any custom code to its proper location for proper working, you need to identify among the type of code that you have received.
How to Identify the Javascript code?
How to identify the CSS code?
How to identify the PHP code?
Below are the steps to add the various steps that will help you to add the below types of code on your website –
Let’s go though all of them with detailed steps:
There are two ways to add the Custom Javascript code on the CartFlows pages as mentioned below –
You can directly add the JS code in the head section of the page using the wp_head action but if you want to add your custom JS file then you need to use the wp_enqueue_script action. This action is used to register and add a new JS fine on the website.
Following are some more information on wp_head & wp_enqueue_script action hooks:
The CSS added from this section will be added globally on your website means it will add the CSS on all the pages of your website.
But If you want to add the custom PHP code without using any extra plugin then we suggest to add it by creating a child theme.
Once the Child Theme is created then it will have the functions.php file and where you have to add your custom PHP code.
All the themes of your website will be located at your_website’s_root_folder/wp-contents/themes/all_your_themes_folders directory. Now, you have to add the created child theme, in the themes directory of your website.
Note: It is recommended adding the Custom Code to the child theme’s functions.php file, in order to avoid any data loss while updating the Parent Theme.
]]>These Upsell & Downsell shortcodes will provide more control and help you to add/display information of Variation Product on the upsell & downsell pages. So that you can let users know which product they are buying and the price of it.
Also, giving you the flexibility to design the Upsell & Downsell pages as per your design requirements. That means you can now fully customize your upsell & downsell pages.
Now, with the help of these shortcodes, you can display –
You can still import the Upsell & Downsell ready-made templates and modify it as per your design needs and add from the below shortcodes to display the respective variation product’s information to suit your needs.
Note: These shortcodes will only work on the Upsell & Downsell pages of the CartFlows. If used anywhere else like on default pages of WordPress, WooCommerce or on other CartFlows pages then it may result in displaying error messages or some random text or something else can’t predict it.
You can locate these shortcodes on the Upsell / Downsell pages under the Offer Page Settings under Shortcodes section as shown below –
Below is the list of shortcodes and their detailed explanation on how to use on the Upsell & Downsell pages –
Shortcode: [cartflows_offer_product_variation]
Shortcode: [cartflows_offer_product_quantity]
Shortcode: [cartflows_offer_product_title]
Shortcode: [cartflows_offer_product_desc]
Shortcode: [cartflows_offer_product_short_desc]
Shortcode: [cartflows_offer_product_price]
Shortcode: [cartflows_offer_product_image]
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.
]]>