Drip Integration

Drip is an email marketing platform built around ecommerce automation and customer journey workflows. WP Smart Consent integrates with Drip via the Subscribers API v2, forwarding opted-in contacts to your account in real time using a single POST /subscribers upsert call.

What You’ll Need#

A Drip API token and your Drip Account ID. To find them, log into your Drip account and go to User Settings (top right avatar) → API. Copy your API token from there. Your Account ID is the numeric value visible in the URL when logged into your Drip dashboard, for example https://app.getdrip.com/123456/ where 123456 is your Account ID.

Connection Tab#

Enter your Account ID and API token in the Connection tab and save. Drip does not have traditional contact lists — segmentation is done entirely through tags. WP Smart Consent uses the Tags tab in place of a list selector, and fetches your existing tags from the account to populate the picker.

Field Mapping Tab#

Email, first name, and last name are always sent to Drip. In Drip’s API, first name and last name are stored as custom_fields rather than top-level contact properties — WP Smart Consent handles this automatically.

The field mapping tab lets you forward additional contact data to Drip custom fields. Drip custom fields are referenced by their field name exactly as defined in your Drip account. In the field mapping table, set the destination key to the custom field name — for example phone, company, or city. Custom fields must exist in your Drip account before they will appear on contact records.

Available WPSC source fields for mapping: phone, company, country, order total, source URL, and any custom global data fields you have defined.

Options Tab#

Update existing — when enabled (the default), if a subscriber with the same email already exists in Drip their custom fields and tags will be updated. When disabled, the call still runs but Drip’s own upsert behaviour applies — existing subscribers are not removed, but field values may or may not be overwritten depending on Drip’s current API behaviour.

Send on unchecked — when enabled, contacts are forwarded to Drip even when the opt-in checkbox was not ticked. Use this if you manage consent at the Drip automation level rather than at the checkbox level.

Tags Tab#

Enter a comma-separated list of tags to apply to every contact forwarded through this integration. Tags are merged with any tags already on the subscriber — existing tags are never removed. If a tag does not exist in your Drip account it will be created automatically on first use.

Drip tags are how you segment subscribers into audiences and trigger automations, so using a dedicated tag like wpsc_optin or newsletter_subscriber makes it easy to build Drip workflows triggered by WP Smart Consent opt-ins.

How the API Call Works#

WP Smart Consent sends a single POST to https://api.getdrip.com/v2/{account_id}/subscribers with the following structure:

json

{
  "subscribers": [{
    "email": "jane@example.com",
    "tags": ["newsletter", "wpsc_optin"],
    "custom_fields": {
      "first_name": "Jane",
      "last_name": "Smith",
      "phone": "+1 555 000 0000"
    },
    "status": "active"
  }]
}

Tags from the Tags tab and any tags from the list picker are merged into a single deduplicated array. All custom field mappings including first name and last name go into custom_fields.

Troubleshooting#

Contact not appearing in Drip — verify both the Account ID and API token are correct. A wrong Account ID returns a 404; a wrong token returns a 401. Both fail silently unless WordPress debug logging is enabled.

Custom field values not saving — confirm the field name in the mapping table exactly matches the custom field name in your Drip account. Drip custom field names are case-sensitive.

Tags not being applied — if a tag name contains special characters or spaces, Drip may normalise it. Check your Drip account under Subscribers → Tags to see the exact tag name that was created.