Salesforce Managed Package
Strala's Salesforce Managed Package is a set of code that adds required fields to the Contact and Lead objects in order to integrate with Strala JourneyStream to capture Conversion Events needed for attribution.
Additionally, it installs Apex classes that allow you to fire conversion events into JourneyStream based on events that happen in Salesforce through Salesforce's Process Builder.
Managed Package Installation
We are currently waiting for final App Exchange approval from Salesforce for our managed package. While this is still in process, Strala's Managed Package can still be installed on Sandbox or Production, using the following link:
You will need to replace the host name with your salesforce instance name if you are installing on a Sandbox.
When you go to this link, you will receive a notice that you are installing a Non-Salesforce Application. We anticipate final approval shortly, which will eliminate this warning. Select Install for All Users, select the checkbox to acknowledge you are installing the managed package, and click Install to begin the process.
There will not be any PII sent to Strala or stored at Strala. However, we will receive contact_id, lead_id, opportunity_id, and account_id as well as create dates for those fields.
For conversion events where an opportunity is involved, we have the ability to receive information like opportunity amount, product, etc. but that is controlled by the party sending the data and it is up to you if they choose to send that information as part of the conversion event.
If information like an email address is needed for association events, it must be a consistently hashed and salted email address before it is sent to us, where we don’t know the salt. Alternatively we prefer to use the contact or other system ID to represent the individual.
To send JourneyStream events from Salesforce, you will need to grant access to Strala's JourneyStream web sites. Grant this access and click Continue.
The installation process will take a few minutes while it adds the objects, classes and grants access to those classes.
Once the process is finished, you will receive the following notification
Depending on your Salesforce instance's performance at the time of installation, you may see the following warning:
This happens when Salesforce is processing other tasks and it reaches its default timeout. Click Done, which will return you to the Installed Packages window. The installed package should show up within a minute and will be viewable after you refresh the page.
Organization Level Custom Settings
You'll need to configure some custom settings at the organization level in order for the managed package to function correctly. Navigate to Setup > Custom Code > Custom Settings. You should see an entry labelled Strala Journey Settings. Click on the label:
At the page that pops up, hit Manage
This will bring you to a page where you can specify custom settings for users, groups, and most importantly the organization. We're concerned with the organization level values for this custom settings group. If you have not installed the managed package before, there will be a New button at the bottom of the page header. If you have installed the managed package before, the button will be replaced with one that says Edit. Click on the applicable button in order to update your settings:
At the page that pops up, you'll want to enter the following values:
- Strala Org UUID: your organization's UUID as provided by customer success
- Enable JourneyStream Debugging: true or false, provides slightly more information when requests fail.
- Strala JourneyStream Endpoint:
You'll want to ensure that the relevant URL has been added as a remote site as well. While the managed package install tries to take care of this for you, some organizations disallow automatic authorization of remote sites.
Once the managed package is installed, you will need to create processes using Salesforce's Process Builder to fire events into JourneyStream. This enables an organization to control and define the business rules surrounding when an event should fire. Because every instance of Salesforce is set up and configured differently, this allows maximum flexibility to match your business rules and fire consistent conversion events across multiple Salesforce instances or using different rules within the same instance.