Vainu View

Vainu View is a feature designed for teams who need a quick access to Vainu's data without the need to leave their CRM. At its core, Vainu View is just a URL that points to the company profile of a given company. This URL is then often feeded into an iframe element or a similar embedding for the most convenient way to access the company profile.

The following steps are useful in defining how Vainu View should be set up for your organization.

We will cover these questions in the following paragraphs in more detail.

To be able to use Vainu View, you will firstly need a place to store the URL that is then used to open the company profile. Commonly, Vainu View is set up in CRM systems. In those cases, the recommended approach is to create a new field within the Company/Account object that will store the URL. Technically, this field can of course exist in any system that is capable of storing data.

Depending on the type of link used (see next paragraph for more details), the field might need to be able to accommodate a long string. Tokenized links contain an authentication token that is over 100 characters long. Therefore, we usually recommend using field types that can accept long strings of text. Otherwise, the link might populate only partially and not work properly.

Vainu View is currently available through different types of links which differ in how they are set up, and how they actually work: a tokenized link and a non-tokenized link. A tokenized link is strongly recommended for its ease of use, but it requires either the use of Vainu Connector or Vainu API. Non-tokenized link is the alternative option when setting up a tokenized link is not an option due to technical or contractual constraints.

To set up a tokenized Vainu View link you need to use either Vainu Connector or Vainu API.

In Connector, you need to make sure that the field you created for this purpose is mapped with a data point called "Vainu view link". If that option is not available in the data management settings, please reach out to our support team to verify that your permissions have been set up correctly. The option is not available if Vainu View is not part of your organization's agreement.

In API, you should build an automation that takes the business ID of the company in a format that includes both the country prefix and the organization number (FI12345678) and fetches the tokenized link using the following endpoint where you replace *businessid* with the correct business ID:

This query then returns a tokenized link you can store in a separate field. If the query fails due to a permission error, please reach out to our support team to verify that your permissions have been set up correctly. The endpoint is not available if Vainu View is not part of your organization's agreement.

Setting up a non-tokenized link is the alternative approach when setting up a tokenized link through Vainu Connector or Vainu API is not possible due to technical or contractual constraints.

The setup is relatively easy as you only need to create links using this simple pattern where you replace *businessid* with the correct business ID in a format that includes both the country prefix and the organization number (FI12345678).

The key decision is finding out how to make the link dynamic, so it reads the business ID from a separate field to complete the link automatically. Depending on the system where Vainu View is configured there may or may not be an easy ready-made approach to build dynamic links.

The final step in setting up Vainu View is deciding whether or not you want to embed Vainu View into your existing system. It is of course possible to skip this part entirely, and just use the link to open up the company profile in Vainu in a separate browser tab. However, a lot of people prefer an embedded Vainu View for truly making Vainu feel like a native part of your existing system.

The actual process to create an embedded view depends on the system used. As long as the system can load external HTML content to an iframe or a similar element, then building an embedded view should be possible.

We have step-by-step instructions to embed Vainu View to Salesforce, Dynamics, and SuperOffice. Note that due to limitations in the SuperOffice integration, it is only possible to configure Vainu View with a non-tokenized link where the embedded view can only be accessed with Vainu login credentials.

If Vainu View has been set up using a tokenized link, it basically mirrors the settings of one particular user. In most cases, this user is the CRM main user. Unfortunately, the identity of the CRM main user is not visible on the platform, but our support team can identify the correct user. Once the user has been identified, it is up to that user to make any changes to their settings at their own discretion.

Similarly to the previous question, the Research Agent view is mirrored from the CRM main user's Vainu account. They define which prompt is the default that applies for all Vainu Views of the organization, and they can only see prompts that have been shared with them. If you want access to your own prompt, you will need to share it with this user. As explained above, the CRM main user is not visible on the platform, but our support team can help identify the correct user.

Vainu View is natively available in HubSpot through the Vainu Similar Companies element. Make sure the element is visible on the Company page layout in HubSpot through Settings -> Data Management -> Properties -> Objects -> Companies -> Record Customization.

Once the element is visible, you should see a "Vainu View for *Company X*" link near the bottom of the element. Clicking on the link opens up the company card in a pop up window.

HubSpot's Vainu View uses our domain database as its source whenever Vainu View is not part of your organization's agreement. If you believe Vainu View should be part of your agreement, please reach to our support team so they can make sure that the permissions have been set up according to the agreement.

Yes, but that requires a login so we can identify the user who initiated the export. This works automatically when using non-tokenized links, as users always login to Vainu View anyway. With tokenized links, initiating the export will prompt for a user login before allowing the creation of new contacts.

If your Vainu View is still using the old user interface, the URLs are probably pointing towards our older platform. The format of the stored Vainu View links are then usually like this (where *businessid* is the full business ID of the given company):

As the old platform will be sundowned at some point in the near future, we strongly recommend migrating your organization to use the new Vainu View using the instructions detailed in this document. This update will also introduce valuable new features such as improved contact data, Vainu Research Agent etc.

While it might be possible to just update the existing implementation with new links, we strongly recommend building the implementation from scratch for two reasons: