Inbox Tracker Installation Guide

If you are a Salesforce Marketing Cloud Administrator, please follow these one-time steps to install the SparkPost Inbox Tracker application through the AppExchange.

• You will be automatically be redirected to the installation page if you are logged into SFMC

• In the top right corner, select Install

Please do not skip this step! The data extension will not be visible if it is skipped.

• Refresh your browser window
• Click on the AppExchange icon to make sure that SparkPost Inbox Tracker is a selectable option and open it

• Please return to the installation page. In the top tab, select Access

• This page allows you to enable a user's access to the Inbox Tracker application within SFMC. Upon granting access, these users will see our application listed in the AppExchange dropdown (as shown in Step 2). There are two prerequisites to granting this access:

  • Users must have logins to Inbox Tracker

    • Related: How to Add Users

  • Individual users must have Content Creator rights in Salesforce or have custom role defined by organization that grants access to read/write content, data, applications, audiences, journeys

• If you want to grant access to ALL users that meet the above criteria, select License All Users in the top right corner

• If you only want certain users to access the application, select your individual business units on the left and select which users you would like to delegate access. Make sure to press Save in the top right.

• Navigate to this this page
• Select SFMC Email Sending Stats

• In the top right corner, click Run once
• Select the schedule to repeat every hour and the expiration to never

The configuration for the application, seed lists, and other information will be stored in the Data Extension folder named “SparkPost Integrations <MID Number>”.

• There are two ways to find the Data Extension
  • Email Studio > Email > Subscribers > Data Extensions
  • Audience Builder > Data Extensions

Note: The application footprint Data Extension will not be created until an authorized user logs into application (as shown in Step 2.)