API Tester
The built-in API Tester lets you send test conversion events to any connected platform without affecting real leads:
How to Use the API Tester
- Navigate to Admin → Webhooks (API Tester)
- Select the platform you want to test (Facebook, Google, TikTok, etc.)
- Choose the event type to send (Purchase, Lead, etc.)
- Fill in test user data:
- Email:
[email protected](or use a real email for full match testing) - Phone:
+15551234567 - Name:
Test User - Value:
100.00
- Email:
- Click Send Test Event
- View the response immediately:
{
"status": 200,
"platform": "facebook",
"event": "Purchase",
"response": {
"events_received": 1,
"fbtrace_id": "AbC123..."
},
"match_quality": "Good"
}
What the API Tester Validates
- Credentials — Your API keys, access tokens, and pixel/dataset IDs are correct
- Event format — The event payload is properly structured for the platform
- Network connectivity — DealOracle can reach the platform's API
- Response handling — The platform accepted the event
Common Errors
| Error | Cause | Fix |
|---|---|---|
401 Unauthorized | Invalid or expired access token | Re-authenticate the integration in Admin → Integrations |
400 Bad Request | Malformed event payload | Check event mapping configuration |
403 Forbidden | Insufficient permissions | Verify your ad account has the required permissions |
429 Rate Limited | Too many requests | Wait a few minutes and try again |
Test Mode
For end-to-end testing, create a test lead and walk it through the full conversion flow:
Step-by-Step
-
Create a test lead — Click Add Lead in the Lead Manager
- Name:
Test Lead - [Your Name] - Email: Use a real email you control (for match verification)
- Phone: Your real phone number (optional, improves match quality)
- Tags: Add a
testtag for easy identification
- Name:
-
Set a conversion disposition — Change the lead's disposition to a mapped outcome (e.g., "Sold")
-
Check the Event Stream — Open the lead and go to the Event Stream tab:
- Look for "Conversion Sent" entries for each connected platform
- Verify the response code is
200 OK - Check the match quality indicator
- Note any errors or warnings
-
Verify in the ad platform — Go to each platform's event manager to confirm the test event arrived (see Platform Verification below)
Tips for Testing
- Use real email/phone for at least one test to verify match quality
- Test each disposition that has conversion mappings
- Test with all connected platforms to ensure each integration works
- After testing, you can delete the test lead or keep it tagged for reference
- Run tests after any credential changes or mapping updates
Platform Verification
After sending test events, verify they arrived in each ad platform:
Facebook / Meta
- Go to Events Manager (business.facebook.com/events_manager)
- Select your Pixel / Dataset
- Click the Test Events tab
- Look for your test event with the correct event name and parameters
- Check the match quality score (aim for Good or Excellent)
Tip: Facebook's Test Events tab shows events in near real-time. Events typically appear within 1-2 minutes.
Google Ads
- Go to Google Ads → Goals → Conversions
- Find your conversion action
- Check the Source column — it should show "Uploaded" or "Import"
- Verify the conversion count increased
Note: Google can take up to 3 hours to process uploaded conversions. Don't panic if it doesn't appear immediately.
TikTok
- Go to TikTok Ads Manager → Assets → Events
- Select your pixel
- Check the Event Debugging section
- Verify your test event appears with the correct event name
Snapchat
- Go to Snapchat Ads Manager → Events Manager
- Select your Snap Pixel
- View recent events and verify your test conversion appears
- Go to LinkedIn Campaign Manager → Analyze → Conversion Tracking
- Find your conversion rule
- Check for recent activity matching your test event
Troubleshooting Failed Tests
If a test event doesn't appear in the platform:
- Check the Event Stream in DealOracle for error details
- Verify credentials in Admin → Integrations — tokens may have expired
- Confirm the event mapping is configured for the disposition you used
- Try the API Tester to isolate whether it's a credential or mapping issue
- Check the platform's status page for outages
