Configuring the extension
When the extension has been successfully installed, you can start configuring it.
Enabling the extension
In Magento admin, navigate to Stores > Configuration > Integrations” and select the "Voyado" tab.
Inside this configuration space, you can enable or disable the functionality supported by the extension.
Start by enabling the extension under “General” settings as seen in the video below.
Websites
You can now connect your Voyado Engage environment/s to all your websites.
In the top left corner, change the website under “Scope”. You can choose to have a default setup for all websites, connected to one Voyado Engage environment (recommended), or configure websites separately, connecting each one to a separate instance.
Establish your connection settings
Next, you'll need to input the credentials for your Engage environment.
Base URL: Input the Base URL of your Engage environment (For example: https://tenantid.staging.voyado.com).
API key: Input your Engage API key (for example: 00000000-0000-0000-0000-000000000000).
Source: Input the source of contact registration to use as a filter when triggering marketing automation acquisition journeys in Engage. (Example: ecom-eu).
StoreExternalId: Input the external ID of the Engage store that you want to connect your customers and orders to.
Configure the contact sync
This integration with Engage supports the sync of customers, guests and newsletter subscribers. These different types of customers are each stored in Voyado Engage as separate contact types.
Caution
All contact types must be created in Engage by the Voyado team before contact exports are enabled.
To allow syncing of the Customer entity in Magento you will have to:
Enable the customer export, found under Export > Enable customer export.
Go to the “Customer Specific Settings” section and enable “Create Voyado contact as member”.
If you want to sync your guest customers and store them in Engage, follow these steps:
Enable the customer export which can be found under Export > Enable customer export.
Go to the “Customer Specific Settings” section and enable Create Voyado contact also from Guest Customer.
If you want to store your newsletter subscriptions in Engage:
Enable the newsletter subscriber export under Export > Enable newsletter subscriber export.
Phone number validation
Voyado Engage requires a phone number to have a country calling code. If no validation for this is done in the front-end, and a phone number without a country calling code is input in checkout, the extension will validate that phone number based on the code of the country chosen in checkout.
For example:
A customer chooses country “Sweden” and gives the phone number “0701234567” in checkout.
The extension validates to check if the number is a valid Swedish number.
If it is, we add a country calling code and format the number to “+46701234567” before we send it to Engage.
If not, we just exclude the phone number from the request sent to Engage.
Enable Engage to update customers in Magento 2
In the configuration area you have the option of activating a two-way sync, allowing Engage tp update customers in Magento 2. The two-way sync is connected to the login event in Magento 2, meaning that data is fetched from Engage and used to update the customer whenever they login to their account.
You can sync any or all of the name and address data or the newsletter subscription flag from Engage.
Note
Two-way sync is only applicable if you have the “Require Email Confirmation” setting enabled in Magento 2. This can be found in Stores > Configuration > Customer Configuration.
Follow these steps to enable to two-way sync:
Enable the “Sync after login” setting which can be found under Customer specific settings > Sync after login.
Enable “Sync name and address” if you want Engage to update this information in Magento 2.
Enable “Sync newsletter subscription” if you want Engage to update this information in Magento 2 (recommended).
Contact data model
Here are the fields in the contact model:
Contact: |
First name |
Last name |
Street |
City |
Zip code |
Country code |
Gender |
Recruited in store (the store at which the contact signed up) |
Preferences: |
Accepts email marketing |
Note
The contact data model can be extended by developing a custom patch.
Configure syncing of purchases and returns
To sync purchases (called invoices in Magento) and returns (called credit memos in Magento) you must enable two separate exports. Activating these will allow you to create segments based on the contact's order history in Voyado Engage.
You can enable the invoice export at Export > Enable invoice export.
You can enable the credit memo export at Export > Enable credit memo export.
Warning
The order will only be stored for segmentation in Engage after it has been set to "invoiced" in Magento Admin.
{
"contact": {
"contactType": "member",
"matchKey": "f0352103-7143-4a44-a20d-af3300c58d7f",
"matchKeyType": "ContactId"
},
"createdDate": "2022-11-08T12:49:43+00:00",
"createdDateForXml": "2022-11-08T12:49:43+00:00",
"currency": "EUR",
"items": [
{
"articleName": "Joust Duffle Bag",
"articleNumber": "24-MB01",
"awardsBonus": true,
"extraData": [],
"grossPaidPrice": 85,
"quantity": 2,
"sku": "24-MB01",
"taxAmount": "17.0000",
"taxPercent": "25.0000",
"type": "PURCHASE"
}
],
"paymentMethods": [
{
"description": "Payment for: 000000034",
"type": "checkmo",
"value": 85
}
],
"receiptNumber": "000000034",
"storeExternalId": "opensource_demostore",
"taxDetails": {
"description": "TAX",
"percent": "25.0000",
"totalExcludingTax": 68,
"totalIncludingTax": 85,
"value": "19.5000"
},
"totalGrossPrice": 85,
"uniqueReceiptId": "000000034"
}{
"contact": {
"contactType": "member",
"matchKey": "f0352103-7143-4a44-a20d-af3300c58d7f",
"matchKeyType": "ContactId"
},
"createdDate": "2022-11-08T12:49:43+00:00",
"createdDateForXml": "2022-11-08T12:49:43+00:00",
"currency": "EUR",
"items": [
{
"articleName": "Joust Duffle Bag",
"articleNumber": "24-MB01",
"awardsBonus": true,
"extraData": [],
"grossPaidPrice": 42.5,
"quantity": -1,
"sku": "24-MB01",
"taxAmount": "8.5000",
"taxPercent": "25.0000",
"type": "RETURN"
}
],
"paymentMethods": [
{
"description": "Refund payment for: 000000034",
"type": "Refund",
"value": -42.5
}
],
"receiptNumber": "000000034",
"storeExternalId": "opensource_demostore",
"taxDetails": {
"description": "TAX",
"totalExcludingTax": 34,
"totalIncludingTax": 42.5,
"value": "8.5000"
},
"totalGrossPrice": -42.5,
"uniqueReceiptId": "34-20"
}Configure transactional emails
If you enable the order export in the configuration area, you can choose to trigger transacational communication via Engage which will streamline the graphic design of your emails, whether they are transactional or marketing emails.
Navigate to Export > Enable order export to activate the export.
The following order states are supported “out of the box” by the extension:
Order confirmation email
Order shipped email
Order cancelled email
Order returned email
Caution
If you want to trigger “Order returned email”, you must enable the credit memo export (see the previous section).
Each order status can be individually enable and disabled.
The ststuses in default Magento 2 implementation works like this:
Status “Pending” connects to an “Order confirmed” event.
Status “Processing” connects to an “Order shipped” event.
Status “Complete” connects to an "Order invoiced” event.
Status “Canceled” connects to an “Order canceled” event.
Credit memo connects to a “Order returned” event.
Note
Your Magento 2 implementation might trigger these events differently, which means the statuses above might not be relevant for your setup. For example, in some cases a confirmed order sets the initial order state to “Processing” instead of “Pending”, meaning you don’t have to activate the Pending state in the configuration area.
Order data model
Below are the "out of the box" data points included in transactional emails:
Contact: |
MatchKey (contactId) |
MatchKeyType (GUID) |
Order header: |
Currency |
Created date |
Freight fee |
Freight fee VAT |
Language |
Order number |
Order status |
Payment methods |
Shipping method |
Payment status |
Total discounts |
Total gross price |
Total VAT |
Total original price |
Total net price |
Total items price |
Total discounts |
Customer information |
First name |
Last name |
Middle name |
Phone |
Billing city |
Billing country |
Billing company |
Billing street |
Billing zip code |
Shipping first name |
Shipping last name |
Shipping middle name |
Shipping phone |
Shipping city |
Shipping company |
Shipping country |
Shipping street |
Shipping zip code |
Order items: |
Description |
Price |
Quantity |
SKU |
Image URL |
Image target URL |
VAT amount |
VAT percent |
Type (PURCHASE or RETURN) |
Note
If you want to extend the order payload with the additional product attributes in Magento, follow the instructions in the README.md file in Gitlab under the section "Extending". If you don't have access to the file on Gitlab, try this article [LINK TO "Installing the extension"].
Shipment settings
Add the Magento tracking URL at Shipment settings > Add the Magento tracking URL also shown in the admin.
Setting this to “Yes” will add the default tracking link provided by Magento 2 which is available in admin.
Setting this option to “No” will allow you to add your transporter's tracking URL. When the transactional email is sent, the first tracking number found will be added to the URL and sent in the payload.
Soft identification
When you send a newsletter or email with a link to your customers in Engage, the links are encrypted with a contact identifier (contactId). This functionality can be used for various actions, such as triggering abandoned carts or product views through Engage's tracking script, or to personalize the experience on-site since Engage knows who the visitor is.
To enable soft identification:
Navigate to Soft Login > Enable and select “Yes”.
Input your decryption key.
Note
The Decryption Key, 32 characters long, is configured in the Engage backoffice. Ask your Voyado team.
When the customer arrives on-site through a soft identification link, the extension decrypts it, identifying the customer. There are now two ways to proceed:
Automatically push the contact identifier to Google Tag Manager (dataLayer) by setting “Display on Frontend” to “Yes”.
Only expose the contact identifier and then use it server-side.
Caution
Soft identification only facilitates web-activity tracking and personalization on-site. It is not something that is supported out-of-the-box, since it is tightly coupled to front-end components.