Vendre is a complete e-commerce platform that includes all the components you need to run e-commerce, whether you sell B2C, B2B or your own brand.
With the integration between Rule and Vendre, you can automatically sync and send events that occur in your webshop directly to your account in Rule, to easily reach customers via email and SMS.
Process your customers directly after they have made a purchase in your shop using automations in Rule based on purchase behavior data from your store. This way, your communication will be more accurate and personalized.
We will go through:
About the integration
Installation
Usage
Import historical orders, one retrieval at a time
Data fields sent to Rule
About the integration
This integration uses Vendre webhook triggers to send customer and order data to Rule when certain events occur on the Vendre platform.
Additional information about Vendre's webhooks and API can be found here.
Installation
In the Vendre admin panel, navigate to the 'Apps & Integration' section in the navigation window and click on 'Webhooks'
Create an API key inside your Rule account, go to 'Settings' > 'Developer' > Create a new API key > Name the API key > Copy the API key
The webhook URL should be combined with the API key shown below (alternatively, you can enter your API key in the text box below to automatically combine the webhook URL).
Enter Rule API Key:
https://ix.rule.io/vendre?apikey=APIKEYHERE
On Vendre's webhook page, paste the webhook URL (combined with the API key) into the URL field for the webhook you want to activate. It is recommended to activate all available webhooks to have the most complete set of data available on Rule.
To test webhooks, trigger events from the webshop for the webhooks that have been added (such as creating a new order, creating a new customer, or updating a customer's information). Once a webhook has been triggered, you can see the webhook logs at the bottom of the webhooks page on Vendre to confirm that data was sent to Rule.
The integration is now complete and you will be able to see customer events inside the Rule platform because the connection allows Vendre to send that data to Rule as soon as an event occurs.
Once you have finished your settings, make a test call to Rule for all your flows, then you will be able to see in your Rule account what data you are receiving and to which tag.
Usage
Webhook event in Vendre | Tag in Rule | Data sent to Rule | Description |
Customer Added | Vendre, Newsletter* | Subscriber Data |
|
Customer Updated | Vendre, Newsletter* | Subscriber Data |
|
Customer Deleted | - | - |
|
Cart Updated | CartInProgress | Subscriber & Cart Data |
|
Order Completed | OrderCompleted | Order Data |
|
The newsletter tag is used when the customer checks the box "subscribe to newsletter" at checkout
All events are triggered from the storefront. Updating or adding customers from the admin panel will not trigger webhook events
Import historical orders, one retrieval at a time
If there are orders and subscribers in Vendre that are missing in Rule, we recommend retrieving them, so you can start segmenting your subscribers from day 1. All Rule needs is an API key from Vendre and the address to the e-commerce site.
Then send these to support@rule.se. See example below
Vendre API key (example): 4wGpn-UB9lPLjygjGw9E7F4Bz-GyC-ElTz6N
You can find the API key under Settings > Administrators, then select any administrator (or create a new one for this purpose). The API key is listed as Secret key.
Please also note that only one retrieval occurs at a time.
If you are unsure where to find this information, contact Vendre.
Data fields sent to Rule
Subscriber Fields
Subscriber.Source (Vendre)
Subscriber.AddressCity
Subscriber.AddressCountryId
Subscriber.AddressPostcode
Subscriber.Street
Subscriber.Street2
Subscriber.Company
Subscriber.MarketID
Subscriber.Gender
Subscriber.NameAlias
Subscriber.NameFirst
Subscriber.NameLast
Subscriber.Birthday
Subscriber.GroupId
Subscriber.DateAdded
Subscriber.DateModified
Cart Fields
Cart.Products (JSON - see below)
Cart.Names
Cart.Models
Cart.Manufacturers
Cart.ProductTags
The field Cart.Products contains a JSON-formatted array with information about the product/products in an order:
id_string
id
image_id
image_path
quantity
model
name
price
final_price
tax
tax_class_id
weight
package_content
unit
external_id
category_name
manufacturer_name
tag_names
Order Fields
Order.ID
Order.BillingName
Order.BillingCompany
Order.BillingStreetAddress
Order.BillingStreetAddress2
Order.BillingCity
Order.BillingPostcode
Order.BillingCountryId
Order.Currency
Order.ShippingName
Order.ShippingCompany
Order.ShippingStreetAddress
Order.ShippingStreetAddress2
Order.ShippingCity
Order.ShippingPostCode
Order.ShippingCountryId
Order.VatDisp
Order.Date
Order.Names
Order.Models
Order.Manufacturers
Order.Products (JSON - see below)
Order.Total
Order.Totals (JSON - see below)
Order.ProductTagsSwedish
Order.ProductTagsEnglish
Order.ProductCategoriesSwedish
Order.ProductCategoriesEnglish
The field Orders.Products contains a JSON-formatted array with information about the product/products in an order:
id
image_id
external_id
quantity
model
name
price
final_price
tax
tax_class_id
weight
attributes
package_content
unit
manufacturer_name
The field Order.Totals contains a JSON-formatted array with the total cost of an order:
title
text
value
tax
class