Outreach connection

Overview overview

Outreach is a Sales Execution Platform with the most B2B buyer-seller interaction data in the world and significant investments in proprietary AI technologies to translate sales data into intelligence. Outreach helps organizations automate sales engagement and act on revenue intelligence to improve their efficiency, predictability, and growth.

This Adobe Experience Platform destination leverages the Outreach Update Resource API, which allows you to update identities within an audience corresponding to prospects in Outreach.

Outreach uses OAuth 2 with Authorization Grant as the authentication mechanism to communicate with the Outreach Update Resource API. Instructions to authenticate to your Outreach instance are further below, within Authenticate to destination section.

Use cases use-cases

As a marketer, you can deliver personalized experiences to your prospects, based on attributes from their Adobe Experience Platform profiles. You can build audiences from your offline data and send these audiences to Outreach, to display in the prospects’ feeds as soon as audiences and profiles are updated in Adobe Experience Platform.

Prerequisites prerequisites

Experience Platform prerequisites prerequisites-in-experience-platform

Before activating data to the Outreach destination, you must have a schema, a dataset, and segments created in Experience Platform.

Refer to Adobe’s documentation for Audience Membership Details schema field group if you need guidance on audience statuses.

Outreach prerequisites prerequisites-destination

Note the following prerequisites in Outreach, in order to export data from Platform to your Outreach account:

You need to have an Outreach account prerequisites-account

Go to the Outreach sign in page to register and create an account, if you do not have one already. Also see the Outreach support page for more details.

Note down the items below before you authenticate to the Outreach CRM destination:

Your Outreach account email
Your Outreach account password

Set up custom field labels prerequisites-custom-fields

Outreach supports custom fields for prospects. Refer to How To add a custom field in Outreach for additional guidance. For ease of identification it is recommended to manually update the labels to their corresponding audience names instead of keeping the defaults. For example as below:

Outreach settings page for prospects displaying custom fields.
Outreach UI screenshot showing the custom fields on the settings page.

Outreach settings page for prospects displaying custom fields with user-friendly labels matching to the audience names. You can view the audience status on the prospect page against these labels.
Outreach UI screenshot showing custom fields with associated labels on the settings page.

Label names are for ease of identification only. They are not used when updating prospects.


The Outreach API has a rate limit of 10,000 requests per hour per user. If you reach this limit you will receive a 429 response with the following message: You have exceeded your permitted rate limit of 10,000; please try again at 2017-01-01T00:00:00..

If you received this message, you must update your audience export schedule to conform to the rate threshold.

Refer to the Outreach documentation for additional details.

Supported identities supported-identities

Outreach supports update of identities described in the table below. Learn more about identities.

Target identity
  • Outreach identifier. This is a numeric value corresponding to the prospect profile.
  • The ID must match the ID within the Outreach URL for the prospect being updated.
  • Refer to the Outreach documentation for further details.

Export type and frequency export-type-frequency

Refer to the table below for information about the destination export type and frequency.

Export type
  • You are exporting all members of a segment, together with the desired schema fields (for example: email address, phone number, last name), according to your field mapping.
  • Each segment status in Outreach gets updated with the corresponding audience status from Platform, based on the Mapping ID value provided during the audience scheduling step.
Export frequency
  • Streaming destinations are “always on” API-based connections. As soon as a profile is updated in Experience Platform based on audience evaluation, the connector sends the update downstream to the destination platform. Read more about streaming destinations.

Connect to the destination connect

To connect to the destination, you need the Manage Destinations access control permission. Read the access control overview or contact your product administrator to obtain the required permissions.

To connect to this destination, follow the steps described in the destination configuration tutorial. In the configure destination workflow, fill in the fields listed in the two sections below.

Within Destinations > Catalog search for Outreach. Alternatively you can locate it under the CRM category.

Authenticate to destination authenticate

To authenticate to the destination, select Connect to destination.

Platform UI screenshot showing how to authenticate to Outreach.

You will be shown the Outreach login page. Provide your email.

Outreach UI screenshot showing the field to input email to authenticate to Outreach.

Next provide your password.

Outreach UI screenshot showing the field to input password step to authenticate to Outreach.

  • Username: Your Outreach account email.
  • Password: Your Outreach account password.

If the details provided are valid, the UI displays a Connected status with a green check mark. You can then proceed to the next step.

Fill in destination details destination-details

