Troubleshooting Integrations & Auth Errors

Integrations play a crucial role in ensuring data consistency and accuracy in SegMetrics. Understanding the notifications you receive about your integrations is vital, as these can signal potential issues that may affect the quality of your data. This guide explains common integration errors and how to resolve them.


You'll receive notifications about your SegMetrics account through email and the notification bell icon with a red number within the app as shown below. \ You can also see important notifcations at the bottom of your homepage.

These notifications are designed to alert you immediately when there's an issue with your data imports, so you can take quick action to maintain data accuracy.


Types of Notifications

Re-Connect Your Integration

These alerts indicate a failure in the integration import process. It could be due to invalid credentials, account permissions, or errors in the data.

What to do:

  1. Click the link "Click here to re-authorize your account"
  2. This will take you to the Integration page so you can reconnect your integration
  3. Once you click this link, the notification will disappear

⚠️ Important Warning: Be sure to select Reconnect Integration for your integrations and DO NOT select Disconnect as that will DELETE all the data and depending on the integration, your data might not be imported back.

Data Upload Failed

This indicates that there was an error with uploading your data.

What to do:

  1. Click the link "Click here to try again"
  2. This will take you to the Integration page so you can attempt to upload the data again
  3. Once you click the link, the notification will no longer show

Troubleshooting Common Issues

Invalid Credentials

Problem: Your integration stops working due to authentication issues.

Common causes:

  • Username, password, or API key has been changed recently on your integration's side
  • Unintentional white space in credentials
  • Wrong case (uppercase/lowercase) in credentials
  • Expired API keys or tokens

Solution:

  1. Go to your Integrations page
  2. Click on the problematic integration
  3. Click re-connect and re-enter your credentials carefully
  4. Ensure no extra spaces before or after your credentials
  5. Verify the correct case for usernames and API keys
  6. Wait for the next standard account sync and see if the data is updated

Ad Account Permissions

Problem: Ad platform integrations fail to sync data.

Requirements: We require edit permissions for all ad account integrations.

Solution:

  1. Log into your ad platform (Facebook, Google, etc.)
  2. Navigate to account permissions or user management
  3. Ensure the SegMetrics integration has edit permissions
  4. Update permissions if necessary
  5. Reconnect the integration in SegMetrics

Expired OAuth Tokens

Problem: OAuth-based integrations (like Google, Facebook) stop working after a period.

Solution:

  1. Navigate to the Integration page
  2. Find the expired integration
  3. Click "Reconnect Integration"
  4. Complete the OAuth authorization process again
  5. Verify the integration is working properly

Best Practices

Regular Monitoring

  • Check notifications daily: Regularly monitor the notification bell icon for any alerts
  • Set up email alerts: Ensure you're receiving email notifications for integration issues
  • Weekly integration review: Perform a weekly check of all your integrations' status

Credential Management

  • Document credential changes: Keep track of when you update passwords or API keys
  • Test after changes: Always test integrations after making credential changes
  • Use secure storage: Store API keys and credentials securely

Proactive Maintenance

  • Update API keys before expiration: Many platforms provide expiration dates for API keys
  • Monitor integration logs: Check for warning messages that might indicate future issues
  • Keep integrations current: Update to newer API versions when available

Data Validation

  • Verify data after reconnection: Check that data is flowing correctly after fixing issues
  • Compare data points: Ensure imported data matches what you see in the source platform
  • Monitor for gaps: Look for any missing data periods during integration downtime

When to Contact Support

Reach out to support at help@segmetrics.io if you're experiencing:

  • Persistent authorization failures after trying the troubleshooting steps
  • Data discrepancies between SegMetrics and your source platforms
  • Unknown error messages not covered in this guide
  • Multiple integration failures happening simultaneously
  • Questions about specific error notifications

When contacting support, include:

  • Screenshot of the error notification
  • Integration platform name (Facebook, Google, etc.)
  • Steps you've already tried
  • When the issue first started occurring

Frequently Asked Questions

Q. Why do I keep getting re-authorization requests for the same integration?

A. This usually indicates an issue with API permissions or an expired OAuth token. Check that your integration has the necessary permissions in the source platform and consider updating your API credentials.

Q. What happens if I accidentally click "Disconnect" instead of "Reconnect"?

A. Clicking "Disconnect" will delete all imported data from that integration. Depending on the integration type, historical data may not be recoverable. Always use "Reconnect Integration" for authorization issues.

Q. How often should I expect to re-authorize integrations?

A. Most integrations should maintain their connection indefinitely. However, OAuth-based integrations (like Google and Facebook) may require re-authorization every 90 days to 1 year, depending on the platform's policies.

Q. Can I prevent integration errors from happening?

A. While you can't prevent all errors, you can minimize them by keeping credentials current, monitoring notifications regularly, and ensuring your connected accounts have the proper permissions.

Q. What's the difference between a temporary error and a permanent failure?

A. Temporary errors (like rate limiting) often resolve themselves within a few hours. Permanent failures (like invalid credentials) require action on your part to resolve and won't fix themselves over time.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us