Showing results for 
Show  only  | Search instead for 
Did you mean: 
This is a verified product documentation article. For case-based resolutions articles, please reference the Knowledge Base section of Invoca Community.

Sharing Invoca data with your other marketing software can leave you with a lot to keep track of. Apps, users, permissions, and tokens… oh my. What’s the best way to stay on top of it all? Here are some tips to help make sure platforms stay connected and things work seamlessly.

Create a dedicated user for your integrations

Whenever you set up a new Invoca integration, we recommend creating a new user in your Invoca account explicitly for that integration. For example, if you want to create a new Invoca for Google Ads integration, create an account for

By creating a new user that is specific to the integration, you can assign the minimum permissions required for the integration to work. This helps keep your account secure. In addition, it also helps avoid disruptions to the integration in cases where an employee is removed due to turnover or a change in roles. Imagine, if a user that is tied to a specific employee is used for authentication, then the integration would break when that employee leaves the company and their associated user is removed from the platform.

The necessary permissions are different for each integration. Refer to the Integration Details documentation for each integration to see permission requirements.

This is especially relevant for integrations that use an OAuth 2.0 handshake to authenticate your integration, which include:

  • Invoca for AdWords
  • Google Ads
  • Salesforce Sales Cloud
  • Search Ads 360
  • Google Campaign Manager

Note that Facebook Ads uses OAuth 2.0, but Facebook requires users to be associated with a legitimate Facebook personal account.

Establish a single source of leads  

When you have several different apps sending data back and forth about the same leads and conversions, without a detailed plan about how you want your data to flow between systems, it can be easy to introduce errors to your data, such as duplicate or mismatched records. To address this, we recommend you establish one single source of leads across your tools, which can then flow into other apps. 

Need to reset your password? Check your integrations!

For security purposes, Invoca revokes API access tokens for users when they reset their password. If you authenticated with your user credentials and subsequently reset your password, you’ll want to hop back into Invoca to re-authenticate.

Beware When Renaming or Deleting Signals

Many integrations are built around Signals. If you have selected a Signal to be sent to another platform, practice extreme caution when changing the Signal name or deleting the Signal.

In the Google Ads, Microsoft Advertising, and Facebook integrations, you will 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 would like to deactivate any of the connect app integrations (Facebook Ads, Google Ads, Salesforce Sales Cloud, and Salesforce Marketing Cloud) be sure to follow the deactivate flow from the Invoca platform. Do not remove access from the integrated platform.

By navigating to the connect app in the Invoca platform and clicking “deactivate”, we will do some clean-up to help minimize errors. For example, we will remove our app access, delete webhooks to stop sending data to the other platform, and remove certain Invoca-created objects.

If you're troubleshooting errors, check your response codes

While we do our best to monitor and handle exceptions, it is beneficial to know how to troubleshoot integration errors.

For connect apps, Invoca provides webhook health stats that will show the most recent response code for a failed request. Similarly, for custom webhooks, Invoca provides a Last Status Code column. When clicked, the Last Status Code will provide more detail, including the response body.

If you copy information from the response into a search engine, you’ll often be linked to public facing API documentation that will provide an indication of what caused the error. For example, let’s say I have an integration with Search Ads 360 and I see my last request failed with the following response body:

"error": {
  "errors": [
    "domain": "global",
    "reason": "requestValidation",
    "message": "The request was not valid. Details: [0x00000101: Click ID 'XXXXXXXXXXXXXXXXXXXXXX' is not found for conversion index=0 conversionId=FF801E53-EAXXXXXX]"
 "code": 400,
 "message": "The request was not valid. Details: [0x00000101: Click ID  'XXXXXXXXXXXXXXXXXXXXXX' is not found for conversion index=0 conversionId=FF801E53-EAXXXXXX]"

Searching for “DoubleClick Search 0x00000101”, brings up this article from the Google knowledge base with suggestions on how to diagnose and fix.


• Basic Knowledge: Invoca webhooks 
• Best practices for configuring and managing your integrations 
• Basic Knowledge: Invoca reports 
• Basic Knowledge: Signals 

Need more help?

Don't see what you are looking for? You can ask the Community or contact support.