To configure details for the destination, fill in the required and optional fields below. An asterisk next to a field in the UI indicates that the field is required.
Platform UI screenshot showing how to fill in details for the Outreach destination.

  • Name: A name by which you will recognize this destination in the future.
  • Description: A description that will help you identify this destination in the future.

Enable alerts enable-alerts

You can enable alerts to receive notifications on the status of the dataflow to your destination. Select an alert from the list to subscribe to receive notifications on the status of your dataflow. For more information on alerts, see the guide on subscribing to destinations alerts using the UI.

When you are finished providing details for your destination connection, select Next.

Activate audiences to this destination activate


Read Activate profiles and audiences to streaming audience export destinations for instructions on activating audiences to this destination.

Mapping considerations and example mapping-considerations-example

To correctly send your audience data from Adobe Experience Platform to the Outreach destination, you need to go through the field mapping step. Mapping consists of creating a link between your Experience Data Model (XDM) schema fields in your Platform account and their corresponding equivalents from the target destination. To correctly map your XDM fields to the Outreach destination fields, follow these steps:

  1. In the Mapping step, click Add new mapping. You will see a new mapping row on the screen.
    Platform UI screenshot showing how to Add new mapping

  2. In the Select source field window, choose the Select identity namespace category and add the desired mappings.
    Platform UI screenshot showing Source mapping

  3. In the Select target field window, select the type of target field that you want to map your source field to.

    • Select identity namespace: select this option to map your source field to an identity namespace from the list.
      Platform UI screenshot showing Target mapping using OutreachId.

    • Add the following mapping between your XDM profile schema and your Outreach instance:

      table 0-row-3 1-row-3
      XDM Profile Schema Outreach Instance Mandatory
      Oid OutreachId Yes
    • Select custom attributes: select this option to map your source field to a custom attribute that you define in the Attribute name field. Refer to Outreach prospect documentation for a comprehensive list of supported attributes.
      Platform UI screenshot showing Target mapping using LastName.

    • For instance, depending on the values you want to update, add the following mapping between your XDM profile schema and your Outreach instance:

      table 0-row-2 1-row-2 2-row-2
      XDM Profile Schema Outreach Instance
      person.name.firstName firstName
      person.name.lastName lastName
    • An example using these mappings is shown below:
      Platform UI screenshot example showing Target mappings.

Schedule audience export and example schedule-segment-export-example

  • When performing the Schedule audience export step you must manually map Platform audiences to the custom field attribute in Outreach.

  • To do this, select each segment, then enter the corresponding numeric value which corresponds to the Custom Field N Label field from Outreach in the Mapping ID field.

    note important
    • The numeric value (N) used within the Mapping ID should match the custom attribute key suffixed with the numeric value within Outreach. Example: Custom Field N Label.
    • You only need to specify the numeric value, not the whole custom field label.
    • Outreach supports a maximum of 150 custom label fields.
    • Refer to Outreach prospect documentation for details.
    • For example:

      table 0-row-2 1-row-2
      Outreach Field Platform Mapping ID
      Custom Field 4 Label 4

      Platform UI screenshot showing an example Mapping Id during Schedule audience export.

Validate data export exported-data

To validate that you have correctly set up the destination, follow the steps below:

  1. Select Destinations > Browse to navigate to the list of destinations.
    Platform UI screenshot showing Browse Destinations.

  2. Select the destination and validate that the status is enabled.
    Platform UI screenshot showing Destinations Dataflow Run for the selected destination.

  3. Switch to the Activation data tab, then select an audience name.
    Platform UI screenshot showing Destinations Activation data.

  4. Monitor the audience summary and ensure that the count of profiles corresponds to the count created within the segment.
    Platform UI screenshot showing Segment summary.

  5. Log in to the Outreach website, then navigate to the Apps > Contacts page and check if the profiles from the audience have been added. You can see that each audience status in Outreach was updated with the corresponding audience status from Platform, based on the Mapping ID value provided during the audience scheduling step.

Outreach UI screenshot showing the Outreach Prospects page with the updated audience statuses.

Data usage and governance data-usage-governance

All Adobe Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how Adobe Experience Platform enforces data governance, see the Data Governance overview.

Errors and troubleshooting errors-and-troubleshooting

When checking a dataflow run, you might see the following error message: Bad request reported while pushing events to the destination. Please contact the administrator and try again.

Platform UI screenshot showing the Bad request Error.

To fix this error, verify that the Mapping ID you provided in Platform for your Outreach audience is valid and exists in Outreach.

Additional resources additional-resources

The Outreach documentation has details on Error Responses which you can use to debug any issues.