Integrating PledgeBox Email Marketing with Third-Party Platforms

Integrating PledgeBox Email Marketing with Third-Party Platforms

Use Email Marketing → Integrations to import contacts from a supported platform into a PledgeBox audience. The connection form and required credentials differ by platform.

Start the connection

  1. Open Email Marketing and click Integrations.
  2. Click Add Integration.
  3. Select your platform and click Next.
  4. Enter an integration name and the fields listed below.
  5. Continue to select the source and destination audience shown by the wizard.
  6. Review the requested permissions and finish the connection.
Email Marketing platform selector with six third-party platforms outlined in red
Select the intended platform from the red outline. API and Webhook are separate general options below the platform cards.

Required fields and permissions

PlatformFields in PledgeBoxCurrent setup guidance
ShopifyShop Domain, Client ID, Client SecretUse the store’s myshopify.com domain. The connection requests read_customers.
WooCommerceStore URL, Consumer Key, Consumer SecretCreate a REST API key with Read permission.
MailchimpAPI KeyUse a Mailchimp Marketing API key for the intended account.
KlaviyoAPI KeyUse a private key with Lists (Read), Profiles (Read) and Segments (Read).
HubSpotAccess TokenUse a private app token with crm.objects.contacts.read.
Zoho CRMClient ID, Client Secret, Refresh Token, Zoho Domain, ModuleRead the Zoho-specific explanation below before generating credentials.

Shopify: use the correct store and callback

Get the exact myshopify.com domain from the store’s settings. Do not guess it from a public custom domain or an admin URL handle.

The current PledgeBox form specifies this redirect URL:

https://api.pledgebox.com/api/edm/shopify/callback

Enter the Client ID and Client Secret from the app configured for that store. Review the installation request before approving it. Customer import is separate from pushing PledgeBox orders to Shopify for fulfillment.

Zoho CRM: authorization code and Refresh Token

The current setup hint directs you to Zoho API Console, then Add Client → Self Client. It requests ZohoCRM.modules.ALL.

This is broad module access, not a read-only Contacts permission. Review the scope with your Zoho administrator before granting it. Do not add organizational or write scopes merely because an older tutorial listed them. If your organization requires a narrower scope, confirm supported scopes with PledgeBox before connecting.

During initial setup, the field labeled Refresh Token accepts the generated temporary authorization code. PledgeBox’s current hint states that the code is exchanged automatically. The authorization code and the resulting refresh token are different credentials.

  1. Copy the Client ID and Client Secret from the intended Self Client.
  2. Generate the authorization code with the scope required by the current PledgeBox setup.
  3. Paste the newly generated code into the field labeled Refresh Token.
  4. Select the Zoho Domain that matches your account’s region.
  5. Select the intended Module, then continue.

Use the code before the expiration time selected in Zoho. Do not assume every code lasts exactly ten minutes. If it has expired or has already been used, generate a new code.

See Zoho’s scope definitions and Zoho’s OAuth explanation.

Check the first sync

  1. Open the saved integration and check its connection status.
  2. Use Sync Now to start the import.
  3. Check the sync result and any error message.
  4. Open the destination audience and verify a small sample against the selected source.
  5. Check the imported email, source and subscription status before selecting the audience for a campaign.

Do not assume that creating a connection imports every contact immediately, that duplicate records are always merged, or that a fixed automatic sync interval applies. Use the integration’s actual status and sync results. Importing a contact does not itself establish permission to send marketing email.

If the connection or sync fails

Check the account, source, destination audience, required permission, token validity and regional domain. Save the exact error message. Before repeating an import, check what the first attempt added to the audience.

For ongoing failures, contact PledgeBox support with the integration name, platform and error. Do not send keys, secrets, authorization codes or refresh tokens in email or screenshots.

Disconnect access

When a connection is no longer needed, review its controls in PledgeBox and revoke the dedicated key or app authorization at the source platform. Check that revoking a shared key will not interrupt another integration.