Keyring Social Importers vs Sync Mautic

Please read about each importer before running this plugin. This package of social importers provide you with the ability to pull in your content that gets created on other sites, and re-publish it on your own WordPress site. Rather than leaving others in control of everything you’ve put time and effort into, why not host it yourself on your one true, home-on-the-web, WordPress? Read more about this technique/approach to data ownership. After an initial import, all of these importers can also optionally check each hour and automatically download new content as well, keeping things in sync over time. They all currently import as Posts, with specific Post Formats, depending on the content type. Importers included currently: Delicious Fitbit Flickr Foursquare/Swarm Instagram Instapaper Jetpack/WordPress.com Moves Nest Cameras Pinterest Pocket Strava TripIt Twitter You can potentially write your own importers as well, using the base class included. Importers Common Features If you select to ‘auto-import new content’, all importers will check once per hour for new content. All posts created by the importers are associated with a taxonomy called keyring_service, which allows you to filter/select them. Appears in wp-admin as “Imported From” under the Posts menu. Every attempt is made to download/store as much data as possible, and use it intelligently (e.g. tags). Raw import data is stored in a custom field (raw_import_data) as a json_encode()ed string. Delicious Every bookmark from your Delicious account is imported as a post. All imported posts are marked with the ‘link’ Post Format. delicious_id and the href/link itself are saved as custom fields. Tags used on Delicious are used in WordPress. Fitbit Very basic for now, just imports your data and creates a simple summary post. Summary post only contains a statement about how many steps you took that day. Flickr Every photo in your Flickr account is downloaded (the actual, original image) and imported into your Media Library. For every photo, a Post is created and published, containing that one image (and it is attached within WordPress). Posts are marked with the ‘image’ Post Format. Posts are created with the publish date matching the ‘Taken’ date of the photo. The modified date (of the Post) is set to the ‘Upload’ date from Flickr. There is no support/handling of Galleries, Sets or anything else in Flickr, just one Post per photo. Tags used on Flickr are used on WordPress. If available, geo data is downloaded and stored per the WordPress Geodata guidelines. flickr_id and the full URL to the photo page are stored as custom fields. Foursquare Imports each check-in on Foursquare as a separate Post. Marks those Posts with the ‘status’ Post Format. foursquare_id plus geo lat/long are stored as separate custom fields, per the WordPress Geodata guidelines. Instagram Each photo on your Instagram account is downloaded and imported into your Media Library. For every photo, a Post is created and published, containing that one image (and it is attached within WordPress). Posts are marked with the ‘image’ Post Format. The name of the filter used is stored as instagram_filter, the URL to the photo page is stored as instagram_url. Instapaper Imports your Archived links and creates a post for each of them (with post format of Link). Uses the title from the document in Instapaper, if there is a description associated then it uses that as well. NEW: Downloads the full content of the article using Instapaper’s API, and stores that in the post content, so that you can search it later. Disable it by creating a stub plugin, or dropping this in your theme’s functions.php; add_filter( ‘keyring_instapaper_download_article_texts’, ‘__return_false’ ); Jetpack/WordPress.com Import posts from either self-hosted, or hosted copies of WordPress, via the Jetpack/WordPress.com API. Post author is always overridden. Tags, content, title, excerpt are all carried over. Moves Imports your data daily. Creates a summary post, which is a bulleted list detailing each category of activity for the day. Stores raw and summary data for further processing. Nest (Camera) Allows you to pick hours of the day to take snapshots from your cameras. You can pick anything between no snapshots, or one every hour, per camera. Each snapshot will be downloaded directly into your Media Library. Each snapshot will also be published as a Post (with post type of “image”) using the Author/Category/Tag options you select. If you click the “Check For New Content Now” button, when configured for auto-import, then all cameras with at least one scheduled snapshot will take one right now, regardless of what time they’re scheduled (good for verifying that things work, or taking a specific snapshot for whatever reason). Does not require a Nest Aware subscription, since the relatively infrequent snapshots are under request limits. Pinterest NEW: This is a new addition, and is pretty rough still. Not recommended for production sites. Imports every individual pin as a post (can be a LOT), with a Post Format of “image”. Stores the image for each pin in your Media Library. Pocket Imports links and creates a post for each of them, with the Link post format. Uses as many details (e.g. title) as possible from Pocket. Strava Activities are imported as new Posts. * Activity type is stored as post meta for easier querying. GPS data is stored as an encoded polyline if available. [https://github.com/emcconville/google-map-polyline-encoding-tool](Google Maps Polyline Encoding Tool) has been tested to work well with the data. Stores raw and summary data for further processing. Currently does NOT download any media or support People & Places. TripIt Trips are imported, with flights mapped and posted as Status-format posts. Geo data is stored using something resembling the WordPress Geodata guidelines. Posts are tagged using airport codes and city names. Now supports paging through the API to avoid timeouts on accounts with lots of trip data. Twitter Every tweet will be downloaded as an individual Post. Posts are marked with the ‘aside’ Post Format. If available, geo data is downloaded and stored per the WordPress Geodata guidelines. Twitter_id and twitter_permalink are stored. If your tweet contains #hashtags, they are applied as tags within WordPress. “Entities” are expanded (URLs are not t.co, they are the real/final URLs).

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.