GetResponse Integration

GetResponse gets the store customers without manual exports

An email service can write by scenario - abandoned cart, repeat purchase, welcome series - when it knows who your customers are and what they did. The add-on tells it on its own: storefront subscriptions, action tags, profile fields, orders and carts go to GetResponse on schedule.

Why the store needs a GetResponse link

A contact list filled from manual exports is stale by the end of the week: new customers are missing, nobody set the tags, and the abandoned-cart scenario has nothing to start from. The add-on removes the manual step - the service receives the data from the store itself.

Checkout: the "Customers" list checkbox is pre-checked - that is how the list is set up.

How a customer joins a list

• •  Checkout. The list is shown at the last step; the checkbox can be pre-checked or left empty, as your consent policy requires.
• •  Customer account. The customer manages subscriptions on the profile page; an unconfirmed subscription is shown as such.
• •  Newsletter form. An address from the standard CS-Cart form goes to the list marked for newsletters.
• •  Sync patterns. A rule like "every English-speaking customer goes to list X" queues the customers who registered before the add-on was installed.
• •  Manually. The administrator subscribes a customer from the customer card or adds a group of users and newsletter subscribers on the export screen.
• •  Any list language. A list in a language the store does not have is imported as well - its GetResponse language is shown in the table.

Customer account: three lists with checkboxes - subscriptions are visible and managed by the customer.

Contact lists imported from GetResponse: the language of the list, the id in the service, the storefront name and the status.

What travels with the contact

• •  Action tags: add to cart, wish list, comparison, call request, one-click purchase, subscription at checkout, "has orders", user type.
• •  Custom fields: four service fields (registration date, last login, order date and total) and any of yours - linked to a customer profile field.
• •  Contact name and e-mail, subscription confirmation, date.
• •  Tags and fields are edited by the administrator in the customer card - the changes leave with the next scheduled run.

The GetResponse tab in the customer card: list subscriptions and field values.

Action tags: the default set is created with one button both in the store and in GetResponse.

Ecommerce: products, orders and carts

With ecommerce enabled the add-on keeps the store in GetResponse: categories and products with price, image and link, orders with items and total, customer carts.

• •  Everything that changed in the store lands in the export queue and leaves on schedule - saving a product is never delayed.
• •  Manual export: "all" or "only new" for every object type, single objects through the picker.
• •  Abandoned carts of customers who are not subscribed to any list yet can go to a separate list.
• •  An order leaves with a billing status - PAID, PENDING or CANCELLED - by its status in the store: which statuses count as paid and as cancelled is set in the settings.
• •  Category, product and order pages carry a tab with the GetResponse id and the export date.

Customer carts that will go to GetResponse: items, total, date.

The export queue: what changed in the store and which action goes to the service.

The administration panel

• •  The "Marketing - GetResponse" section: contact lists, subscribers, export, export queue, sync patterns, waiting for sync, custom fields, tags.
• •  Subscribers of every list: name, e-mail, confirmation, link to the store account, removal from the list.
• •  The "waiting for sync" queue shows who goes to the service on the next run.
• •  Tags and fields are created from the panel straight in GetResponse; removal - in the store only or everywhere.

Subscribers of a list: who confirmed the address, who has a store account.

Sync patterns: user type, language and mailing list - to a contact list.

Settings and schedule

• •  API key and GetResponse store, the Web Connect code for on-site tracking.
• •  Three scheduled commands with ready cron lines: subscribers, ecommerce objects, patterns.
• •  The schedule key is generated at installation and stored in the add-on settings.
• •  Order statuses that reach GetResponse as paid and as cancelled.
• •  Administrator group privileges: viewing separately from managing.

Add-on settings: API key, GetResponse store, export queue and the Web Connect code.

The Orders section: which statuses reach GetResponse as PAID and as CANCELLED.

Marketplace and several storefronts

• •  CS-Cart Ultimate. API key, store and lists are separate per storefront; settings are set for all storefronts at once or one by one.
• •  Multi-Vendor. The add-on is managed by the marketplace administrator; vendors do not see it.
• •  Languages. Names of lists, tags and fields are translated into the store languages.

What's new in version 2.7

• •  Orders reach GetResponse with the billing status PAID, CANCELLED or PENDING by their order status; the paid and the cancelled statuses are chosen in the new "Orders" settings section.
• •  The order date, tax total and order page address travel with the order - scenarios like "N days after the purchase" count from the order date.
• •  The scheduled exchange is protected by a separate cron key: it is generated automatically at installation, stored in the add-on settings and can be updated any time on the CRON tab.
• •  Contact lists in a language the store does not have are imported under the default language; the list table shows the language of the list in GetResponse.
• •  The sync queue of a disabled or deleted list is cleared.
• •  CS-Cart Ultimate: exporting all customers to a list takes the customers of the current storefront only.

Frequently asked questions