Set up Marketing Highlights

Last update: August 27, 2026

CREATED FOR:

Admin

Marketing Highlights shows each prospect’s live Marketo activity, such as email opens and clicks, web visits, and form fills. This article explains how to connect your Marketo instance so that activity flows in.

IMPORTANT

Completing this setup requires access to the Adobe Developer Console and to Admin in Marketo. Work with your Adobe contact and your Marketo administrator to complete the four parts below.

Setup has four parts:

Part A: Create API credentials in the Adobe Developer Console.
Part B: Gather your Sales Qualifier endpoint and identifiers.
Part C: Configure a webhook in Marketo Engage.
Part D: Add the webhook to a trigger Smart Campaign.

After setup is complete, users see and filter this activity on Prospects > Marketing Highlights.

Part A: Create API credentials part-a-create-api-credentials

These credentials let Marketo authenticate securely to Sales Qualifier.

To create the credentials:

Go to Adobe Developer Console and sign in with your Adobe ID.
Select Create new project, or open an existing project.
Select Edit project, rename the project to something identifiable, such as Sales Qualifier Marketing Highlights, and select Save.
Select Add API, select Experience Platform API, then select Next.
Choose OAuth Server-to-Server as the authentication type, then select Next.

OAuth Server-to-Server lets Marketo call the Sales Qualifier API directly from its server, without requiring a person to sign in.
Enter a credential name of 45 characters or fewer, such as Sales Qualifier Marketing Highlights Creds.
Select the product profile to associate, then select Save configured API.
Under Connected credentials, open the OAuth Server-to-Server credential. Select Retrieve client secret, then copy the Client ID and Client Secret. You use these values in Part C.

WARNING

Keep the Client Secret private. Treat it like a password, and do not send it by email. Use your organization’s approved secure channel to share it with whoever configures the webhook.

Part B: Gather your endpoint and identifiers part-b-gather-your-endpoint-and-identifiers

You need three values for Part C:

Endpoint URL—The Sales Qualifier webhook address for your region.
imsOrg ID—Your organization’s identifier in the Adobe Identity Management System (IMS), in the form {ORG_ID}@AdobeOrg.
Sandbox name—The name of your AEP sandbox exactly as it appears in the Sales Qualifier URL (the sname value), not the display name shown in the UI. Use the lowercase URL value, for example prod, not Prod.

Region

Webhook endpoint URL

North America

https://5r6xakp9k3.execute-api.us-east-1.amazonaws.com/prod/external/marketo/signals

EMEA

https://pc72i8q1k3.execute-api.eu-west-1.amazonaws.com/prod/external/marketo/signals

APAC / Australia

https://5cxxxyqlai.execute-api.ap-southeast-2.amazonaws.com/prod/external/marketo/signals

If you are unsure of your region, imsOrg ID, or sandbox name, your Adobe contact can confirm them.

Part C: Configure the Marketo webhook part-c-configure-the-marketo-webhook

To create the webhook:

In Marketo, select Admin > Webhooks.
Select New Webhook.
Set URL to the endpoint URL for your region from Part B.
Set Request Type to POST.
Set Request Token Encoding to JSON. This setting is required.

Paste the payload template below into Template. Use Marketo’s Insert Token to match the field names in your instance.

note
NOTE
With JSON encoding, do not wrap string tokens in quotation marks. Marketo adds them automatically.

code language-json

{
  "leadId": {{lead.Id:default=0}},
  "email": {{lead.Email Address:default=}},
  "fullName": {{lead.Full Name:default=}},
  "company": {{company.Company Name:default=}},
  "title": {{lead.Job Title:default=}},
  "department": {{lead.Department:default=}},
  "country": {{lead.Country:default=}},
  "score": {{lead.Lead Score:default=0}},
  "rating": {{lead.Lead Rating:default=}},
  "leadStatus": {{lead.Lead Status:default=}},
  "leadSource": {{lead.Lead Source:default=}},
  "isCustomer": {{lead.Is Customer:default=false}},
  "industry": {{company.Industry:default=}},
  "annualRevenue": {{company.Annual Revenue:default=0}},
  "numEmployees": {{company.Num Employees:default=0}},
  "campaignId": {{campaign.id:default=0}},
  "campaignName": {{campaign.name:default=}},
  "programName": {{program.name:default=}},
  "occurredAt": {{system.dateTime:default=}},
  "munchkinId": {{system.munchkinId:default=}},
  "triggerName": {{trigger.Trigger Name:default=}},
  "crmId": {{lead.SFDC ID:default=}},
  "crmType": {{lead.SFDC Type:default=}},
  "crmOwnerEmail": {{lead.Lead Owner Email Address:default=}},
  "crmOwnerFirstName": {{lead.Lead Owner First Name:default=}},
  "crmOwnerLastName": {{lead.Lead Owner Last Name:default=}},
  "attributes": {
    "asset": {{trigger.Name:default=}},
    "link": {{trigger.Link:default=}},
    "subject": {{trigger.Subject:default=}},
    "webPage": {{trigger.Web Page:default=}},
    "category": {{trigger.Category:default=}},
    "details": {{trigger.Details:default=}},
    "sentBy": {{trigger.Sent By:default=}},
    "receivedBy": {{trigger.Received By:default=}},
    "referrer": {{trigger.Referrer:default=}},
    "searchEngine": {{trigger.Search Engine:default=}},
    "searchQuery": {{trigger.Search Query:default=}},
    "imDescription": {{lead.Last Interesting Moment Desc:default=}},
    "imType": {{lead.Last Interesting Moment Type:default=}},
    "imDate": {{lead.Last Interesting Moment Date:default=}},
    "imSource": {{lead.Last Interesting Moment Source:default=}},
    "chatAgentName": {{trigger.Agent Name:default=}},
    "chatAgentEmail": {{trigger.Agent Email:default=}},
    "chatConversationStatus": {{trigger.Conversation Status:default=}},
    "chatConversationSummary": {{trigger.Conversation Summary:default=}},
    "chatGoalName": {{trigger.Goal name:default=}},
    "chatMeetingStatus": {{trigger.meeting status:default=}},
    "chatScheduledFor": {{trigger.Scheduled For:default=}},
    "chatDocumentName": {{trigger.Document Name:default=}},
    "chatDocumentUrl": {{trigger.Document URL:default=}},
    "chatPageUrl": {{trigger.Page URL:default=}}
  }
}

Select Webhook Actions > Set Custom Header, then add the following headers, using the values from Part A and Part B:

table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 5-row-2 layout-auto
Header	Value
`Content-Type`	`application/json`
`x-client-id`	Your Client ID
`x-client-secret`	Your Client Secret
`x-gw-ims-org-id`	Your imsOrg ID
`x-sandbox-name`	Your sandbox name

Select Save.

Part D: Add the webhook to a trigger Smart Campaign part-d-add-the-webhook-to-a-trigger-smart-campaign

Add a Call Webhook flow step to a trigger Smart Campaign, either an existing one or a new one. The Smart List triggers on that campaign decide which activities are sent to Sales Qualifier.

To add the webhook:

Open an existing trigger Smart Campaign, or create a new one (Marketing Activities > New > Smart Campaign).
On the Smart List tab, add the trigger or triggers for the activities you want to send, for example Clicks Link in Email, Fills Out Form, or Visits Web Page.
On the Flow tab, add a Call Webhook step and select the webhook you created in Part C.
Activate the Smart Campaign.

Activity from that Smart Campaign now flows into Sales Qualifier. Representatives see and filter this activity on Prospects > Marketing Highlights.

recommendation-more-help

sales-qualifier-help