Managed Salesforce Package

What is in the Package?

When you install the package in your Salesforce org, you gain visibility into Paminga through iFrames.

Those iFrames let you see a Contact's activity history, adjust their lead score, and even unsubscribe them from email communications right from Salesforce. It is the same panel Dynamics customers get from Paminga for Dynamics 365.

The package also includes custom fields that surface marketing attribution data such as First Touch and Last Touch sources and dates, Lead Score, and Most Recent Visit date.

The package works for Paminga accounts hosted in the US and in the EU. One setting, Paminga Region, tells it which Paminga instance to load the panel from; see Post Install Instructions below.

Package Install Instructions

Install the Paminga package into Salesforce

• Already have an earlier version installed? Read Upgrading from an Earlier Version first
• Click one of these links to login and begin the installation process
  • Install in Production Instance
  • Install in Sandbox Instance
• Select Install for Admins Only if you plan to grant access through the Paminga Permissions permission set the package includes
• Select Install for All Users to have the fields and iFrames available by default on every custom profile. Users on a standard profile, such as Standard User, still need the permission set; see Who Can See the iFrames and Fields
• Check the box for I acknowledge that I’m installing a Non-Salesforce Application that is not authorized for distribution as part of Salesforce’s AppExchange Partner Program
• Click on Install
• You will be prompted to Approve Third-Party Access
  • The package adds https://crm.paminga.com, https://crm.eu.paminga.com, and https://www.paminga.com to CSP Trusted Sites
  • This allows Salesforce to display the Paminga iframes, whichever region your account is in.
  • Check the box for Yes, grant access to these third-party web sites
  • Click Continue
• You will see a spinner for Installing and granting access to [your Install for selection]...
• You will end on the screen Installation Complete!
  • The Post Installation Instructions will be displayed
  • Click Done

Post Install Instructions

Get the Paminga App Token

• Log into Paminga as the user you choose to use for iframe authentication. US accounts sign in at app.paminga.com; EU accounts sign in at app.eu.paminga.com
• In the upper right, hover the user initials and click Personal Settings
• In the Left Nav, click Personal Access Tokens
• Click Generate Token
• Name the token Salesforce iframe Token
• Click Create Token
  • Copy this token for use in Salesforce

A token belongs to one Paminga instance

A Personal Access Token only authenticates on the instance it was created on. If your account is hosted in the EU, create the token while signed in at app.eu.paminga.com, and set Paminga Region to EU in the next step. A US token with an EU region, or the reverse, shows "Unable to authenticate to Paminga" in the frame.

Enter your Paminga App Token into Salesforce

• Go to Setup->Custom Code->Custom Metadata Types
• You will see Paminga Settings
  • Click Manage Records
• Click New
• For the Label, enter App Token
• For the Name, it will auto-fill as App_Token
• Paste your copied token into the Paminga App Token field
• Leave Paminga Region at US, or choose EU if your Paminga account is hosted in the EU
• Click Save

Create one record only. The package reads the record named App_Token; if there is none, it reads the first record by Name. Every Salesforce user sees the panel through this one token, so there is no need for a record per salesperson.

Add the Paminga fields and iframes to your layouts

• Salesforce Classic

  • Setup->Objects and Fields->Object Manager->Account->Page Layouts
  • Setup->Objects and Fields->Object Manager->Contact->Page Layouts
  • Setup->Objects and Fields->Object Manager->Lead->Page Layouts

• Lightning

  • Setup->Objects and Fields->Object Manager->Account->Lightning Record Pages
  • Setup->Objects and Fields->Object Manager->Contact->Lightning Record Pages
  • Setup->Objects and Fields->Object Manager->Lead->Lightning Record Pages

• There are 8 custom fields for Contacts and Leads

  • First Touch Marketing Channel
  • First Touch Source
  • First Touch Date
  • Last Touch Marketing Channel
  • Last Touch Source
  • Last Touch Date
  • Paminga Lead Score
  • Most Recent Visit Date

