Sync Mautic vs Allow Multiple Accounts

Allow multiple user accounts to be created, registered, and updated having the same email address. By default, WordPress only allows a specific email address to be used for a single user account. This plugin removes that restriction. The plugin’s settings page (accessed via Users -> Multiple Accounts or via the Settings link next to the plugin on the Manage Plugins page) provides the ability to allow only certain email addresses the ability to have multiple accounts (such as if you only want admins to have that ability; by default all email addresses can be used more than once). You may also specify a limit to the number of accounts an email address can have (by default there is no limit). The settings page also provides a table listing all user accounts that share email addresses (see screenshot). Compatible with Multisite and BuddyPress as well. Links: Plugin Homepage | Plugin Directory Page | Author Homepage Template Tags The plugin provides three optional template tags for use in your theme templates. Functions Returns a count of the number of users associated with the given email. Returns the users associated with the given email. Returns a boolean indicating if the given email is associated with more than one user account. Arguments $email (string) An email address. Filters The plugin exposes three filters for hooking. Typically, customizations utilizing these hooks would be put into your active theme’s functions.php file, or used by another plugin. c2c_count_multiple_accounts (filter) The ‘c2c_count_multiple_accounts’ hook allows you to use an alternative approach to safely invoke c2c_count_multiple_accounts() in such a way that if the plugin were deactivated or deleted, then your calls to the function won’t cause errors in your site. Arguments: same as for c2c_count_multiple_accounts() Example: Instead of: Do: c2c_get_users_by_email (filter) The ‘c2c_get_users_by_email’ hook allows you to use an alternative approach to safely invoke c2c_get_users_by_email() in such a way that if the plugin were deactivated or deleted, then your calls to the function won’t cause errors in your site. Arguments: same as for c2c_get_users_by_email() Example: Instead of: Do: c2c_has_multiple_accounts (filter) The ‘c2c_has_multiple_accounts’ hook allows you to use an alternative approach to safely invoke c2c_has_multiple_accounts() in such a way that if the plugin were deactivated or deleted, then your calls to the function won’t cause errors in your site. Arguments: same as for c2c_has_multiple_accounts() Example: Instead of: Do:

Mautic is an excellent Open Source Email and SMS marketing tool, but it lacks the ability to see what your contacts have purchased or if they came from your website. Sync Mautic works with WordPress to tag those subscribed via your website and also with WooCommerce so that when a customer completes an order and they are subscribed as a contact, it will automatically tag them with the products, categories, and brands they have purchased. Our plugin also provides an endpoint you can hook into for OptinMonster to collect leads, but if you don’t use OptinMonster we provided a [mautic_form] shortcode to use which will inject a form that links to your Mautic instance. Features: Supports WordPress Supports WooCommerce Supports tracking eCommerce revenue using our eCommerce Connector for Mautic [NEW] Optional order line items (product ID, name, quantity, category) for eCommerce Connector 1.3.0 [NEW] Optional signed webhook order tracking as an alternative to page hits [NEW] Optional clickthrough collection for signed webhook so orders can be attributed to the Mautic email that was clicked Supports OptinMonster using /wp-json/sync-mautic/v1/optinmonster Supports adding leads using /wp-json/sync-mautic/v1/add-lead Adds [mautic_form] shortcode to give an email signup. You can use the tag attribute to add tags in Mautic [mautic_form tag=”Tag 1, Tag 2″] Adds a checkbox to WooCommerce checkout to subscribe to newsletter Tag users of your website in Mautic Tag customers of your store in Mautic Tag subscribed contacts with products they purchase Tag subscribed contacts with categories they have purchased from Tag subscribed contacts with brands they have purchased from Upgrade Take a backup of your WordPress database and files before you upgrade. A backup lets you restore WordPress if something goes wrong. Update Sync Mautic from the WordPress plugins screen, or replace the plugin files in /wp-content/plugins/sync-mautic/. Open Settings > Sync Mautic after the upgrade and confirm your tracking settings. In Mautic, open Ecommerce Connector → Validation and set Allowed order sources to WooCommerce. Sync Mautic sends WooCommerce as the order source. GDPR and privacy This plugin may send contact, order, and revenue data to Mautic. That data may be personal data under the GDPR and similar privacy laws. Cookies are not the threshold. The signed webhook is server-to-server and does not set cookies, but it still processes personal data. Page-hit tracking uses WP Mautic visitor identification, which typically involves cookies. Page hits also send billing email on the mtc.js pageview so the order can be linked to an existing Mautic contact. Page hits do not set an additional cookie. Optional clickthrough collection stores a first-party cookie so signed webhook orders can be attributed to a Mautic email. Before you enable tracking, update your privacy and cookie policies along with cookie acceptance banners so they disclose that order, purchase, and revenue information may be sent to and stored in Mautic for marketing analytics, email attribution, segmentation, and contact profiling. Do not rely on this plugin’s settings alone; your public-facing privacy policy (and any other required notices) must reflect this processing. You are also responsible for: Having a lawful basis for processing (for example consent or legitimate interests, as applicable in your jurisdiction) Obtaining consent where required before enabling order tracking, clickthrough collection, or checkout opt-in Handling data subject requests (access, erasure, and related rights) for data stored in WordPress and in Mautic Configuring retention and security in line with your policies and legal obligations Data this plugin may send or store When order tracking is enabled, this plugin may send to Mautic (via Ecommerce Connector): Order identifiers, totals, currency, source, and order date Line items (product/item ID, name, quantity, category), when enabled Billing email on page-hit (mtc.js) pageviews and signed webhook requests, used only to link an existing Mautic contact (contacts are not created from page hits or the webhook) Optional clickthrough token (ct) for email attribution, when Collect clickthrough is enabled Links between orders and contacts, and optional attribution to Mautic emails Mautic may then store and display contact commerce fields, timeline entries, and report data derived from those orders. This plugin may also store in WordPress: Cached Mautic lead IDs on WordPress user profiles when order tagging is enabled A first-party clickthrough cookie and matching order meta when Collect clickthrough is enabled Checkout newsletter signup meta when checkout opt-in is used Order tagging and checkout opt-in may create or update Mautic contacts and tags. Past order tagging does not send historical orders to Ecommerce Connector. Access and erasure Contact export of ecommerce order history (order ID, totals, currency, source, location, date, attributed email, and line items) is handled in Mautic by Ecommerce Connector, so you can fulfill access requests there. Deleting a Mautic contact also deletes that contact’s ecommerce orders and line items in Mautic. Commerce fields on the contact are removed with the contact. Email revenue totals for those orders will drop after deletion. Merging Mautic contacts moves ecommerce orders to the remaining contact. Deleting a WordPress user does not automatically delete the matching Mautic contact or that contact’s ecommerce orders. You are solely responsible for any data protection measures required for your use of this integration. Disclaimer This software is provided as is, without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages, or other liability arising from use of this software. You are solely responsible for how you deploy and use this plugin, including compliance with applicable laws and data protection obligations.