Skip to main content
Practical tips for keeping your Invoca integrations secure and stable — dedicated integration users, a single source of leads, and what to check before renaming Signals or deactivating an integration.

​
Create a dedicated user for your integrations

We recommend creating a new Invoca user explicitly for each integration — for example, invocagoogleadsintegration@yourcompany.com. This lets you assign the minimum permissions the integration needs, keeping your account more secure, and avoids disruptions when an employee tied to a shared login leaves the company or changes roles. Necessary permissions vary by integration — refer to each integration’s documentation for its specific requirements. This is especially relevant for integrations using an OAuth 2.0 handshake, including Google Ads, Salesforce Sales Cloud, Search Ads 360, and Google Campaign Manager.

​
Establish a single source of leads

When several apps send data back and forth about the same leads and conversions without a clear plan for how data flows between systems, it’s easy to introduce errors like duplicate or mismatched records. Establish one single source of leads across your tools, which then flows into other apps.

​
Resetting your password? Check your integrations

For security, Invoca revokes API access tokens when a user resets their password. If you authenticated an integration with your own credentials and then reset your password, you’ll need to re-authenticate that integration.

​
Be careful when renaming or deleting Signals

Many integrations are built around Signals. If a Signal is sent to another platform, use extreme caution when renaming or deleting it. In the Google Ads, Microsoft Advertising, and Facebook integrations, you’ll need to revisit your Configuration settings after renaming or deleting a Signal — remove the original Signal row on the Configuration page and re-add the new Signal.

​
Before you deactivate an integration

If you want to deactivate a connect app integration (Facebook Ads, Google Ads, Salesforce Sales Cloud, or Salesforce Marketing Cloud), use the deactivate flow within the Invoca platform rather than removing access from the integrated platform directly. Deactivating through Invoca triggers cleanup — removing app access, deleting webhooks, and removing certain Invoca-created objects — that helps minimize errors.

​
If you’re troubleshooting errors, check your response codes

Invoca provides webhook health stats showing the most recent response code for a failed request on connect apps, and a Last Status Code column with more detail (including the response body) for custom webhooks. Searching the response body’s error text often surfaces public API documentation explaining the cause — for example, a Search Ads 360 error mentioning a missing Click ID can be searched directly to find Google’s own diagnostic guidance.

​
Where to go next

Last modified on September 25, 2026