Understanding Permissions for Data Mapper for Mailchimp

Why Permissions Are Necessary

Stripe Apps, like Data Mapper for Mailchimp, operate with strict security protocols. Permissions define exactly what data the app can access and what actions it can perform, ensuring your account remains secure while allowing the app to deliver its full functionality. When you install Data Mapper, you’ll see a list of permission requests, each with a clear purpose. These permissions enable the app to read data like customer details or product information from Stripe and sync it to Mailchimp, as well as store app-specific settings to keep your integration running smoothly.

Below, we outline each permission Data Mapper requests, its purpose, and how it supports the synchronization process described in your onboarding flow. This ensures you have full transparency into how we help you save time, enhance accuracy, and power your marketing campaigns.

Permissions and Their Role in Syncing Your Data

Customer Data

• Customer Read (customer_read) Purpose: Allows the app to look up customer information in your Stripe account. How It Helps: This permission is essential for syncing customer details—such as name, phone number, or address—to your Mailchimp audience. During onboarding, you select which customer details to sync, and this permission ensures those details are accurately transferred and updated in Mailchimp, keeping your audience profiles current.

Payment and Transaction Data

• Payment Intent Read (payment_intent_read) Purpose: Enables the app to look up customer payment details. How It Helps: This permission allows Data Mapper to track payment activities, which can be used to trigger customer journeys in Mailchimp based on payment actions, such as a completed purchase. It supports targeted marketing by connecting payment data to your audience segments.

• Charge Read (charge_read) Purpose: Creates charge events within Mailchimp. How It Helps: By accessing charge data, the app can sync purchase information to your Mailchimp store, enabling you to attribute transactions to specific contacts. This is critical for segmenting your audience based on purchase history or total spend.

• Invoice Read (invoice_read) and Credit Note Read (credit_note_read) Purpose: Creates invoice and credit note events within Mailchimp. How It Helps: These permissions allow the app to sync invoice and credit note details, which can trigger automations in Mailchimp, such as sending follow-up emails after an invoice is issued or a credit note is applied. This enhances your ability to engage customers at key moments.

• Quote Read (quote_read) Purpose: Creates quote events within Mailchimp. How It Helps: This permission enables the app to sync quote data, allowing you to trigger marketing campaigns when a quote is created or accepted, helping you nurture leads through the sales process.

Subscription and Plan Data

• Subscription Read (subscription_read) Purpose: Allows Stripe events to tag Mailchimp contacts. How It Helps: This permission lets the app track subscription events (e.g., new subscriptions or cancellations) and sync them to Mailchimp. You can use this data to tag contacts or trigger automations, such as welcoming new subscribers or re-engaging those who cancel.

• Plan Read (plan_read) Purpose: Enables migration of product plans to Mailchimp. How It Helps: This permission ensures that subscription plans from Stripe are synced to your Mailchimp store, allowing you to segment customers based on their subscription type or status, enhancing your marketing precision.

Product and Coupon Data

• Product Read (product_read) Purpose: Enables migration of products to Mailchimp. How It Helps: This permission allows the app to sync product details to your Mailchimp store, ensuring that only products with prices matching your Stripe account’s currency are included. This is key to setting up your store during onboarding and attributing purchases to the correct contacts.

• Coupon Read (coupon_read) and Promotion Code Read (promotion_code_read) Purpose: Allows migration of coupon codes to Mailchimp. How It Helps: These permissions enable the app to sync coupon and promotion code data, which can be used to create targeted campaigns in Mailchimp, such as offering discounts to specific customer segments.

Sales and Payment Links

• Checkout Session Read (checkout_session_read) and Payment Links Read (payment_links_read) Purpose: Allows migration of product sales from payment links and checkout sessions. How It Helps: These permissions let the app sync sales data from Stripe’s checkout sessions or payment links to your Mailchimp store. This ensures all purchases, regardless of how they’re made, are accurately reflected in your audience data for segmentation and automation.

• Balance Read (balance_read) Purpose: Allows migration of sales and purchase data to Mailchimp. How It Helps: This permission provides access to balance transactions, enabling the app to sync comprehensive sales data to Mailchimp. This supports historical data syncing during onboarding, giving you a complete view of customer activity.

Event and Account Data

• Event Read (event_read) Purpose: Allows reading event data from users who have installed the app. How It Helps: This permission enables the app to monitor Stripe events, such as new purchases or subscription changes, and sync them to Mailchimp to trigger customer journeys or update contact tags. It’s critical for real-time automation.

• Connected Account Read (connected_account_read) Purpose: Allows lookup of connected Stripe accounts. How It Helps: If you manage connected accounts (e.g., for a marketplace), this permission ensures the app can access relevant data from those accounts, enabling seamless syncing to Mailchimp for all your business operations.

App Configuration

• Secret Write (secret_write) Purpose: Allows storage of app-specific install details. How It Helps: This permission lets the app store configuration details, such as your selected Mailchimp audience or store settings, securely in your Stripe account. It ensures your preferences are saved and applied consistently across the app’s functionality.

• User Email Read (user_email_read) Purpose: Enables easier account signup for new Mailchimp accounts. How It Helps: This permission allows the app to access your email address to streamline the process of connecting or creating a Mailchimp account, making onboarding faster and more convenient.

How Permissions Support Your Onboarding Flow

The permissions above directly support the onboarding steps you’ve outlined:

• Selecting a Mailchimp Audience and Permissions: Permissions like customer_read and user_email_read ensure customer data and account details are accessible for syncing and setup.

• Creating a Mailchimp Store: Permissions such as product_read, charge_read, and balance_read enable the app to sync products and historical purchase data to your store, ensuring only products with matching currencies are included.

• Syncing Historical Data: Permissions like customer_read, charge_read, and subscription_read allow the app to import past customers and transactions, providing a complete dataset for your marketing efforts.

• Choosing Customer Details to Sync: The customer_read permission ensures the app can access and transfer specific details (e.g., name, phone, address) to Mailchimp, updating existing contacts as needed.