• The Account, Contact, and Lead iFrames

  • VisualForce Pages for Salesforce Classic Page Layouts
    • Paminga Account Iframe Page
    • Paminga Contact Iframe Page
    • Paminga Lead Iframe Page
    • Set each Visualforce section's height to 600 pixels. The layout editor starts it at 200, which cuts the panel off
  • Lightning Web Components for Lightning Record Pages
    • pamingaRecordIframe (a single component to use on each module type)

Who Can See the iFrames and Fields

If you installed for All Users, every internal custom profile can already open the iFrames and read the eight fields. Standard profiles, such as Standard User, get nothing from the install, so assign those users the Paminga Permissions permission set (Setup → Users → Permission Sets). If you installed for Admins Only, assign the permission set to every user who needs the panel. It grants read access to the eight fields and access to the iFrame pages and component, nothing else.

The fields are written by the Paminga sync, so the permission set grants read access only. Install for All Users is different: it makes the fields editable on every custom profile, and a read-only permission set cannot take that back. If you do not want people editing them, install for Admins Only and assign the permission set, or remove edit access on those profiles after installing. The Salesforce user the Paminga sync connects as needs edit access to them; a System Administrator already has it.

Upgrading from an Earlier Version

First check Setup → Installed Packages and look at the Namespace Prefix of your Paminga package.

If it is paminga, install the new version with the same links above. Salesforce upgrades the package in place and keeps your App Token record and your attribution field data. You are asked again to Approve Third-Party Access, because the new version adds the EU host; grant it, or the frame stays blank. If your account is hosted in the EU, set Paminga Region to EU on the App Token record after the upgrade: versions before 1.2 had no region setting and always loaded the US panel. Users who already had a record page open need a full browser reload before the new region takes effect.

Salesforce does not change a package's page layouts during an upgrade, so the App Token record's edit page may not show Paminga Region yet. If it doesn't, go to Setup → Custom Code → Custom Metadata Types, click Paminga Settings, edit Paminga Setting Layout under Page Layouts, drag Paminga Region into the layout, and save. Then edit the record again.

If the prefix is anything else, or blank, you have an older, separate Paminga package that this version cannot upgrade. Installing 1.2 would put a second package beside it. Before you uninstall it, remove its iFrames from your Lightning record pages and page layouts, and delete the records you created in its settings, such as App_Token. Salesforce refuses the uninstall while either is still there, and the uninstall page lists anything else in the way. Uninstalling deletes the values in its fields. If you want to keep them, tick Save a copy of this package's data on the uninstall page before you confirm. Then follow Package Install Instructions and Post Install Instructions as a new install.

Troubleshooting

The frame says "Unable to authenticate to Paminga". The token and the Paminga Region on your App Token record point at different instances (a token from app.paminga.com with Region EU, or one from app.eu.paminga.com with Region US), or the token no longer works: it was revoked, or the Paminga user it belongs to was deactivated. Check which instance you signed in to when you created the token, then check the record. After an upgrade, a record with no region loads the US panel; see Upgrading from an Earlier Version. If you changed the region a moment ago, reload the browser tab: Salesforce caches the frame's address for the page.

A toast says "Error loading iframe: The App Token is not saved in Paminga Settings". The package found no Paminga Settings record. Either none exists yet, or the token went into the settings of an older Paminga package. In Salesforce Classic the frame shows a Visualforce error instead of the toast. Go back to Post Install Instructions.

The frame is blank or says "This content is blocked". Salesforce is blocking the Paminga host, usually because third-party access was declined during install. Go to Setup → Security → Trusted URLs and make sure https://crm.paminga.com and https://crm.eu.paminga.com are present, Active, and have frame-src (iframe content) ticked. Edit any that are not, tick what is missing, and save.

The frame says "crm.paminga.com refused to connect". The same applies to crm.eu.paminga.com. Your Salesforce domain is not on Paminga's embed allow-list. This is on our side, not yours: email support@paminga.com with your Salesforce URL and the exact message.

The frame says "We looked, but were unable to find a contact using the email that's present in the URL." The Paminga account the token belongs to has no contact with the record's email address. Either the record has not synced to Paminga yet, or the token was created on a different Paminga account than the one holding your data.