How It WorksPricingIntegrationsAffiliatesDocsBlog
Log inGet Started
Back to DocsTroubleshooting

Integration Connection Issues

Fix common OAuth failures, token expirations, and permission errors.

Table of contents

OAuth Failed

If the OAuth popup closes without successfully connecting, or you see an error during the authorization flow, try these steps:

Quick Fixes

  1. Check popup blockers — DealOracle opens a popup window for OAuth. If your browser blocks it, the flow can't complete.

    • Look for a "popup blocked" indicator in your browser's address bar
    • Allow popups for app.dealoracle.com (or your custom domain)

  2. Try a different browser — Some browser extensions (especially ad blockers or privacy extensions) can interfere with OAuth redirects. Try Chrome, Firefox, or Safari without extensions.

  3. Check you're logged into the correct account — The OAuth flow will connect to whatever ad platform account you're currently logged into. Make sure you're logged into the account that owns the pixels/conversions you want to use.

  4. Clear cookies and retry — Stale session cookies from the ad platform can cause OAuth failures. Clear cookies for the ad platform's domain, then try again.

If the Problem Persists

  • Check the ad platform's status page for outages
  • Try connecting from a different device or network
  • Contact DealOracle support with the error message (if shown)

Token Expired

OAuth tokens expire periodically. DealOracle automatically refreshes them in the background, but sometimes the refresh token itself expires or becomes invalid.

Symptoms

  • Integration shows a yellow warning status
  • Conversions start failing with invalid_token errors
  • The integration shows "Token expired" in the status detail

How to Fix

  1. Go to Integrations
  2. Click Disconnect on the affected platform
  3. Click Connect to re-authorize
  4. Complete the OAuth flow
  5. Verify the status shows green / connected

What's Preserved

When you disconnect and reconnect:

  • Event mappings — Preserved (your disposition-to-event mappings stay intact)
  • Platform settings — Preserved (pixel IDs, conversion action IDs)
  • Historical data — Preserved (past conversion events are not affected)
  • OAuth token — Replaced with a fresh one

Preventing Token Issues

  • Don't change your ad platform password without re-authorizing DealOracle
  • Don't revoke DealOracle's app access from within the ad platform settings
  • If you use two-factor authentication, ensure it doesn't block automated token refreshes

Permissions Changed

If someone changes your role or access on the ad platform, DealOracle's integration may stop working even though the token is still valid.

Common Scenarios

  • Removed from Business Manager — On Facebook, if you're removed from the Business Manager that owns the pixel, the integration can't send events
  • Downgraded role — If your role is changed from Admin to Analyst on the ad platform, you may lose write access needed to send conversions
  • Pixel ownership transferred — If the pixel or conversion action is moved to a different account

How to Fix

  1. Restore your permissions on the ad platform (or have an admin do it)
  2. Go to Integrations in DealOracle
  3. Disconnect and Reconnect the integration to get a fresh token with updated permissions
  4. Verify by checking a test lead's event stream for successful conversion sends

Prevention

  • Use a dedicated service account for DealOracle integrations rather than a personal account
  • Notify your team not to modify the integration account's permissions without coordinating

Rate Limiting

Ad platforms impose rate limits on API calls, including conversion event uploads. If you're sending a high volume of conversions in a short time, platforms may temporarily reject requests.

Symptoms

  • Event stream shows 429 errors on some conversion attempts
  • Some conversions send successfully while others fail
  • Errors appear in bursts rather than consistently

How DealOracle Handles Rate Limits

DealOracle automatically handles rate limiting:

  1. Detects the 429 response from the platform
  2. Queues the failed conversion for retry
  3. Retries with exponential backoff (waits longer between each retry)
  4. Succeeds once the rate limit window resets

What You Should Do

  • Usually nothing — DealOracle's auto-retry handles most rate limiting situations
  • Check event stream — Look for the conversion event status. If it shows "Retrying" or "Pending", it will be sent automatically
  • If retries exhaust — After multiple failed retries, the event is marked as failed. You can manually re-trigger it from the lead's event stream

Reducing Rate Limit Issues

  • Avoid bulk-updating hundreds of lead dispositions simultaneously
  • If importing leads in bulk, stagger disposition changes over time
  • Contact DealOracle support if you consistently hit rate limits — we can help optimize your sending pattern
#debugging#integrations#oauth#troubleshooting