Adobe Campaign Standard (oAuth) Connector Setup Guide | Server-Side Connectors

API Information

This connector uses the following vendor API:

API Name: Adobe Campaign Standard (OAuth)
API Version: v1.0
API Endpoint: https://mc.adobe.io/

Connector Actions

Action Name	AudienceStream	EventStream
Send Transactional Event	✓	✗
Trigger Signal Activity	✓	✗
Create or Update Profile	✓	✗

Configure Settings

Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article.

After adding the connector, configure the following settings:

Technical Account ID
- The Technical Account ID can be found in the Adobe I/O Console.
- For more information, see Authenticating and accessing Adobe Experience Platform APIs.
Organization ID
- The Organization ID can be found in the Adobe I/O Console.
Tenant ID
- The Tenant ID can be found in your Adobe Marketing Cloud URL.
- Example: https://yourtenantid.experiencecloud.adobe.com/campaign.html
API Key
- The API Key (Client ID) can be found in the Adobe I/O Console.
Secret Key
- The Client Secret can be found in the Adobe I/O Console.

Action settings - parameters and options

Enter a name for the action and select the action type from the drop-down menu.

The following section describes how to set up parameters and options for each action.

Action - Send Transactional Event

Parameters

Parameter	Description
Email	Required. The email address of the recipient.
Event ID	Required. The type of event you want to send. This ID is generated when creating the event definition. For additional information, see the Adobe Campaign Documentation.
Expiration Date	Optional. The sending of the transactional event will be cancelled after this date.
Scheduled Send Date	Optional. The transactional event will be processed and the transactional message will be sent at this date.
Transactional API Endpoint	Optional. Specify to override default value of `mc` followed by Tenant ID from connector configuration. This is typically applicable when working in your stage instance. For example, if stage Tenant ID is `geometrixx-mkt-stage3`, then override Transactional API Endpoint to `geometrixx`.
Template Name	If using a template to pass data, input with Transactional Message Content Template and enter name of main template. Do not include double curly braces in name. For example, use `SomeTemplateName` not `{{SomeTemplateName}}`.
Template Variables	Provide template variables as data input for Transactional Message Content Template. For additional information, see: Template Variables Guide). Name nested template variables with the dot notation. Example: `items.name` Nested template variables are typically built from data layer list attributes.
Transactional Message Content Template	Template describing enriched transactional message content. Templates are injected by name with double curly braces into supported fields. Example: `{{SomeTemplateName}}` For additional information about using enriched message content, see Adobe’s Campaign Documentation.

Action - Trigger Signal Activity

Parameters

Parameter	Description
Workflow ID	The ID of the workflow configured in your Adobe console.
Source	Used to indicate the triggering request source.
Parameter Map	It is possible to call a workflow with parameters. Map a parameter’s value to it’s name. String, Number, Boolean, and Date/Time types are supported.

Action - Create or Update Profile

Parameters

Parameter	Description
Update Strategy	Required Select applicable update strategy. Create Only — Look up an existing profile and if not found, create a new profile. Update Only — Look up an existing profile and update it. Create or Update — Look up an existing profile and if found, update it, otherwise create a new profile.
Filter	Required when Update Strategy is Create Or Update or Update Only. It is strongly recommended to select filters that return unique results. For additional information, see Composite Identification Key. If the search result returns multiple profiles, only the first one is updated.
Is Custom Filter	See about custom filters.
Template Variables	Provide template variables as data input. For additional information, see Template Variables Guide. Name nested template variables with the dot notation. Example: `items.name` Nested template variables are typically built from data layer list attributes.
Templates	Provide templates to be referenced in body data. For additional information, see Trimou Templating Engine Guide. Templates are injected by name with double curly braces into supported fields. Example: `{{SomeTemplateName}}`