Nordisk E-handel Integration
The partnership between Rule and Nordisk E-handel enables connected e-retailers, through this integration, to utilize Rule's services. Rule can be seen as a completely separate sales channel, just like social media or Google. The information needed about the customer to stay relevant can be brought into Rule to create campaigns and automations.
We will go through:
1. Installation
2. Usage
3. Data fields sent to Rule
Installation
Nordisk E-handel manages the integration process.
Contact your account manager at Nordisk E-handel, and they will assist you through the process.
Once your settings are ready, perform a test call to Rule for all your flows. After that, you will be able to see which data is received in your Rule account and under which tag it is placed.
Usage
Nordic E-commerce Events
| Event Trigger | Description | Tag in Rule | Data sent to Rule |
| Customer Updated | When a customer updates their information, UPDATE_CUSTOMER is sent along with the fields described in the Customer Fields section. | UPDATE_CUSTOMER | Subscriber & Order Data |
| Cart Updated | When the contents of the shopping cart are changed, the tag CartInProgress is sent along with the fields described in the Cart Updated section. Since the shopping cart can be updated in NEH without any changes made to its contents, there is some logic to prevent spam with unnecessary updates. | CartInProgress | Subscriber & Order Data |
| Order Completed | When an order is created, the tag OrderCompleted is sent along with the fields described in the Order Completed section. The tag CartInProgress is removed. | OrderCompleted | Subscriber & Order Data |
Data fields sent to Rule
Customer Updated
Subscriber.Source Subscriber.Firstname Subscriber.Lastname Subscriber.Number Subscriber.Street Subscriber.Street2 Subscriber.City Subscriber.Zipcode Subscriber.Country Subscriber.CountryCode Subscriber.Language Subscriber.LanguageCode Subscriber.State Subscriber.Tele Subscriber.Cell Subscriber.Fax Subscriber.Company Subscriber.OrgNo Subscriber.VATNumber Subscriber.CustomerType Subscriber.WantNewsletter Subscriber.Currency Subscriber.Login Subscriber.OneTimeCustomer Subscriber.ctext<n> Subscriber.cselect<n> Subscriber.CustomerCategory Subscriber.cctext<n> Subscriber.ccselect<n> // CustomerCategory, cctest<n> and ccselect<n> can occur multiple times
Cart Updated
Subscriber.Source Subscriber.Firstname Subscriber.Lastname Subscriber.Number Subscriber.Street Subscriber.Street2 Subscriber.City Subscriber.Zipcode Subscriber.Country Subscriber.CountryCode Subscriber.Language Subscriber.LanguageCode Subscriber.State Subscriber.Tele Subscriber.Cell Subscriber.Fax Subscriber.Company Subscriber.OrgNo Subscriber.VATNumber Subscriber.CustomerType Subscriber.WantNewsletter Subscriber.Currency Subscriber.Login Subscriber.OneTimeCustomer Subscriber.ctext<n> Subscriber.cselect<n> Subscriber.CustomerCategory Subscriber.cctext<n> Subscriber.ccselect<n> Order.Total Order.TotalValue Order.Vat Order.ShippingMethod Order.PaymentMethod Order.PaymentMethodMethod (always empty) Order.PaymentMethodType (always empty) Order.ShippingCost Order.ShippingVat Order.PaymentCost Order.PaymentVat Order.Products (see below) Order.Variations Order.Collections Order.Brands Order.Skus Order.otext<n> Order.oselect<n> Order.AbandonedCartLink // CustomerCategory, cctest<n> and ccselect<n> can occur multiple times
Order Completed
Subscriber.Source Subscriber.Firstname Subscriber.Lastname Subscriber.Number Subscriber.Street Subscriber.Street2 Subscriber.City Subscriber.Zipcode Subscriber.Country Subscriber.CountryCode Subscriber.Language Subscriber.LanguageCode Subscriber.State Subscriber.Tele Subscriber.Cell Subscriber.Fax Subscriber.Company Subscriber.OrgNo Subscriber.VATNumber Subscriber.CustomerType Subscriber.WantNewsletter Subscriber.Currency Subscriber.Login Subscriber.OneTimeCustomer Subscriber.ctext<n> Subscriber.cselect<n> Subscriber.CustomerCategory Subscriber.cctext<n> Subscriber.ccselect<n> Order.AbandonedCartLink (always empty) Order.Total Order.Vat Order.TotalValue Order.ShippingMethod Order.PaymentMethod Order.PaymentMethodMethod Order.PaymentMethodType Order.ShippingCost Order.ShippingVat Order.PaymentCost Order.PaymentVat Order.Firstname Order.Lastname Order.Company Order.Street Order.Street2 Order.Zipcode Order.City Order.Country Order.BillingFirstname Order.BillingLastname Order.BillingCompany Order.BillingStreet Order.BillingStreet2 Order.BillingZipcode Order.BillingCity Order.BillingState Order.BillingCountry Order.BillingTele Order.Products (see below) Order.Variations Order.Collections Order.Brands Order.Skus Order.otext<n> Order.oselect<n> Order.Number Order.Date
Order Products
Order.Products is a JSON-sträng from an array of objects with the following fields
brand
category
name
vname
sku
image
price
tax
qty
subtotal
Text<n>
select<n>
vtext<n>
vselect<n>
gtext<n>
gselect<n>
btext<n>
bselect<n>
inputfields
attributes
Note
Fields ending with <n> are fields that have a numeric identifier in their name. The number of fields varies from store to store as they are usually only activated from store-specific developments. Only active fields are sent, and all numeric identifiers start at 1.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article
