Blogs

  • integrate Salesforce with Google AdWords

    Introduction to Connect Salesforce to Google Ads :

    • Salesforce and Google Ads are two tools that are a staple of any marketer’s technology stack. 
    • Google Ads provides the world’s largest advertising platform, being able to reach anyone with an internet connection, and Salesforce is the world’s most popular CRM system to track your prospects and customers.
    • These two companies have created best in breed solutions, but if you are using both, you will know how hard it is to integrate the systems to produce the analytics you need. 
    • Without connecting the dots between your marketing and CRM data, you cannot fully optimize your campaigns. Let’s look into why this is important

    Why Connect Salesforce to Google Ads?

    • If you are using Salesforce & Google Ads, you will most likely be generating a portion of your leads through advertisements on Google.
    • This will flow through to your website where a customer will fill in a form, which, if properly integrated, should appear in your Leads object in Salesforce.
    • If you have this kind of setup, it’s already pretty slick, and you can effortlessly get customer inquiries for your product or service. 
    • But how do you understand which campaigns are the top performers? Which campaigns are bringing the most customers, and therefore where should you be spending your money? How do you see your ROI from Marketing spend?
    • These answers are impossible to answer without connecting your Salesforce Lead & Opportunity data, with Google Ads.

    Auto-Tagging :

    • Auto-tagging is a required feature, which when used with Google Ads conversion tracking, allows you to see how effectively your ad clicks lead to valuable customer activity, such as website purchases, phone calls, app downloads, and more.
    • Auto-tagging is turned off by default. To turn it on, follow the steps below.
    • Sign in to your Google Ads account.
    • In the left page menu, click Settings > Account Settings > Auto-tagging
    • Check the box “Tag the URL that people click through from my ad” and Save

    Steps to Integrate Salesforce to Google Ads Account:

    Step 1: Configure your Salesforce account

    • Create a custom field with the Name “GCLID”. Length should be 255 characters.
    • The field should be read-only so the users don’t accidentally alter it.
    • Field history tracking for the field “Stage” should be enabled.

  • How to use the Lookup field in Lightning DataTable?

    We all know that Salesforce standard Lightning DataTable is the best table that we can use to display the record and it also does support the in-line editing. There are some limitations of the Standard lightning datatable like we can not have a lookup field, Picklist field or event some file upload for every column. In this blog post, I will show you how you can create a custom data type to show lookup, picklist, or anything that you wanted to have.

    Step1 – Create a new Lightning Web Component

    In this step, we will create a lightning web component which will extend the LightningDatatable like below

    export default class ExtendedDataTable extends LightningDatatable { }

    Extending LightningDatatable will help us to create our own Lightning DataTable Data Type

    Step2 – Create a Custom DataType for Custom Lookup



    Now, as you have created the new component, in the js file of the same component create a custom datatype like below.
    In the above example, I have defined the data type for the picklist and custom lookup.

    Step3 – Create a new html file inside the Same Web Component



    Now, you need to create the .html file inside the same Web Component. here is the sample code which is using a search component which is actually used for custom Lookup
    You can get the complete code for the Search Component from here

    Step4 – Prepare the Custom Lookup Columns for DataTable

    Now, we need to create a new Lighting Web Component which will be using the component which we have created on the top.

    Once you have created the component, you need to prepare the columns for data table like below

    The above code contains the column for custom lookup using our new component & data type that we have created.

    Here is the code for Custom Picklist

    Here is the code for custom file upload

  • Single Sign On(SSO)

    Single sign-on (SSO) lets users access authorized network resources with one login. You validate usernames and passwords against your corporate user database or other client app rather than Salesforce managing separate passwords for each resource.

     There are 2 ways we can implement SSO in Force.com

    1) Delegated authentication

    Delegated authentication SSO integrates Salesforce with an authentication method that you choose. You can integrate authentication with your LDAP (Lightweight Directory Access Protocol) server or use a token instead of a password for authentication. You manage delegated authentication at the permission level, not at the org level, giving you more flexibility. With permissions, you can require some to use delegated authentication while others use their Salesforce-managed password.
    Delegated authentication offers the following benefits.

    Uses a stronger form of user authentication, such as integration with a secure identity provider

    Makes your login page private and accessible only behind a corporate firewall

    Differentiates your org from all other companies that use Salesforce to reduce phishing attacks

    2) Federated Authentication

    Federated authentication using Security Assertion Markup Language (SAML) lets you send authentication and authorization data between affiliated but unrelated web services. You can log in to Salesforce from a client app. Salesforce enables federated authentication for your org automatically.

    Configure SSO Across Multiple Salesforce Orgs

    Let your users log in across multiple Salesforce orgs using single sign-on (SSO) credentials. With SSO, you can validate user credentials against a corporate database or other app rather than managing separate passwords for each Salesforce org.

    Enterprises often deploy more than one Salesforce org. Unless you implement SSO, users that access different orgs must reauthenticate with each org. Removing this extra login step makes it more convenient for users and enhances security because it’s easier for users to maintain and use a single, strong password.

    SSO follows a hub-and-spoke architecture. At the center is a centralized authentication hub, the identity provider. The identity provider validates credentials and asserts the user’s identity to the spokes—Salesforce orgs that are the service providers. The org that is the identity provider generates SAML assertions that follow the SAML 2.0 standard for SSO.

    Benefits of SSO

    Implementing SSO brings several advantages to your org.

    • Reduced administrative costs—With SSO, users memorize a single password to access network resources and external apps and Salesforce. When accessing Salesforce from inside the corporate network, users log in seamlessly and aren’t prompted for a username or password. When accessing Salesforce from outside the corporate network, the users’ corporate network login works to log them in. With fewer passwords to manage, system admins receive fewer requests to reset forgotten passwords.
    • Leverage existing investment—Many companies use a central LDAP database to manage user identities. You can delegate Salesforce authentication to this system. Then when users are removed from the LDAP system, they can no longer access Salesforce. Users who leave the company automatically lose access to company data after their departure.
    • Time savings—On average, users take 5–20 seconds to log in to an online app. It can take longer if they mistype their username or password and are prompted to reenter them. With SSO in place, manually logging in to Salesforce is avoided. These saved seconds reduce frustration and add up to increased productivity.
    • Increased user adoption—Due to the convenience of not having to log in, users are more likely to use Salesforce regularly. For example, users can send email messages that contain links to information in Salesforce, such as records and reports. When the recipient of the email message clicks the links, the corresponding Salesforce page opens.
    • Increased security—All password policies that you’ve established for your corporate network are in effect for Salesforce. Sending an authentication credential that’s only valid for a single time also increases security for users who have access to sensitive data.

    Viewing Single Sign-On Login Errors

    If your organization is enabled for Single Sign-On using delegated authentication and has built a Single Sign-On solution, you can view the most recent Single Sign-On login errors for your organization.


    • 1.From Setup, enter Delegated Authentication Error History in the Quick Find box, then select Delegated Authentication Error History.
    • 2.For the twenty-one most recent login errors, you can view the user’s username, login time, and the error.

  • Quick Text in Salesforce

    Quick text is predefined messages, like greetings, answers to common questions, and short notes. Which helps to stop retyping the same message over and over and save time. You can insert quick text in emails, chats, and more.

    Enable Quick Text:

    • From Setup enter Quick Text Settings in the Quick Find box
    • Select Quick Text Settings
    • Click Enable Quick Text
    • Save

    Where can use Quick Text?


    Give Users Access to Quick Text:

    Giving users access to quick text lets them insert predefined messages in their emails, chats, events, tasks, Knowledge articles, and more. Service agents can respond to customers and update cases quickly and easily. Sales reps can work with their contacts, accounts, and opportunities more efficiently.

    Use a permission set or update profiles to give your users Read permission on the Quick Text object. Optionally, you can also give users Create, Edit, and Delete access to let them create and manage their own quick text messages.

    Create Quick Text Messages:

    Create custom predefined messages to insert into emails, chats, tasks, events, and more. Quick text can include merge fields, line breaks, and special characters.

    • Open Quick Text tab
    • Click on New to create Quick Text (You can create record type for Quick Text)
    • Enter a message name (Use a name that helps users identify when to use this message)
    • Enter the message (The message can include line breaks, lists, special characters, merge fields, and up to 4,000 characters)
    • You can merge fields based on your requirement.
    • Select the channels in which you want the message to be available.
      • Email : For Email actions
      • Event : For Event actions
      • Internal : Works with internal fields, like on the Change Status action
      • Knowledge : For Knowledge articles in Lightning Experience
      • Live Agent : Works with Live Agent chat in the Service Console
      • Phone : or the Log a Call action
      • Portal : Works in a community or a customer portal
      • Social : For social posts
      • Task : For Task actions
    • Select a category
    • Select a channel
    • If you use merge fields, click Preview to review the message with data from records that you choose.
    • Save

    Insert and Use Quick Text:

    You can use quick text on all standard and custom objects in the following supported quick actions or places: emails, events, Knowledge articles, Live Agent chats, Log a Call action, social posts, and tasks.

    Share Quick Text:

    You can share quick text with users, public groups, and more. The way you share quick text in Salesforce Classic and Lightning Experience is different. In Salesforce Classic, you can share individual quick text. In Lightning Experience, you share quick text using folders.

    You can also change your org-wide default sharing setting for quick text. Or you can limit access by creating sharing rules to specify which groups of users have access to the quick text.