Top
integrated part of core system

Service: Sync internal newsletter subscription information

applies to: xtcommerce forks

IMPORTANT: read this documentation before activating the module

Why

The latest release of modified-shop and Gambio contain some basic changes how newsletter subscription information is handled.

before:

Table "customers" contains a field "customers_newsletter" (0 or 1) holding the newsletter subscription status. This status can be edited in the customer admin interface.

MailBeez utilises this status for:

  • basic check for newsletter subscription (you can configure MailBeez for doing this)
  • Newsletter Advanced Module: only customer with newsletter subscription will receive an email

after:

The field "customers_newsletter" still exists, but is not updated any longer. In the modified-shop customer administration you can no longer edit this information.

The table "newsletter_recipients" contains all Newsletter subscriber information, both for customers and prospects.

The MailBeez Framework does not check for this table.

The MailBeez Newsletter Advanced module provides an adapter to use this table as a source for "prospect" lists. That allows you to both contact separately customers and prospects.

What happens?

When running this module the customer status from table "newsletter_recipients" newsletter will be synchronised into the "customers" table. If there is not entry the status will be set to 0.

What data can be lost?

When a customer is performing an "unsubscribe" the matching entry in table "newsletters_recipients" will be deleted. So you can not tell, if a customer has unsubscribed.

For this reason after running the module only those customers with a matching entry in table "newsletter_recipients" will still have a newsletter subscription.

Please check whether table "newsletter_recipients" contains all current subscriber information.

Found errors? Think you can improve this documentation?   edit this page