How can we help you?

1. Overview & System Requirements

The Gravity Forms Sentry Integration delivers enterprise application error tracking, crash reporting, performance tracing, and diagnostic observability directly to your Sentry dashboard. When enterprise websites, WooCommerce checkouts, payment intake portals, or complex multi-step questionnaires experience PHP fatal exceptions, third-party webhook dispatch failures, validation crashes, or payment gateway timeouts, this integration captures the entire execution context with rich stack traces, breadcrumbs, user identifiers, and form metadata.

Instead of relying on customers reporting broken forms or sifting through massive unformatted PHP error logs on your web server, your engineering team receives instant alerts via Slack, PagerDuty, or email the moment an issue occurs. With full environmental tagging and release tracking, developers can diagnose and resolve critical intake bugs before they impact revenue.

2. Authentication & Sentry DSN Configuration

The integration uses Sentry’s standardized DSN architecture to transmit error events and performance spans over HTTPS directly to Sentry ingestion endpoints:

Obtaining Your Sentry DSN

1. Log in to your Sentry Dashboard at sentry.io.
2. Navigate to Settings → Projects and select your target WordPress / PHP project (or click Create Project and select PHP).
3. In the project settings sidebar, click on Client Keys (DSN).
4. Copy the complete DSN URL (e.g., https://abcdef123456@o123456.ingest.sentry.io/7891011).

Configuring in WordPress Dashboard

1. In your WordPress dashboard, navigate to Forms → Settings → Sentry.
2. Paste your Sentry DSN URL into the Sentry DSN input field.
3. Specify your Environment Name (e.g. production, staging, or development).
4. Optionally set the Release Version (e.g. v2.4.1 or Git commit hash) to track errors across deployments.
5. Click Save Settings. Click the Send Test Event button to verify that a test error appears in your Sentry dashboard.

3. Feed Configuration & Event Instrumentation

The integration operates at both the global form engine level and individual form feed levels to track critical error conditions:

Monitored Error Events

• Payment Gateway Failures: Captures card declines, 3D Secure authentication drop-offs, and API communication errors from Stripe, Square, PayPal, and Authorize.net.
• Feed Processing Exceptions: Automatically intercepts fatal errors or unhandled exceptions thrown by third-party CRM and marketing add-ons during entry dispatch.
• Validation Failures & Spam Rejections: Logs recurring honeypot or reCAPTCHA validation blocks to detect coordinated bot attacks.
• File Upload Exceptions: Records MIME type validation failures, disk quota errors, and corrupted file attachment transfers.

Contextual Metadata & Breadcrumbs

• Form Attributes: Captures Form ID, Form Title, Entry ID, and submission URL.
• User Context: Records User ID, Role, and IP address (with option to anonymize IP for GDPR compliance).
• Execution Breadcrumbs: Records step-by-step chronology leading to the failure (e.g. Form Rendered → Step 2 Navigated → Payment Submitted → Gateway Timeout).

4. Advanced Performance Tracing & Observability

Sentry Performance Monitoring allows engineering teams to identify submission bottlenecks:

• Transaction Spans: Measures exact elapsed execution duration for individual form lifecycle events: validation runtime, database write latency, notification dispatch, and external API calls.
• Slow Feed Detection: Automatically flags external APIs that take more than 2,000ms to respond, preventing poor user experience during checkout.
• Release Health & Regression Tracking: Correlate new WordPress theme or plugin updates with sudden spikes in form submission errors.

5. Error Handling & Troubleshooting Matrix

Troubleshoot common Sentry integration issues using the reference matrix below:

6. Developer Extensibility & Filter Hooks

Developers can programmatically append custom tags, sanitize sensitive PII, or filter error events before transmission to Sentry:

/**
 * Filter: gform_sentry_before_capture
 * Purpose: Sanitize user PII or filter benign errors before sending to Sentry.
 * 
 * @param array $event The raw Sentry event payload array.
 * @param array $form  The Gravity Forms form object.
 * @param array $entry The submitted entry object.
 * @return array|null Modified event or null to discard event.
 */
add_filter( 'gform_sentry_before_capture', function( $event, $form, $entry ) {
    // Strip sensitive fields (e.g. credit card last 4 or SSN) from extra context
    if ( isset( $event['extra']['entry_data'] ) ) {
        unset( $event['extra']['entry_data']['field_ssn'] );
    }
    
    // Tag event with high priority if form value exceeds $1,000
    $payment_amount = floatval( rgar( $entry, 'payment_amount' ) );
    if ( $payment_amount > 1000 ) {
        $event['tags']['high_value_transaction'] = 'true';
        $event['level'] = 'fatal';
    }
    
    return $event;
}, 10, 3 );

{build_terminal_block(”’/**
* Action: gform_sentry_capture_custom_message
* Purpose: Send a custom operational alert to Sentry on anomalous form behavior.
*/
add_action( ‘gform_after_submission’, function( $entry, $form ) {
$submission_duration = floatval( rgar( $entry, ‘time_to_fill’ ) );

// Alert Sentry if form completion was unnaturally rapid (potential bot bypass)
if ( $submission_duration > 0 && $submission_duration < 2.0 ) {
do_action( 'gform_sentry_capture_message',
sprintf( 'Suspicious rapid submission on Form #%d (Entry #%d): %.2fs', $form['id'], $entry['id'], $submission_duration ),
'warning'
);
}
}, 10, 2 );''', "Capture Custom Sentry Alert")}

7. Frequently Asked Questions